You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
once the connection to the redis server is somehow not working, the server catches the exception and will disable the app in which it happened - in this case it was files_sharing which caused all shares being deleted from user computers :/
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.
After all, any other app could also cause similar affects, when Redis just becomes unavailable.
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.
Activity
MorrisJobke commentedon Jan 15, 2018
The error looked like this:
nickvergessen commentedon Jan 15, 2018
server/lib/private/legacy/app.php
Lines 237 to 243 in e3c0fd6
Check the exception for some types?
nickvergessen commentedon Jan 15, 2018
Or just change getAlwaysEnabledApps to getShippedApps
blizzz commentedon Jan 15, 2018
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.
runout-at commentedon Jan 15, 2018
Since the last upgrade (12.0.4) following apps were disabled several times and i believe it's the same issue:
files_sharing
files_trashbin
nickvergessen commentedon Jan 16, 2018
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.