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
subtle changes after fixing #11 #19
Comments
sure,
|
|
Oh, now I understand, the directory is not writable… |
This fix should work. |
Yes its fixed. |
dg
added a commit
that referenced
this issue
Feb 25, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version: dev-master
Bug Description
After file locking changes in #11 we can't have read-only cache.
We are getting errors like
file cache permissions are:
we have successfully used: on deploy we generate our class cache. web server is not allowed to
change class cache file due permissions. Everything works fine until #11
Steps To Reproduce
generate cache with one user, and try to use it with another
Expected Behavior
To works like before
Possible Solution
revert everything until 180f89e
and it works like a charm
The text was updated successfully, but these errors were encountered: