Added SAFE_EXCEPTION setting for strict error handling#7478
Open
Added SAFE_EXCEPTION setting for strict error handling#7478
Conversation
aKlimau
force-pushed
the
add-exception-handling
branch
2 times, most recently
from
bb7ebbb to
e2033a0
Compare
aKlimau
force-pushed
the
add-exception-handling
branch
5 times, most recently
from
882f41c to
be20dc7
Compare
aKlimau
force-pushed
the
add-exception-handling
branch
from
be20dc7 to
791089e
Compare
mdellweg
approved these changes
Mar 20, 2026
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
2 participants
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.
Added SAFE_EXCEPTION setting (defaults to False) for strict error handling, returning "Internal error" for every non PulpException if set to True.
Added deprecation warning for every non PulpException error message.
📜 Checklist
See: Pull Request Walkthrough