add file path in opcache lock file error - #10331
Merged
Merged
Conversation
Member
|
Thank you for the PR! I don't think that "opcache" to the output makes much sense, since this is written to the OPcache log (not the general error log, anyway). I am not sure about |
Contributor
Author
|
I get this error in the output of a container, trying to use a readonly filesystem, so I had no indication on the opcache log. Yes, logfile_path can be sufficient. |
jfcoz
force-pushed
the
opcache_lock_error
branch
from
January 15, 2023 18:31
42d68fd to
50fcf51
Compare
dstogov
approved these changes
Oct 9, 2023
Member
|
Sorry for missing this. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Make error more verbose with the lock file path