Skip to content
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

Errors occur trying to write composer caches #121

Closed
ScopeyNZ opened this issue Sep 11, 2018 · 6 comments
Closed

Errors occur trying to write composer caches #121

ScopeyNZ opened this issue Sep 11, 2018 · 6 comments

Comments

@ScopeyNZ
Copy link
Contributor

ScopeyNZ commented Sep 11, 2018

This package uses Composer API to get information about packages. When this happens, composer attempts to write caches to the configured cache directory (.composer) using the COMPOSER_HOME or HOME environment variable. This causes errors on CWP where the .composer parent directory is not writable (this comes from HOME).

We have anticipated this in bringyourownideas/silverstripe-composer-update-checker: https://github.com/bringyourownideas/silverstripe-composer-update-checker/blob/1/src/Extensions/ComposerLoaderExtension.php#L100-L112

This code should be migrated to this module.

This causes Greylog to be flooded with errors.

@ScopeyNZ
Copy link
Contributor Author

Raising the priority. I realised that it's quite likely environments have a HOME environment variable defined - if this is not writable then the extension code won't resolve the issue. We should probably just rely on COMPOSER_HOME, the fallback to HOME seems a little unsafe - although usually you would expect HOME to be writable...

@indygriffiths
Copy link

indygriffiths commented Oct 8, 2018

Has there been any movement on this issue? The "permission denied" error from this module and the update checker has chewed through about a quarter of our monthly Raygun error allocation.

@robbieaverill
Copy link
Contributor

@indygriffiths would you like to try the patch on the platform? That's really all that's holding this up

@robbieaverill
Copy link
Contributor

@brynwhyman
Copy link

@indygriffiths have you had a chance to test this patch? If not, I'll get the team to look at it this week. Sorry for the delay on this one.

@robbieaverill
Copy link
Contributor

Fixed in #42 and #43

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants