New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Jesse websocket problem #371
Comments
~$ pip list |grep websockets |
Hi there. So basically the WebSocket stopped working without disconnecting. Where did you get |
P.S: I edited the post to add the correct formating to make it easier to read the logs. |
not in my logs, I am watching websocket msg by websocat (https://github.com/vi/websocat) on linux shell .. |
At
But your log at
Which means the private WS connection couldn't renew authentication as the logged file said which is the cause of the other problems you mentioned. I looked at my code to see how I'm logging it, the error handling of it is only handling a certain case that I could reproduce. There are two cases:
I added a new line to log the raw response of the exchange to look into it if it happened again. But there is a good change that it won't because I wrote this code a long time ago for Binance and this is the first time I get a report about this. The new line I added will be in the next version which I'll release in the coming days. If it happened again, please report it via the custom report button in the GUI because that way I get to see the raw exchange logs as well. |
I think it will be great and better if jesse can handle the websocket pushed listenKeyExpired event to delete the old key and got a new one... |
great, its so weird...and in my hongkong and japan servers,it happend once in a while.. |
We normally don't allow the listenKey to be expired in the first place. But I guess it's a good idea to implement handling for when it does happen. I'll add it. Thank you for the suggestion! |
This should be fixed with the upcoming release in the next few days. Thanks for reporting it. |
I have doing a further test on the old v0.34.0 version, it seem maybe the problem is "no WS connection reopened" Just FYI
we got the first listenKey here, but as the binance-docs,it usually will be listenKeyExpired after 24 hours cos:
at this moment, the umCjy2181cDzcKa7zB5rLErBdLidBtU3abdsq0YZ4ruMmkJrgF7qNLt6OoWd5ZlV listenKey is still alive
at this time, we got a new listenKey ...and the old listenKey listenKeyExpired...
after 17:05:00, Jesse submit go_short and go_long orders every 5m... all orders have been filled in exchange, but no anything on the Jesse side...like Jesse got nothing from the new listenKey websocket.. So I think maybe ,this is reason, no WS connection reopened with the new listenKey after old listenKey Expired...Jesse just used the Expired WS connection even we had got a new one... cos in the log, I cannot find anything like "Successfully reopened/opened WS connection to" the new listenKey msg.. |
The |
on the latest Jesse and live 0.34 version , nothing changed, the bug is still there I have sent report via the report button in the GUI , pls check thanks |
I think this can be fix, if jesse live plugin got websocket pushed listenKeyExpired event and handle it to delete the old key and got a new one...then close the old websocket ,reconnect websocket with the new key .. |
Pushing the |
Problem 1:
2022-09-15 07:48:14 listenKeyExpired (websocket pushed Event: User Data Stream Expired)
2022-09-15 08:25:54 ATOM-USDT, STOP order has been EXECUTED in exchange,But Jesse get nothing from websocket...
so the position is still there in Jesse (and forever) ,but in fact, no position in exchange anymore
Problem 2:
2022-09-15 09:00:00 DEFI-USDT, MARKET, sell has been EXECUTED in exchange,But Jesse get nothing from websocket...
2022-09-15 09:00:00 DEFI-USDT, MARKET, sell has been EXECUTED in exchange,But Jesse get nothing from websocket...
at last, in Jesse,there is no any DEFI-USDT position, but in exchange,there is 0.025 DEFI position...
The text was updated successfully, but these errors were encountered: