Skip to content
This repository has been archived by the owner on Nov 6, 2020. It is now read-only.

Status bar has nonsensical states #6273

Closed
gavofyork opened this issue Aug 10, 2017 · 3 comments
Closed

Status bar has nonsensical states #6273

gavofyork opened this issue Aug 10, 2017 · 3 comments
Assignees
Labels
F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue.
Milestone

Comments

@gavofyork
Copy link
Contributor

I'm running:

  • Parity version: 1.7.0
  • Operating system: Any
  • And installed: Any

e.g.:
image

There are currently three criteria contributing to the overall status:

  • Chain synchronised (chain)
  • Connected peers (peers)
  • Time synchronised (time)

In reality, only two are needed and they should be combined in such a way:

  • Green iff peers && chain
  • Orange iff peers && !chain
  • Red otherwise.

The time being synchronised should be used only as a trouble-shooting mechanism, not as an indication of whether Parity Wallet is "good to go".

@gavofyork gavofyork added F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. M7-ui labels Aug 10, 2017
@gavofyork gavofyork added this to the 1.8 milestone Aug 10, 2017
@gavofyork gavofyork modified the milestones: 1.7, 1.8 Aug 10, 2017
@tomusdrw
Copy link
Collaborator

tomusdrw commented Aug 10, 2017

We also display a warning state if you are connected to only one peer, although it may be nonsensical for private chains.
I wanted to disable that check only on "non-public" networks, do you think it's better to disable it everywhere?

@5chdn
Copy link
Contributor

5chdn commented Aug 10, 2017

No, it's fine for private chains. Developers should certainly understand why their private network only has 1-2 peers.

@5chdn
Copy link
Contributor

5chdn commented Aug 10, 2017

This is related / should be merged with #6130

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue.
Projects
None yet
Development

No branches or pull requests

3 participants