Skip to content

JDC fallback engine does not have a visual representation #129

@lucasbalieiro

Description

@lucasbalieiro

We need to think on how to handle the fallback scenarios of JDC:

  • When one of the upstreams fails the fallback upstream is called
  • If all upstream fails the JDC falls back to solo mining.

From the sv2-ui prespective we can only know this from parsing the logs.

As an example, the AxeOS just accept two upstreams and if the main one fails it pops up a yellow banner:

Image

Metadata

Metadata

Assignees

No one assigned

    Labels

    pendingpending decision making, do not tackle this issue

    Projects

    Status

    Todo 📝

    Status

    Todo 📝

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions