feat: add additional logging for database errors#44788
Merged
Conversation
feb7100 to
e4c74ef
Compare
This was referenced Apr 11, 2024
e4c74ef to
c84520e
Compare
including the stack trace of the current database transaction Signed-off-by: Robin Appelman <robin@icewind.nl>
c84520e to
7fbb981
Compare
sorbaugh
approved these changes
Jul 24, 2024
yemkareems
approved these changes
Jul 25, 2024
Member
Author
|
/backport to stable29 |
Member
Author
|
/backport to stable28 |
2 tasks
2 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.
Add
db.log_exceptionsconfig flag which will log any db exception in the nextcloud log regardless of it being cached in application code.These logs also include the stack trace of the current database transaction