-
Notifications
You must be signed in to change notification settings - Fork 393
fix: return proper error rather than persisting error message on snapshot #1960
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
Conversation
…shot Signed-off-by: StandingMan <[email protected]>
CTTY
left a comment
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.
Hi @Standing-Man , thanks for the contribution! Looks good overall, I just have some minor feedbacks
Signed-off-by: StandingMan <[email protected]>
CTTY
left a comment
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!
Signed-off-by: StandingMan <[email protected]>
liurenjie1024
left a comment
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.
Thanks @Standing-Man for this fix, and @CTTY for review.
Which issue does this PR close?
What changes are included in this PR?
Avoid storing error message on snapshot, return error instead.
Are these changes tested?
Yes