Open MichelSantos opened 5 years ago
kenCode (on telegram) reported the issues. Great initiative @MichelSantos thank you! :)
@sschiessl-bcp you've been working on this the most. Care to take a look at this?
For Information: Today I get this condition despite my unix system time being correct and in sync. Yesterday this was not a problem.
I'm in the uk (BST UTC+1).
The devtools console shows me:
auto selecting to wss://eu-central-1.bts.crypto-bridge.org
app.9bf820f14e671fbb5f33.js:1 Connecting to wss://eu-central-1.bts.crypto-bridge.org
6app.9bf820f14e671fbb5f33.js:1 not yet synced, retrying in 1s
app.9bf820f14e671fbb5f33.js:1 willTransitionTo err: Error: ChainStore sync error, please check your system clock
This happens on two different machines so is presumably an issue with the EU Central Cryptobridge node, but I have no way to select another.
There was a short downtime yesterday for all nodes, and some might still be resyncing. Please try again.
Describe the bug A user has reported getting the white screen of death (WSOD) because his clock time was not synchronized with standard time (approximately 5 minutes of difference). This occurred when starting the reference wallet. No indication about the problem was indicated except through the debug log.
To Reproduce Steps to reproduce the behavior:
Expected behavior The user should be notified that his clock is off and that it requires synchronization.
Alternatively, if the user's clock is synchronized within some tolerance but the problem is with the clock of the connected node (#1228, #1826, #2091) then the user should be notified of this problem and be offered an opportunity to select another node.
Screenshots The user provided a screen shot of the logs that contained the following message:
Desktop:
**Web Wallet The same behavior was reported by the user when accessing the web wallet that was present at wallet.bitshares.org
Additional context The behavior was resolved after the user synchronized his system clock to standard time