banderwagon: fix bytes uncompressed #71
Merged
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 PR fixes a situation found by @advaita-saha.
The situation is that
BytesUncompressed()
returns serialized bytes in a "trusted" fashion -- that is, simply the X and Y coordinates to be deserialized later. That's fine, but inSetBytesUncompressed(..., trusted bool)
we allow both trusted and untrusted deserialization. So if you callSetBytesUncompressed(...)
with the wrongtrusted
flag then it will fail.The reality is that we don't use uncompressed bytes serialization from untrusted sources in any place in geth (at least for now), so what I do here is to be a bit more clear about expectations in the API.
Concretely, rename to
BytesUncompressedTrusted()
which gives a clear signal that in the future those bytes can be deserialized withSetBytesUncompressed(..., true)
.I added a test that shows this case.