-
Notifications
You must be signed in to change notification settings - Fork 8.9k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[FAB-16879] Add stack trace to couchdb http errors (#1048)
If there is http error calling couchdb, no context was provided to higher level code that handles the errors. This change adds stack trace to the http error at the point that the error is raised, so that admins can identify what was going on upon hitting the error. In most places, the higher level error handlers are already printing stack trace, if available. This change adds the stack trace printing to OpenLeder() error handling, e.g. if there is an error during recommit lost block path. Also, for each of the points in ledger code where go routines are used, if stack trace was added in the go routine error, the stack would only be available from the point the go routine was called and lower. This is resolved by also adding stack trace to errors that are returned from go routines. Signed-off-by: David Enyeart <enyeart@us.ibm.com>
- Loading branch information
Showing
4 changed files
with
6 additions
and
4 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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