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
Instead printing the error page, we can keep logging this error and throwing the Exception again. Since we have a global catch, we would not end up in a blank page, so it should be safe to do so.
@blizzz Sounds good. And we should use our global exception handling where it is useful. Maybe not log the error there but add the information to the Exception (use HintException) and then it will be displayed to the user (if debug session) and written to the log in the global exception handling mechanism. Am I correct @LukasReschke
An uncatched exception will be displayed fully to the user if debug session, otherwise a generic error page is shown. An Hint Exception will show the hint to the user.
In that part https://github.com/owncloud/core/blob/master/lib/private/db/adapter.php#L74 the Adapter catches the Exception as delivered by Doctrine and outputs an error page. That makes application unable to respond properly on database issues.
Instead printing the error page, we can keep logging this error and throwing the Exception again. Since we have a global catch, we would not end up in a blank page, so it should be safe to do so.
Opinions? @DeepDiver1975 @MorrisJobke @butonic
The text was updated successfully, but these errors were encountered: