fully synced miner shows incorrect info on boot

[shawaj]

After rebooting:

This is the same device a few minutes later:

[ryanteck]

What's the issue? Likely diagnostics booted up before the miner, so that the values were 0. So it's working as intended?

…

On Thu, 3 Jun 2021, 02:59 Aaron Shaw, ***@***.***> wrote: After rebooting: [image: image] <https://user-images.githubusercontent.com/3359418/120574481-4b352c80-c417-11eb-8130-091052ae01ca.png> This is the same device a few minutes later: [image: image] <https://user-images.githubusercontent.com/3359418/120574650-a2d39800-c417-11eb-9850-df43a3faab1d.png> — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#50>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAINW2NF5TXA5IV2Z7LVJ3LTQ3OYBANCNFSM457Z3MLA> .

[shawaj]

I think after boot it should not default to 0% 0/xxx blocks because this will just confuse people.

If it can't get the diagnostics from the miner due to it booting up before it should have an error message saying "Waiting for miner" or similar

[ryanteck]

It's a bit of a mixed one as primarily all this page does is present a human readable form of the diagnostics json file which I then planned to implement into the BTLE software to speed that up of which if I was to edit the data which is stored to something which isn't a number then could cause that to break.

I could possibly have it set to another number which isn't 0, then test on the HTML generation if the number is that display waiting for miner.

[ryanteck]

It looks like it defaults to 1 at very first initial setup, so I can have the test be if it is 0 to say it's waiting for a response.

[ryanteck]

I've added in a test so if it is still loading that it now displays that it is still loading.