fix: deposit index calculation #11
Open
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
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.
The main fix is in 52ccccd
The send set of deposit indexes was incorrect because the function
get_unique_integers_betweenexpects the parameters to be ordered asget_unique_integers_between $lower $upper, however the values were being passed asget_unique_integers_between $upper $lower(becauseswap_index_accuracyshould always be smaller thandeposit_index_accuracy) so the deposits occurred at higher indexes than expected.The second commit refactors the code slightly allowing these indexes to be logged and seen.