This repository has been archived by the owner on Jun 20, 2024. It is now read-only.
Fix fetch_previous_block_hashes
going out of bounds
#12
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 current implementation attempts to access an out of bounds index when block number is > 255.
In particular, assume block 256 is given.
129 responses are returned.
Later, the responses are iterated over:
Assume
starting_offset = 254
. Whenidx
reaches128
,starting_offset - 2 * idx == -2
.Assume
starting_offset = 253
. Whenidx
reaches127
,starting_offset - 2 * idx == -1
.The new implementation provided here constructs the
Vec
of hashes iteratively, simplifying the logic and avoiding any indexing issues. The solution was tested and verified to be functionally equivalent to the current solution for blocks 0-255.