Debug verify status

[bogdanfazakas]

check banned, conditions and display

• verified if last job is succesful
• not verified for the rest

[andreip136]

In leaderboard table:

A check is displayed beside the benchmark score if node.latestBenchmarkResults.totalScore exists.

On node details page:

The node status is displayed with the following checks:

Banned

• only for node admins
• node.banned = true or now < node.bannedUntil or now < node.suspendedUntil

Not eligible

• only for node admins
• node.eligible != true

Verified

• node is not banned or suspended
• node.latestBenchmarkResults exists

Not verified

• missing node.latestBenchmarkResults or node is suspended/banned and user is not node admin

Since node.latestBenchmarkResults only reflects the most recent successful benchmark run and omits any later failed attempts, it can’t be fully relied upon to determine the current state of a node that was previously successful but has since failed to complete a benchmark.

On the client, for a single node (i.e. in the Node details page) we could fetch the actual latest benchmark job and check if it was successful. For the leaderboard table, fetching the latest benchmark job for each node on the displayed page is not ideal, but could be done as a temporary solution until we find a better one that probably involves changes on the backend.