-
Notifications
You must be signed in to change notification settings - Fork 761
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
Hide internal errors from responses to client #5917
Merged
ychebotarev
merged 11 commits into
temporalio:main
from
ychebotarev:y_replace_fe_errors
May 22, 2024
Merged
Hide internal errors from responses to client #5917
ychebotarev
merged 11 commits into
temporalio:main
from
ychebotarev:y_replace_fe_errors
May 22, 2024
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
yiminc
reviewed
May 13, 2024
alexshtin
reviewed
May 14, 2024
yycptt
reviewed
May 14, 2024
yiminc
reviewed
May 15, 2024
yycptt
reviewed
May 16, 2024
dnr
reviewed
May 16, 2024
f0ca069
to
015adff
Compare
yiminc
requested changes
May 17, 2024
alexshtin
reviewed
May 17, 2024
alexshtin
reviewed
May 17, 2024
dnr
reviewed
May 18, 2024
yiminc
approved these changes
May 18, 2024
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.
lgtm now
ae71b98
to
f80cf96
Compare
Co-authored-by: Yichao Yang <[email protected]>
f80cf96
to
9002b37
Compare
stephanos
reviewed
Jun 10, 2024
ResourceExhaustedScopeHeader, reErr.Scope.String(), | ||
)) | ||
if headerErr != nil { | ||
logger.Error("Failed to add Resource-Exhausted headers to response", tag.Error(err)) |
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.
Shouldn't this be tag.Error(headerErr)
? 🤔
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.
What changed?
Add an interceptor for frontend service.
Interceptor will looks at error messages and replace unknown/internal messages to a common message
Why?
We are exposing/can expose to much of the internal details/customer info in errors.
Instead external error will be a simple message, and real error will be logged.
How did you test it?
Add unit test. Build/run tests
Potential risks
N/A
Documentation
N/A
Is hotfix candidate?
No