-
Notifications
You must be signed in to change notification settings - Fork 812
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
Fix log for archival #5819
Fix log for archival #5819
Conversation
Pull Request Test Coverage Report for Build 018e809c-3d58-41a7-b684-2d08f136e522Details
💛 - Coveralls |
Codecov Report
Additional details and impacted files
... and 14 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
|
@@ -89,11 +89,17 @@ func uploadHistoryActivity(ctx context.Context, request ArchiveRequest) (err err | |||
if err == nil { | |||
return nil | |||
} | |||
if err.Error() == errUploadNonRetriable.Error() { | |||
logger.Error(carchiver.ArchiveNonRetriableErrorMsg, tag.ArchivalArchiveFailReason("got non-retryable error from history archiver")) | |||
if errors.Is(err, errUploadNonRetriable) { |
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.
Superfically seems fine, but to double check: are we returning that exact error value?
Comparing strings is a looser check in many common ways, so generally this would be less likely to be true than it was before. Since I don't think we have wrapped errors here. (Or do we? This looks isolated enough that it seems possible anyway)
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.
I don't know what error we're returning because the log isn't showing anything useful, it's not got the error tag
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.
I did check this is coverd by a unit test before changing the errors.Is, I could remove it if it's a concern, but I don't really see a lot of values in jsut string comparing like this
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.
Since it is affecting only staging, maybe you could merge this from your custom branch to verify if it resolves the issues/helps identifying the root cause?
What changed?
The log to work out what's nonretriable is not logged
Why?
How did you test it?
Potential risks
Release notes
Documentation Changes