Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: TreeD size and rows to discard calculation was wrong #1692

Merged
merged 1 commit into from
Apr 24, 2023

Conversation

vmx
Copy link
Contributor

@vmx vmx commented Apr 21, 2023

For the TreeD the amount of nodes for the full merkle tree and not for the subtrees needs to be used. The node_count variable was shadowed by another instance. This is fixed by renaming the initial variable.

For the TreeD the amount of nodes for the full merkle tree and not for
the subtrees needs to be used. The `node_count` variable was shadowed
by another instance. This is fixed by renaming the initial variable.
Copy link
Collaborator

@cryptonemo cryptonemo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch. Fortunately for TreeD it's a no-op. I wonder if in the future we should plumb None down instead, but given how merkletree is structured, makes sense for now.

@vmx
Copy link
Contributor Author

vmx commented Apr 24, 2023

Fortunately for TreeD it's a no-op.

What is a no-op? The rows to discard?

@vmx vmx merged commit 18d1de1 into master Apr 24, 2023
@vmx vmx deleted the tree-d-row-to-discard-fix branch April 24, 2023 09:17
@cryptonemo
Copy link
Collaborator

Fortunately for TreeD it's a no-op.

What is a no-op? The rows to discard?

The value passed in (the 'bug') isn't used.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants