This repository has been archived by the owner on Jan 15, 2024. It is now read-only.
relayer: retry after "nonce too low" errors #1204
Merged
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
|
Build errors seem unrelated to this PR. Maybe ubuntu servers are having issues? Will retry later. |
There are no more updates for impish as of July 14th. https://fridge.ubuntu.com/2022/07/19/ubuntu-21-10-impish-indri-end-of-life-reached-on-july-14-2022/
|
Fix for build in #1205 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
We occasionally get a "nonce too low" error. I'm not 100% sure why this happens but it's possible that a transaction was submitted a bit earlier and got mined quickly enough for the subsequent transaction to have a nonce that is in fact too low. It could also be that we are sometimes getting an outdated response on the transaction count query that ethers is using to determine the nonce.
In any event, I think it makes sense to retry.
Example error log on datadog link.