Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • duniter duniter
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 190
    • Issues 190
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • nodes
  • typescript
  • duniterduniter
  • Issues
  • #928

Closed
Open
Created Apr 04, 2017 by inso@InsoleetReporter

gtest and g1 nodes communicating

Hello,

I just saw the following logs in sakia :

DEBUG:network:handle_new_node:Stacking new peer document : 77mfxsDcX8JZKHD9fBC9wNtM1R7Yj3WA27DsY7kyrePX
DEBUG:network:discovery_loop:New node found : 77mfx
DEBUG:network:discovery_loop:Error : Node is working for gtest currency, but should be g1

What do you think about it ?

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking