Drotak

I had to update my node version to the newest node version. You can see the current version with `nvm ls-remote` and then you can install it with `nvm install...

I also stumbled across this and realized after some debugging that there are a view issues here. For debugging I just simulated a connection loss with removing my lan cable....

> debug log: > >   This error seems to occur when the TCP connection was lost, please see: https://websockets.readthedocs.io/en/latest/howto/faq.html#what-does-connectionclosederror-no-close-frame-received-or-sent-mean But as you can see my message above, the...

@wanth1997 Okay, so far I have found that an exception gets raised and it doesn't matter if I'm connected to the internet or not. The exception is raised in [line...

> Do you guys use the latest version of python-ftx? I can not reproduce this issue. > > My test code: > > ``` > from ftx import ThreadedWebsocketManager >...

I recognized now that even the reconnect inside the x seconds from `get_reconnect_wait` does not work with python3.9 but with python3.8 it works - the issue after the x seconds...

Just for clarification, this is inside test_python_ftx.py: ``` from ftx import ThreadedWebsocketManager def on_read(payload): print(payload) API = "" SECRET = "" wsm = ThreadedWebsocketManager(API, SECRET) wsm.start() # Un-auth subscribe name...

> @Drotak Plz test with the latest version 0.1.1 https://pypi.org/project/python-ftx/0.1.1/ I have installed v0.1.2 now and tested it with your example. Now it seems to work like expected! I'll test...

I have found another problem: When you use private websocket functions you need to sign in which works fine at the first connect. But when you reconnect, the same credentials...