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
Use int64 in memoryMerkleTree #321
Conversation
b84f1e9
to
01fb5cc
Compare
Can you investigate the travis failure first. |
The Travis failure needs to be fixed by a more comprehensive refactor of the NewLogStorage API. |
Fixing the tests should be the priority to avoid introducing additional issues. |
Fixing in #327 |
The tests are passing now. Is this PR ready to go? |
I looked at it yesterday. I'll have another look later today.
…On 27 January 2017 at 09:35, Gary Belvin ***@***.***> wrote:
The tests are passing now. Is this PR ready to go?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#321 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AMv2T0B8SXcZ5qPXM_kszJv1idEhSrTMks5rWbpbgaJpZM4LtYMd>
.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks OK. However in case you're planning to test at scale I should probably point out that this is a complete tree and there won't be enough RAM available to construct a tree large enough to require int64.
I'm adding a proper LogVerifier next. |
This is a PR in preparation for building a LogVerifier.
We need a common set of tree functions to use in the
merkle
package