New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to extract using '/usr/bin/unzip' #10379
Comments
This is quite weird. I haven't seen this ever.. Do you have any strange setup/env/VM on your GH actions? I wonder why retrying unzipping would help, as it does seem to have a corrupt file, and retrying the whole download I'd rather not do given the separation of download/install steps we now have. |
I think I've just reproduced this and I believe it can occur when upgrading from composer v1 to v2. If you have a cache for v1, possibly with older versions of some packages (for me it happened with both symfony/string and symfony/console) you can get this error when running in composer v2. If you remove So if experiencing this, consider deleting |
Could be fixed by #10666 too, or not, but if not then I don't really know what to do here so closing for now, if someone has more info and a repro case feel free to reopen. |
FIY just met this problem using Circle CI for tests. There we install libraries, test app, then reinstall libraries with
Steps wget https://raw.githubusercontent.com/pb-sylius/3brs-sylius-sorting-plugin/5f3dd2d538bca98182b243518501c1f15c5836ae/composer.json
composer update --no-interaction --prefer-dist
composer update --no-interaction --prefer-lowest |
@jaroslavtyc I cannot reproduce this, so again I'm not sure what to say if there is no clear repro or more details as to what is wrong, please try to inspect the state of the cache (/root/project/vendor/composer/tmp-f93ae3ef863034d047581f82d590e064 or whatever it came from in the cache, should be stated above somewhere if you run with |
In my case, this was happening because i had 2 docker containers automated to I removed my volume as I didn't need it anyway. |
In our case asset packagist was the reason. We moved the project URL at GitLab, but the asset packagist URL was still the old one! |
from time to time we experience errors like
in our github actions.
usually just re-starting the github action fixes this problem.
could composer retry the unzip/download to make this more robust?
env:
The text was updated successfully, but these errors were encountered: