Fix other operation fail after key_update fail and rollback #81
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
OuyangHang33
force-pushed
the
fix_after_rollback_other_operation_fail
branch
3 times, most recently
from
4e32fde
to
692fba8
Compare
Signed-off-by: OuyangHang33 <hank.ouyang@intel.com>
OuyangHang33
force-pushed
the
fix_after_rollback_other_operation_fail
branch
from
692fba8
to
5a0279b
Compare
jyao1
approved these changes
Apr 25, 2024
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.
Ref: #7
Fix this scenario:
After responder receive the incorrect UpdateAllkeys request and send error message with S3 old key, the requester will do rollback and use S3 old key to decode message. The other operation will be passed after keys rollback.