Replies: 9 comments 4 replies
-
I think a parameter like Activating this parameter could call a new function like |
Beta Was this translation helpful? Give feedback.
-
Combine it with |
Beta Was this translation helpful? Give feedback.
-
there is already a thread which could do that job: |
Beta Was this translation helpful? Give feedback.
-
It seems That way it works: https://github.com/LUCIT-Systems-and-Development/unicorn-binance-websocket-api/blob/master/example_remove_streams_from_manager.py So we have to improve |
Beta Was this translation helpful? Give feedback.
-
Perfect, thank you! |
Beta Was this translation helpful? Give feedback.
-
Hey Oliver, |
Beta Was this translation helpful? Give feedback.
-
No, i will update the full suite asap... |
Beta Was this translation helpful? Give feedback.
-
In the next release (>1.42.0) this will work:
|
Beta Was this translation helpful? Give feedback.
-
Disccusion about the implementation of deleting old streams: #307 |
Beta Was this translation helpful? Give feedback.
-
Hi Guys,
given the following simple code:
When it is executed, entries for this particular stream_id are made at least in the following dictionaries (maybe in more, these were the ones I've quickly been able to find):
After stopping the stream with the
websocket_manager.stop_stream(stream_id)
command, the entries for this stream_id in the different dictionaries are still existing. There is a functionwebsocket_manager.delete_stream_from_stream_list(stream_id)
to remove the stream_id entry from thewebsocket_manager.stream_list
dicionary, but as far as I know there are no functions to delete the stream_id from all the other dictionaries.Wouldn't it make sense to implement (a) function(s) to remove a stream_id completely from the
websocket_manager
, so the manager can be properly cleaned up? Otherwise these dictionaries will grow a lot, if several streams will be created and stopped over some time.Best regards
Sebastian
Beta Was this translation helpful? Give feedback.
All reactions