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
After running the feeeder for a while it may happen that the socket connection is dropped unexpectedly by Kraken (Cloudflare actually), and the service correctly tries to establish a new connection, and keeps feeding the daemon as expected.
Sometimes, though, the feeder seems to not feed the price received from Kraken but keeps using the same outdated price.
Seems that this does not only happen with kraken: we should try to refactor the code to try to prevent prices not in sync with what the socket is giving to us
After running the feeeder for a while it may happen that the socket connection is dropped unexpectedly by Kraken (Cloudflare actually), and the service correctly tries to establish a new connection, and keeps feeding the daemon as expected.
Sometimes, though, the feeder seems to not feed the price received from Kraken but keeps using the same outdated price.
Check these logs for example:
We need to investigate why this happens and also why it happens only sometimes and not all the times for instance.
The text was updated successfully, but these errors were encountered: