-
-
Notifications
You must be signed in to change notification settings - Fork 57
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
feat(rpc): handle exceptions by returning a proto and non-200 #6402
Merged
Conversation
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
❌ 1 Tests Failed:
View the top 1 failed tests by shortest run time
To view individual test run time comparison to the main branch, go to the Test Analytics Dashboard |
volokluev
reviewed
Oct 9, 2024
volokluev
reviewed
Oct 9, 2024
colin-sentry
force-pushed
the
proto_errors
branch
from
October 10, 2024 15:59
ecf93e5
to
e6b283d
Compare
colin-sentry
force-pushed
the
proto_errors
branch
from
October 10, 2024 17:43
e6b283d
to
4f6e974
Compare
colin-sentry
force-pushed
the
proto_errors
branch
from
October 10, 2024 17:53
c102652
to
9066cfa
Compare
volokluev
reviewed
Oct 10, 2024
volokluev
reviewed
Oct 10, 2024
colin-sentry
force-pushed
the
proto_errors
branch
from
October 10, 2024 19:20
7ba56a4
to
32fe7e5
Compare
volokluev
approved these changes
Oct 10, 2024
volokluev
added a commit
that referenced
this pull request
Oct 11, 2024
In #6402 I asked to put as [little of the error handling logic into the flask layer as possible](#6402 (comment)) but it went too far in the other direction and bled the flask object into the RPC code (which was not the intention). This PR removes the flask `Response` object out of the RPC code
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.
Fixes https://github.com/getsentry/eap-planning/issues/60 (on the snuba side, at least)