This repository has been archived by the owner on Jul 27, 2022. It is now read-only.
fix: adds extra confirming of transactions #187
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
MaximPiessen
previously approved these changes
Feb 7, 2022
BouweCeunen
reviewed
Feb 7, 2022
MaximPiessen
approved these changes
Feb 7, 2022
BouweCeunen
approved these changes
Feb 7, 2022
SushantChandla
approved these changes
Feb 7, 2022
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.
Even when waiting for a transaction to hit a certain commitment
level, we were noticing that calls that happen right after would
sometimes return stale data.
If a transaction was included in slot #18 some of the calls would
sometimes return data from that was present at slot #17