Skip to content

Detected conflict caused consistent crashes #81

@bbenligiray

Description

@bbenligiray
Parsing peers...
Parsed ... peers!
Preparing to connect...
[hypercore] conflict detected in 5b8f...6c55 (writable=false,quorum=1)
Ready to connect all peers!
.../hinter-core/node_modules/hypercore/index.js:219
      throw SESSION_CLOSED('Cannot make sessions on a closing core', this.discoveryKey)
       

This was consistently happening at startup. I removed the chokidar incoming directory watcher, ran this modified hinter-core (which resolved the conflict with no message), then got back to running the original v0.2.0 release with no further issues.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions