Skip to content
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

Gateio perpetual - displays duplicate position on client when retrieving position from exchange #6539

Closed
rapcmia opened this issue Aug 24, 2023 · 4 comments

Comments

@rapcmia
Copy link
Contributor

rapcmia commented Aug 24, 2023

Describe the bug

When the current gateio retrieve position on an event like stopping the hummingbot (or exit), the client recognize it but displays duplicate position as well resulting client to create two take-profot/stop-loss orders to close position.

image

image

  • In the event that you need to retrieve a open position, the client recognize it but displays two open position
  • Crosscheck the exchange in the amount is still for single order yet the client displays two
  • When this happens, it also create two take-profit orders to close the position
  • Possibly related to issue Gateio Perpetual account position info missing #6510

Steps to reproduce

  1. Setup perp-mm using position_mode hedge on gate_io_perpetual
  2. When successfully open position, stop (or exit hummingbot) the strategy then start again
  3. Observe behavior when retrieving position

Release version

dev-1.19.0 / 1.18.0

Type of installation

Source

Attach required files

logs_perp-gateio.log

@nikspz nikspz changed the title Gateio - displays duplicate position on client when retrieving position from exchange Gateio perpetual - displays duplicate position on client when retrieving position from exchange Aug 25, 2023
@nikspz
Copy link
Contributor

nikspz commented Aug 28, 2023

Adding bounty for this issue.
Bug related to the gate.io perpetual connector

Bounty
Sponsor: Hummingbot Foundation
Bounty amount: 10,000 HBOT
Developer portion: 100%
Status: OPEN

@yancong001
Copy link
Contributor

fixed #6551

@rapcmia
Copy link
Contributor Author

rapcmia commented Oct 6, 2023

Fixed on version 1.20.0

@rapcmia rapcmia closed this as completed Oct 6, 2023
@nikspz
Copy link
Contributor

nikspz commented Oct 6, 2023

This bounty closed as paid.
Fix available on latest development and version 1.20.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Paid
Development

No branches or pull requests

3 participants