kraken
broker/live-trade-ctl roaming support is borked, ws subscribe layer raises 'ESession:Invalid session'
... #14
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?
Moving between networks the
pikerd
sub-actorbrokerd
will raise the following upon reconnect to the 2nd net:DESIRED FIX
.kraken.broker.subscribe()
’s enter body, INCLUDING a request to get a new ws token, i.e. rerunning the code,which currently is sitting @ https://pikers.dev/pikers/piker/src/branch/fix_deribit_hist_queries/piker/brokers/kraken/broker.py#L579
That will implicitly trigger a new
.api.Client._private()
call beneath and hopefully avoid this stale session issue 🙏Also, thinking ahead, we should definitely aim for having at least a small suite of “roaming
brokerd
/datad
” tests for backends that can support it.More or less this should verify that each backend opting to use our
.data._web_bs.NoBsWs
provides a correctly implementedfixture
that can withstand net dropouts/changes.