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
The thing is, when head block time of a node is some behind your local clock, it's possible that the node is out of sync, it's also possible that your local clock is too fast, even both. How the lib would know which one is wrong if there is no more info?
I just got an idea: the API server also returns server time E.G. via HTTP response header, perhaps we can use it to check what's the real reason.
If a node is out of sync, user still sees the "Sync clock" issue. Also include the chain head block and time in the thrown error.
bitsharesjs/lib/chain/src/ChainStore.js
Line 151 in 6bad1cf
The text was updated successfully, but these errors were encountered: