Properly scope state/state refs to download/reuse #385
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.
There had been a corner case where a trusted peer sends inconsistent states and state refs, because the exact times to get both data from the store can subtly differ each other. In order to avoid that specific case, I added filtering options named
onlyAfter
/ignoreAfter
toListAllStateReferences()
method, and madeSwarm
to query state refs with a strict scope so that state refs to send are consistent with states to send.