-
-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
composer update on v2.4.2: Failed to write into cache: file_put_contents(%localappdata%/Composer/repo/...) In Cache.php line 147 #11076
Comments
This doesn't make much sense to me at first sight, as it should check if the dir exists and if not create it before doing the write ( composer/src/Composer/Cache.php Lines 92 to 105 in ce082cd
composer/src/Composer/Cache.php Line 140 in ce082cd
If there is a chance for you to run composer from source and try to debug this a bit that'd be valuable, because otherwise I don't see how we'll get to the bottom of this. |
What really confuses me is that all the dependencies are re-downloaded after the last How would i run composer from source? can you kindly point me to some kind of instructions? Thanks |
@aetonsi clone the composer git repository somewhere, run |
The downloading done at the end seems to be related to security advisories according to the stack trace when the error occurs. |
hi, i did a self update to this version and i can confirm that now it works without error!! |
My
composer.json
:Output of
composer diagnose
:When I run this command:
I get the following output:
PLEASE NOTE: i HAVE to truncate the output as it's too big for github (max 65536 characters). I will put "..." instead of portions of the output
And I expected this to happen:
All the errors
Failed to write into cache: file_put_contents(C:/Users/u6/AppData/Local/Composer/repo/ [...]
should not happen.The given folder
%localappdata%/Composer/repo
doesn't exist.Please note that with a composer.phar version 2.2 there's no error! There's actually no output after the last post-update-cmd (
post-update-cmd: @php artisan vendor:publish --tag=laravel-assets --ansi --force
).With the current version 2.4.2, instead, it does all of that downloading after the last post-update-cmd.
Have a nice day
The text was updated successfully, but these errors were encountered: