-
Notifications
You must be signed in to change notification settings - Fork 9
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
feat: appeals undetermined transactions #657
base: main
Are you sure you want to change the base?
Conversation
…inalized rollup transaction
…op when appeal failed and succeeded
…ed state and add button also to modal
- Add N+2 validators, remove leader - Use latest data of transaction when in pending state and not the old one from the crawler - Write consensus data before setting status to have it updated in frontend when going to transaction info modal - Do not deploy contract when transaction was in the undetermined state
…eals-implement-sequential-appeals-fail
…8-appeals-undetermined-transactions
…sation of transaction
…undetermined-transactions
…nly check in appeal_window
…king on finalized state gave a small delay in showing when appeal failed and finality window was exceeded
@cristiam86 In the If you agree, I will add: |
@kstroobants We shouldn't emit messages when the transaction is undetermined. @kirilaa could you please confirm? |
true, the messages are emitted:
|
Quality Gate failedFailed conditions |
@@ -55,7 +56,7 @@ const handleSetTransactionAppeal = () => { | |||
watch( | |||
() => props.transaction.status, | |||
(newStatus) => { | |||
if (newStatus !== 'ACCEPTED') { | |||
if (newStatus !== 'ACCEPTED' && newStatus !== 'UNDETERMINED') { |
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.
@kstroobants what's the reason of this check? can't we rely in the appeal property of the transaction?
transaction = Transaction.from_dict( | ||
transactions_processor.get_transaction_by_hash(transaction.hash) | ||
) | ||
await ConsensusAlgorithm(None, msg_handler_mock).exec_transaction( |
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.
@kstroobants this seems like a different test, shouldn't we divide them into different ones?
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.
Minor comments that would be nice to solve
Fixes #638
What
Why
Testing done
Checks
Reviewing tips