Fix concurrency issue on devnet #8
Closed
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
thomas-nguy
requested review from
vladbochok and
StanislavBreadless
as code owners
thomas-nguy
changed the title
StanislavBreadless
approved these changes
Sep 4, 2023
vladbochok
approved these changes
Sep 4, 2023
StanislavBreadless
pushed a commit
that referenced
this pull request
Sep 14, 2023
Prepare the repo for open sourcing
|
The issue will be resolved with the boojum upgrade: #43 |
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.
When launching a devnet, it happens frequently that the block is committed, proved and executed within a single tx.
When the execution delay is equal to 0 (devnet setting) then it should allow the tx to be valid
Currently because of the strict equality, it will trigger the circuit breaker