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
Hi - this might be related to #710 but I wasn't sure if it should be reopened or another ticket created, so went with the new ticket.
Basically there are two issues, the Chronos Desktop app is sometimes a few blocks behind when I view it in the browser. However when the app catches up it still doesn't seem to reflect the Upcoming Transactions number that is in the browser.
An assumption is also being made on my part that both bits of code (desktop or browser) are searching for upcoming transactions in the same window of time whether 12 hours, 24 hours or some other value.
In the first screenshot you will see that the desktop app is a few blocks behind that of the browser
In the second screen I took the screenshot after saving down the Basic and Detailed logs and noticed that the block numbers were now more in sync but the Upcoming Transactions number is still out of sync.
Hi - this might be related to #710 but I wasn't sure if it should be reopened or another ticket created, so went with the new ticket.
Basically there are two issues, the Chronos Desktop app is sometimes a few blocks behind when I view it in the browser. However when the app catches up it still doesn't seem to reflect the Upcoming Transactions number that is in the browser.
An assumption is also being made on my part that both bits of code (desktop or browser) are searching for upcoming transactions in the same window of time whether 12 hours, 24 hours or some other value.
In the first screenshot you will see that the desktop app is a few blocks behind that of the browser
In the second screen I took the screenshot after saving down the Basic and Detailed logs and noticed that the block numbers were now more in sync but the Upcoming Transactions number is still out of sync.
Attached are the log files also.
02 Basic Log at Oct 11 2018 115am EST.txt
03 Detailed Log at Oct 11 2018 116am EST.txt
The text was updated successfully, but these errors were encountered: