-
Notifications
You must be signed in to change notification settings - Fork 4.5k
Add exception chaining #37423
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
Open
shaheeramjad
wants to merge
4
commits into
apache:master
Choose a base branch
from
shaheeramjad:add-exception-chaining
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+17
−15
Open
Add exception chaining #37423
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
2e69b8e
Add exception chaining to preserve error context
shaheeramjad 1f94581
Merge remote-tracking branch 'upstream/master'
shaheeramjad f3b8a5f
Fix yapf formatting for logging.warning statement
shaheeramjad 6d55c01
Fix yapf formatting: put logging arguments on single line
shaheeramjad File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we're chaining the exception, do we still need to include the exception in the RuntimeError message?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same question exists below in this file as well
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With from e, the cause is in cause and the traceback, so we don’t need to include the exception in the message.
I kept it in because in many environments only the top-level exception message is logged or shown (e.g. in alerts or dashboards). In those cases, "Database operation failed" alone doesn’t tell you the real error, while f"Database operation failed: {e}" stays useful. It’s also a common Python pattern to add context and still include the original error in the wrapper message.
If you prefer to rely on the chain and keep messages minimal, I’m happy to change to e.g. raise RuntimeError("Database operation failed") from e and remove {e} from the message. Happy to follow whatever convention you prefer for this project.