concordium / concordium-node-dashboard Goto Github PK

See issues discovered by dependabot https://github.com/Concordium/concordium-node-dashboard/security/dependabot

@limemloh

The node dashboard should mark which among the bakers in the list are also finalizers.

Bug Description
The field Finalization period average (EMA) was empty most of the time while catching up.

Steps to Reproduce
Start catching up with a node and view the consensus page on the dashboard.

Expected Result
Finalization period average (EMA) shows estimated finalization time.

Actual Result
Finalization period average (EMA) is empty most of the time. Once in a while it showed x seconds.

Versions

• Software Version: Version on most recent testnet
• OS: Linux
• Browser: Brave

• Baking information is not displayed when the node is a baker. This appears to be due to a change in the representation of credentials on accounts from a list to a map.

• Account information is not displayed when clicking on baker accounts.

• Block Explorer should be removed until the functionality is implemented.

• The warning time for received finalized block should not be displayed in millisecond accuracy.

• Warnings for failure to receive/finalize a block within a certain time should be relaxed. Suggest:

  • 5 minutes for block receipt. (With planned settings, this would happen about once in 1000 years coincidentally (if the bakers and network are fully operational).)

  • 10 minutes for block finalization.

• "Node only have 0 peers" -> "has"

• Copy to clipboard functionality does not work for account information or baker identities.

Description
Minor suggestions for improvements of the dashboard while catching up.

Steps to Reproduce
Look at the dashboard while the node is catching up.

Up to date with most peers
My node had caught up to ~50k blocks and the network was at ~70k.
The text said 7 out of 7 peers not up to date, which seems to suggest that the peers are also catching up.
Perhaps it should something like out of sync with 7 out of 7 peers.

Peer Catching Up
The peer you are currently receiving blocks from has the status Catching up, but its status suggests that the peer itself is trying to catch up.

Versions

• Software Version: Version used on most recent testnet
• OS: Linux
• Browser: Brave
• Mobile device, if applicable

As the title states.

It is somewhat there at the moment, but a fair amount of details are different.

Node dashboard should display its version in some places that is accessible to the user.

For orientation show epoch boundaries in the node dashboard.

Bug Description
The contract instances field is always 0.

Steps to Reproduce
View the account details on an account with contracts, fx by:

1. Becoming a baker
2. Deploy and initialize a contract with the baker account
3. Viewing the account details on the baker.

Expected Result
Contract instances: 1

Actual Result

Versions

• Software Version: Version on testnet
• OS: Linux
• Browser: Brave