@paoloardoino experiencing right now very frequent sequence gaps when using WS API with SEQ_ALL flag set? is it known issue? Didn't happen before, like never, or has something related to that feature changed? Thanks
-
-
Replying to @tardis_dev
hello, which websocket channel are you referring to?
1 reply 0 retweets 0 likes -
Replying to @paoloardoino
sorry wasn't precise it's occuring for trades channel, for example for BTCUST, still seeing it in the logs, every time for 'hb' message, what is interesting it works fine for derivatives instruments
1 reply 0 retweets 0 likes -
Replying to @tardis_dev
We're trying to investigate. Is it that the SEQ_ALL is applied also to `hb`? We didn't touch that code. Can you provide https://gist.github.com/ of what you're seeing?
1 reply 0 retweets 0 likes -
Replying to @paoloardoino
Thanks! I'll provide code snippet soon when get back home, hb always had sequence number provided as far as I remember
1 reply 0 retweets 0 likes -
Replying to @tardis_dev
Ok but I'm seeing s equencing for `hb` from my tests. A snippet would be really awesome. Thanks a lot!
1 reply 0 retweets 0 likes -
Replying to @paoloardoino
trying to reproduce it right now, but since last Bitfinex server restart (Stopping. Please try to reconnect) it's gone, still monitoring but seems stable since like 10 minutes or so, thanks!
1 reply 0 retweets 2 likes -
Replying to @tardis_dev @paoloardoino
14h later still rock solid, not even single sequence gap, thanks for the help Paolo, really appreciate it!
1 reply 0 retweets 0 likes -
-
Replying to @paoloardoino
sorry for being such pain, but it's started happening again today - sequence gaps for the trades channel
2 replies 0 retweets 0 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.