-
Notifications
You must be signed in to change notification settings - Fork 5
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: Auctioneer geth #58
Draft
bharath-123
wants to merge
86
commits into
main
Choose a base branch
from
bharath/api-to-query-optimistic-block
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
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
Acquire a mutex lock and unlock while removing transactions from the mempool to avoid concurrent errors on the underlying maps. Changes made: 1. Acquire the pool mutex lock in `ClearAstriaOrdered` 2. Add a test in `legacypool_test.go` called `TestRemoveTxSanity` which adds a bunch of pending txs and removes them using `removeTx`. We use `ValidatePoolInternals` method to ensure that the pool state is not corrupted. This test is a sanity check for us to validate that `removeTx` works as intended and does not have adverse side effects. 3. Add a test in for the ExecutionAPI where we add an invalid tx which will have to be removed. We verify that the mempool is cleared completely after it --------- Co-authored-by: Bharath <[email protected]>
cherry-pick: fix: use mutex lock for tx removal (#51)
…op (#44) Causing an issue with dusk-10 and dawn. Note branch has been forked from `v0.14.1`. Should be merged to main to fix on head but will also need to use this branch to cut a `v0.14.2` for `dusk-10` and dawn
PR to merge release/0.14.3 into main
This is utilizing non finalized protos, merge main before merging
Tested locally by running: `docker run -v $PWD:/workdir protolambda/forkdiff:latest -repo=/workdir -fork=/workdir/fork.yaml -out=/workdir/index.html`
chore: Rebase flame with astria-geth
bharath-123
force-pushed
the
bharath/api-to-query-optimistic-block
branch
from
December 3, 2024 06:08
af19469
to
ffddf4b
Compare
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.
No description provided.