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
Hyperliquid recreates reversing order on close #6948
Comments
I've ran into something similar. I closed the positions created by hummingbot via exchange front-end and then noticed that orders in the opposite direction with equal size and leverage were created. I was also using |
Reproduced on latest development (during the longrun with ~same config) |
Bounty: fix the issue with inconsistent position side / order creation |
can test whether there is any problem. If there is any problem, I will continue to repair it |
fixed, fix merged to latest development (dev-1.28.0) |
Describe the bug
When an order is closed (long or short) a new open is made in the opposite direction.
Occurs in Source and Docker installation, see attached logfile.
For more info send me a message on Discord, I'd like to help.
Steps to reproduce
Release version
1.26
Type of installation
Docker and Source
Attach required files
message.txt
Conf script
markets: {}
candles_config: []
controllers_config:
config_update_interval: 20
script_file_name: v2_generic_with_controllers.py
Conf controller
id: 3tfTznFJZwMPmXj9kCQvdrnChdsjpbsPDif9idf6WheJ
controller_name: dman_v3
controller_type: directional_trading
manual_kill_switch: null
candles_config: []
connector_name: hyperliquid_perpetual
trading_pair: SOL-USD
executor_amount_quote: 3000.0
max_executors_per_side: 1
cooldown_time: 15
leverage: 20
position_mode: ONEWAY
stop_loss: 0.25
take_profit: 0.005
time_limit: null
take_profit_order_type: 2
trailing_stop:
activation_price: 0.004
trailing_delta: 0.001
candles_connector: binance_perpetual
candles_trading_pair: SOL-USDT
interval: 5m
bb_length: 100
bb_std: 2.0
bb_long_threshold: 0.2
bb_short_threshold: 0.8
dca_spreads:
dca_amounts_pct:
dynamic_order_spread: true
dynamic_target: false
activation_bounds: null
The text was updated successfully, but these errors were encountered: