Skip to content

fail loudly if we can't resolve nodes in global config #792

Description

@0xdeafbeef

Motivation

Network global config was updated, but node global config is old. After restart, it's stuck because it doesn't know about new bootstrap peers.

Solution

If all nodes in the global config are dead (you can't ping any node from the list), panic and shout at the user.
It should be easier to understand then

Image

Metadata

Metadata

Assignees

No one assigned

    Labels

    C-networkNetwork moduleP-mediumMedium priorityS-featureSeverity: feature. This is adding a new feature.

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions