-
Notifications
You must be signed in to change notification settings - Fork 279
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] #3627: Transaction atomicity through cloning #3636
Merged
Erigara
merged 3 commits into
hyperledger-iroha:iroha2-dev
from
Erigara:transaction_atomicity
Jun 26, 2023
Merged
[fix] #3627: Transaction atomicity through cloning #3636
Erigara
merged 3 commits into
hyperledger-iroha:iroha2-dev
from
Erigara:transaction_atomicity
Jun 26, 2023
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
Erigara
added
Bug
Something isn't working
iroha2-dev
The re-implementation of a BFT hyperledger in RUST
labels
Jun 22, 2023
Erigara
requested review from
s8sato,
appetrosyan,
mversic,
Arjentix,
SamHSmith,
QuentinI,
outoftardis,
ilchu,
pesterev and
0x009922
as code owners
June 22, 2023 15:16
appetrosyan
previously approved these changes
Jun 22, 2023
Erigara
force-pushed
the
transaction_atomicity
branch
2 times, most recently
from
June 23, 2023 08:29
9a7d4ee
to
ec43083
Compare
Erigara
commented
Jun 23, 2023
appetrosyan
previously approved these changes
Jun 23, 2023
appetrosyan
reviewed
Jun 23, 2023
Erigara
force-pushed
the
transaction_atomicity
branch
from
June 26, 2023 06:57
ec43083
to
68ea995
Compare
appetrosyan
previously approved these changes
Jun 26, 2023
SamHSmith
previously approved these changes
Jun 26, 2023
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
QuentinI
previously approved these changes
Jun 26, 2023
Erigara
force-pushed
the
transaction_atomicity
branch
2 times, most recently
from
June 26, 2023 10:37
621e797
to
1d9fab1
Compare
appetrosyan
previously approved these changes
Jun 26, 2023
SamHSmith
previously approved these changes
Jun 26, 2023
Erigara
force-pushed
the
transaction_atomicity
branch
from
June 26, 2023 14:28
1d9fab1
to
a01ac30
Compare
appetrosyan
approved these changes
Jun 26, 2023
Signed-off-by: Shanin Roman <shanin1000@yandex.ru>
Signed-off-by: Shanin Roman <shanin1000@yandex.ru>
Signed-off-by: Shanin Roman <shanin1000@yandex.ru>
Erigara
force-pushed
the
transaction_atomicity
branch
from
June 26, 2023 14:31
a01ac30
to
dcb733b
Compare
QuentinI
approved these changes
Jun 26, 2023
SamHSmith
approved these changes
Jun 26, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
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.
Description
Apply transaction on cloned wsv and replace original one in case of successful execution.
Linked issue
Partially closes #3627
Benefits
Transaction execution within block is atomic.
Drawbacks
Cloning
wsv
will be costly in case of large wsv.However on the current benchmarks i don't see significant differences.
We should explore time/space tradeoffs for improved solution.
Consider implementation of transaction rollbacks.
Checklist
CONTRIBUTING.md