-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Do not disable shipped apps on exceptions #7865
Comments
The error looked like this:
|
server/lib/private/legacy/app.php Lines 237 to 243 in e3c0fd6
Check the exception for some types? |
Or just change getAlwaysEnabledApps to getShippedApps |
using getShippedApps instead could improve it, but it won't catch all scenarios. After all, any other app could also cause similar affects, when Redis just becomes unavailable. Additionally we could whitelist some known Exceptions (e.g. also databases if they're down). It's not super proof still. |
Since the last upgrade (12.0.4) following apps were disabled several times and i believe it's the same issue: files_sharing |
Yeah, but than again. If the app fails with a database error, we can't know was it because the database had a hick up, or is the app broken and using an invalid schema etc. I'd say lets start this slowly. I will make a patch to protect shipped apps. |
cc @rullzer @schiessle @blizzz @ChristophWurst @nickvergessen @danxuliu Do you have an idea how to mitigate this?
The text was updated successfully, but these errors were encountered: