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

Remove potentially redundant log column for light client #8519

Closed
fulldecent opened this issue Apr 30, 2018 · 1 comment · Fixed by #8962
Closed

Remove potentially redundant log column for light client #8519

fulldecent opened this issue Apr 30, 2018 · 1 comment · Fixed by #8962
Labels
F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. M4-core ⛓ Core client code / Rust. P9-somedaymaybe 🌞 Issue might be worth doing eventually.
Milestone

Comments

@fulldecent
Copy link

This column is duplicated with this column. The end result is wasted screen space. And in my case unnecessary.

screen shot 2018-04-30 at 5 37 12 pm

Remove the latter to save space.

@tomusdrw
Copy link
Collaborator

With full node, the second column shows the highest block number seen in the network.

You seem to be running light node, perhaps it indeed makes sense to remove that for light client.

@tomusdrw tomusdrw added F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. M4-core ⛓ Core client code / Rust. labels Apr 30, 2018
@Tbaut Tbaut added the P9-somedaymaybe 🌞 Issue might be worth doing eventually. label May 2, 2018
@Tbaut Tbaut added this to the 1.12 milestone May 2, 2018
@folsen folsen changed the title Console output column duplicated Remove potentially redundant column for light client May 21, 2018
@folsen folsen changed the title Remove potentially redundant column for light client Remove potentially redundant log column for light client May 21, 2018
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. M4-core ⛓ Core client code / Rust. P9-somedaymaybe 🌞 Issue might be worth doing eventually.
Projects
None yet
3 participants