Skip to content

test results #6

Open
Open

Description

@juliangruber

I was seing some weird behavior with level-merkle and created a repo to reproduce:

https://github.com/juliangruber/level-merkle-test

With $ node test.js <number of parties> you can spawn n processes that replicate a leveldb over tcp and each second one of the nodes stores a new value. Each node outputs on stdout when a new value gets added.

Can you see whether that's intended behavior (i.e. bad use case) or there's something wrong?

Also see the comments in https://github.com/juliangruber/level-merkle-test/blob/master/index.js for things I found odd.

Activity

  1. juliangruber commented on Oct 17, 2013

    @juliangruber
    ContributorAuthor

    I modified the tests, so node a initially already has some data, but that doesn't get replicated.

  2. dominictarr commented on Oct 17, 2013

    @dominictarr
    Owner

    I'm currently in the process of rewriting this to use the merkle-stream module, so I'm not gonna fix the bugs as they are currently there, but I should be able to use your test script.

  3. juliangruber commented on Oct 17, 2013

    @juliangruber
    ContributorAuthor

    cool!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions