-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
DmanV3 script not cleaning up all pending orders after close on HyperLiquid #7032
Comments
hi @tijsk Could you please provide config of your controller / controllers? |
Thanks, |
@nikspz Thanks for looking into this. Could this be because of a too low 'cooldown_time' setting? The default is 300, I've set it to 60. |
Wasn't fixed by changing this setting. Now trying to 'bb_long_threshold' to 0.9 instead of 1.0 |
Isn't the solution either. So I atm I'm out of idea's. Let me know if I can do something else. |
Okay will review logs later this week.
issues from the logs: 1.Failed to cancel order
|
Hi @nikspz, |
When stopping and exiting the instance and running it again these errors occur: 2024-05-28 21:03:11,250 - 15 - hummingbot.client.hummingbot_application - INFO - start command initiated. After deleting the database file this the script is starting again. Maybe this helps in finding the issue? |
Describe the bug
This is tested on the 1.28 development using HyperLiquid
While having the script running I've noticed that some orders of the previous executor are still present on the exchange. See attached screens of Hummingbot status and exchange graph.
When these "ghost orders" are hit and filled they are not taken into account by the Hummingbot script. Resulting in a difference in active amount and finally in a partial closure with a left over active order.
I'm not sure what the philosophy behind the scripts is, but it looks like it is only taking in account the actions from the script itself. Now that this bug is active it's not correcting itself with the actual data from the exchange. In my opinion the script should be based on the actual values on the exchange instead of its own interpretation of it.
Now the script has a 'filled_amount_quote' of 321 USD and the exchange has a "Position Value" of 451 USD.
Steps to reproduce
Release version
dev-1.28.0
Type of installation
Docker
Attach required files
The text was updated successfully, but these errors were encountered: