You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current behavior
In Gridcoin Wallet, I open it up, go to Diagnostics, and it reports Check Estimated Time To Stake as %1 days, but only when it's greater than 45 days (and highlighting yellow). When it's less than 45 days, it displays correctly (for example as 44.2 days).
Expected behavior
It should be showing a numerical value instead of %1
Steps to reproduce:
Run the diagnostics (on a wallet with ETTS greater than 45 days, and less than 90 days. (Wouldn't know if it would reproduce the error if greater than 90 days, someone else would have to check that)
Screenshots
Gridcoin version
Windows v5.4.5.0 - was also evident in 5.4.4 and 5.4.3, can't remember possibly also in an earlier release? I wasn't always an issue though.
Machine specs
Extra information
The text was updated successfully, but these errors were encountered:
This is already fixed. Above PR merged into the development branch. The fix will be in the next release. Thank you for taking the time to document the issue! :)
Bug Report
Current behavior
In Gridcoin Wallet, I open it up, go to Diagnostics, and it reports Check Estimated Time To Stake as %1 days, but only when it's greater than 45 days (and highlighting yellow). When it's less than 45 days, it displays correctly (for example as 44.2 days).
Expected behavior
It should be showing a numerical value instead of %1
Steps to reproduce:
Run the diagnostics (on a wallet with ETTS greater than 45 days, and less than 90 days. (Wouldn't know if it would reproduce the error if greater than 90 days, someone else would have to check that)
Screenshots
Gridcoin version
Windows v5.4.5.0 - was also evident in 5.4.4 and 5.4.3, can't remember possibly also in an earlier release? I wasn't always an issue though.
Machine specs
Extra information
The text was updated successfully, but these errors were encountered: