types: Fix (*V2Transaction).DeepCopy mutating V2StorageProof #172
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.
@n8maninger noticed a flipped conditional in
validateV2FileContracts; after fixing it, I updatedTestValidateV2Blockto update the ChainIndexElement proofs, but the test still failed -- withcommitment hash mismatch, which is a weird error. Further investigation revealed thatV2Block.EncodeTowas mutating the block. Specifically, it wasnil-ing out theV2StorageProofhistory proof, which is why this wasn't caught earlier: since the test wasn't updating the proofs in the first place, they were alwaysnil, soEncodeTodidn't affect them. Anyway, this cascade of failures has all been fixed now :P