BM-664: Handle "already known" error during fulfillment calls #422
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
github-actions
bot
changed the title
willpote
changed the title
willpote
requested review from
capossele,
Wollac,
zeroecco,
austinabell,
willemolding,
rlukata and
a team
as code owners
|
🚀 Documentation Preview Deployment URL: https://boundless-documentation-5fjdsget2-risczero.vercel.app Updated at: 2025-03-31 14:37:23 UTC |
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
This code addresses:
which leads the broker to treat it as a failure and try again, getting
Note there doesn't seem to be an easy way to handle this error generally, each type of transaction will require special treatment. This PR starts with the known error that we've hit.