fix(occ): Suppress errors when checking config.php fileowner#51594
Merged
provokateurin merged 1 commit intomasterfrom Mar 26, 2025
Merged
fix(occ): Suppress errors when checking config.php fileowner#51594provokateurin merged 1 commit intomasterfrom
provokateurin merged 1 commit intomasterfrom
Conversation
Signed-off-by: provokateurin <[email protected]>
Member
Author
|
/backport to stable31 |
Member
Author
|
/backport to stable30 |
This was referenced Mar 26, 2025
8 tasks
Merged
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
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.
Summary
In a docker container of mine I've seen that I'm unable to install since #33545:
I have never seen it fail locally, but I have seen a few times that if something goes wrong in occ, odd errors are thrown down the line.
I tried this patch in the docker container and it makes it successfully install again.
I'm quite surprised, that I didn't find any reports about this issue in the server or docker repos.
Checklist