Skip to content

Node collector changes #572

@lassemand

Description

@lassemand

When node collector backend changes it values it may be the case that a user picking a node from the list of nodes in the ui picks a node which is no longer in the list provided by the backend resulting in an error to the user

To circumvent this several solutions could be considered:

  • Make a lazy list which contains history back in time about nodes with a certain TTL. We still show what the collector backend contains
  • Show an error explaining that the node no longer exists
  • Send forth what ever data we may have obtained from the list and show that

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions