scheduled method callbacks and multiple WebSocketApps about websocket-client

[gborrageiro]

Great, thank you, I will let you know how it goes!

…

On Sun, 30 Jul 2023, 13:50 bubbleboy14, ***@***.***> wrote: Yes, you can set up as many timeouts as you want, with whatever intervals. Ok, so periodically you're resubscribing with a slightly different URL. My recommendation is to manually teardown/close the old WebSocketApp before creating a new one, rather than calling rel.abort(). LMK how it goes! — Reply to this email directly, view it on GitHub <#937 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEU5P4HKIUBSYVMGMEBLSZDXSZKAHANCNFSM6AAAAAA25EQQLU> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[gborrageiro]

It looks like your suggestions have worked perfectly, @bubbleboy14 .
Thanks again, as this has saved me a load of time.

By the way, when I installed websockets-client via pypi (I use miniconda), running

pip install websockets-client

installed a 2010 version, 0.53 release.

I only noticed the old release as more recent parameters which are shown in the documented examples, didn't work.
It was only when I ran the following, that I could install the latest 1.6.1 version:

pip install websocket-client[test, optional]

[bubbleboy14]

Hello @gborrageiro.

The first thing I notice is that "rel.abort()" is your first line - you probably don't need or want that there.

If the purpose of the threading.Timer() is to call a function periodically, you can accomplish that with rel.timeout() - here's what the threading.Timer part would look like with rel.timeout():

rel.timeout(24 * 60 * 60 - 60, self.subscriptions)

And the "self.subscriptions" function should return True, which basically tells rel to reschedule it.

LMK how it goes!

[gborrageiro]

Thanks for your reply @bubbleboy14, Can I schedule multiple rel timeouts, each with differing callback times? When I get disconnected from my WS connection, should I not run rel.abort() so that I can run the two WS apps with rel? The purpose of subscriptions() is to initially setup the WS apps, but also to reinitialise the WS connections in case they get disrupted. Best regards Gabriel

…

On Sun, 30 Jul 2023, 13:12 bubbleboy14, ***@***.***> wrote: Hello @gborrageiro <https://github.com/gborrageiro>. The first thing I notice is that "rel.abort()" is your first line - you probably don't need or want that there. If the purpose of the threading.Timer() is to call a function periodically, you can accomplish that with rel.timeout() <https://github.com/bubbleboy14/registeredeventlistener#signals-and-timers> - here's what the threading.Timer part would look like with rel.timeout(): rel.timeout(24 * 60 * 60 - 60, self.subscriptions) And the "self.subscriptions" function should return True, which basically tells rel to reschedule it. LMK how it goes! — Reply to this email directly, view it on GitHub <#937 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEU5P4FNO665LQJGJEUCJ3LXSZFTHANCNFSM6AAAAAA25EQQLU> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[gborrageiro]

I forgot to add that one of the socket streams is authenticated, so the URL actually changes, hence the notion of having to resubscribe through the subscription method that I defined, with new WS app subscriptions. Thanks Gabriel On Sun, 30 Jul 2023, 13:24 gabriel borrageiro, ***@***.***> wrote:

…

Thanks for your reply @bubbleboy14, Can I schedule multiple rel timeouts, each with differing callback times? When I get disconnected from my WS connection, should I not run rel.abort() so that I can run the two WS apps with rel? The purpose of subscriptions() is to initially setup the WS apps, but also to reinitialise the WS connections in case they get disrupted. Best regards Gabriel On Sun, 30 Jul 2023, 13:12 bubbleboy14, ***@***.***> wrote: > Hello @gborrageiro <https://github.com/gborrageiro>. > > The first thing I notice is that "rel.abort()" is your first line - you > probably don't need or want that there. > > If the purpose of the threading.Timer() is to call a function > periodically, you can accomplish that with rel.timeout() > <https://github.com/bubbleboy14/registeredeventlistener#signals-and-timers> > - here's what the threading.Timer part would look like with rel.timeout(): > > rel.timeout(24 * 60 * 60 - 60, self.subscriptions) > > And the "self.subscriptions" function should return True, which basically > tells rel to reschedule it. > > LMK how it goes! > > — > Reply to this email directly, view it on GitHub > <#937 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AEU5P4FNO665LQJGJEUCJ3LXSZFTHANCNFSM6AAAAAA25EQQLU> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >

[bubbleboy14]

Yes, you can set up as many timeouts as you want, with whatever intervals.

Ok, so periodically you're resubscribing with a slightly different URL. My recommendation is to manually teardown/close the old WebSocketApp before creating a new one, rather than calling rel.abort().

LMK how it goes!

[engn33r]

@gborrageiro I am confused why release 0.53 was installed with the install command you shared. If you have any more information about how that happened, it might help explain some recent issues this month from conda users. This conda repo may be related.

[gborrageiro]

Hi @engn33r, I didn't do anything funky. It was literally a case of create a new env and install packages; we end up with the .53 version. conda create -n my_env python=3.10 -y pip install -r requirements.txt where the requirements file contains websockets-client. It's only when I set websockets-client[optional] that the correct package was found. regards Gabriel

…

On Sun, 30 Jul 2023, 17:20 engn33r, ***@***.***> wrote: @gborrageiro <https://github.com/gborrageiro> I am confused why release 0.53 was installed with the install command you shared. If you have any more information about how that happened, it might help explain some recent issues this month from conda users. This conda repo <https://github.com/conda-forge/websocket-client-feedstock> may be related. — Reply to this email directly, view it on GitHub <#937 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEU5P4D3LV27HKMMDZ7AE4TXS2CWLANCNFSM6AAAAAA25EQQLU> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[engn33r]

@gborrageiro Thanks for the update. When I tried to replicate with:

conda create -n my_env python=3.10 -y
pip install websocket-client

websocket-client version 1.6.1 was installed. So I expect the issue is either in the requirements.txt or your pip configuration.

One last clarification: you are writing websockets-client in your posts, but this project is websocket-client (no "s" after socket). If your install commands used websockets-client (with "s") then there could be some typosquatting involved

[gborrageiro]

Yep, my bad, it's websocket-client.

…

On Sun, 30 Jul 2023, 19:53 engn33r, ***@***.***> wrote: @gborrageiro <https://github.com/gborrageiro> Thanks for the update. When I tried to replicate with: conda create -n my_env python=3.10 -y pip install websocket-client websocket-client version 1.6.1 was installed. So I expect the issue is either in the requirements.txt or your pip configuration. One last clarification: you are writing websockets-client in your posts, but this project is websocket-client (no "s" after socket). If your install commands used websockets-client (with "s") then there could be some typosquatting involved — Reply to this email directly, view it on GitHub <#937 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEU5P4C4FQR2OEMXNJSL35DXS2UR7ANCNFSM6AAAAAA25EQQLU> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[gborrageiro]

here's my full requirements file: aiohttp bitmex bitmex-ws bravado certifi cmake cython gitpython influxdb influxdb_client ipython Jinja2 joblib nbformat matplotlib numpy pandas[performance,computation,excel] psutil pyinstaller pytz pyyaml ratelimit redis[hiredis] rel requests requests_cache scikit-learn scipy seaborn statsmodels tables tk tqdm websocket-client[test, optional] wsaccel websockets wget xlrd xlsxwriter On Sun, 30 Jul 2023 at 20:06, gabriel borrageiro < ***@***.***> wrote:

…

Yep, my bad, it's websocket-client. On Sun, 30 Jul 2023, 19:53 engn33r, ***@***.***> wrote: > @gborrageiro <https://github.com/gborrageiro> Thanks for the update. > When I tried to replicate with: > > conda create -n my_env python=3.10 -y > pip install websocket-client > > websocket-client version 1.6.1 was installed. So I expect the issue is > either in the requirements.txt or your pip configuration. > > One last clarification: you are writing websockets-client in your posts, > but this project is websocket-client (no "s" after socket). If your install > commands used websockets-client (with "s") then there could be some > typosquatting involved > > — > Reply to this email directly, view it on GitHub > <#937 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AEU5P4C4FQR2OEMXNJSL35DXS2UR7ANCNFSM6AAAAAA25EQQLU> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >

[gborrageiro]

I found the offending package, `bitmex-ws`. Finally, I updated my requirements file as follows, which seems to have done the trick: ``` websocket-client[test,optional] >= 1.6.1 ``` Best regards Gabriel On Sun, 30 Jul 2023 at 20:10, gabriel borrageiro < ***@***.***> wrote:

…

here's my full requirements file: aiohttp bitmex bitmex-ws bravado certifi cmake cython gitpython influxdb influxdb_client ipython Jinja2 joblib nbformat matplotlib numpy pandas[performance,computation,excel] psutil pyinstaller pytz pyyaml ratelimit redis[hiredis] rel requests requests_cache scikit-learn scipy seaborn statsmodels tables tk tqdm websocket-client[test, optional] wsaccel websockets wget xlrd xlsxwriter On Sun, 30 Jul 2023 at 20:06, gabriel borrageiro < ***@***.***> wrote: > Yep, my bad, it's websocket-client. > > On Sun, 30 Jul 2023, 19:53 engn33r, ***@***.***> wrote: > >> @gborrageiro <https://github.com/gborrageiro> Thanks for the update. >> When I tried to replicate with: >> >> conda create -n my_env python=3.10 -y >> pip install websocket-client >> >> websocket-client version 1.6.1 was installed. So I expect the issue is >> either in the requirements.txt or your pip configuration. >> >> One last clarification: you are writing websockets-client in your posts, >> but this project is websocket-client (no "s" after socket). If your install >> commands used websockets-client (with "s") then there could be some >> typosquatting involved >> >> — >> Reply to this email directly, view it on GitHub >> <#937 (comment)>, >> or unsubscribe >> <https://github.com/notifications/unsubscribe-auth/AEU5P4C4FQR2OEMXNJSL35DXS2UR7ANCNFSM6AAAAAA25EQQLU> >> . >> You are receiving this because you were mentioned.Message ID: >> ***@***.***> >> >

[engn33r]

@gborrageiro thanks I opened an issue on that other project