Skip to content

Fix bugs and improve script robustness for Bybit listings#1

Open
webcuser wants to merge 1 commit into
masterfrom
fix-bybit-sell-script-bugs-13773144813208891684
Open

Fix bugs and improve script robustness for Bybit listings#1
webcuser wants to merge 1 commit into
masterfrom
fix-bybit-sell-script-bugs-13773144813208891684

Conversation

@webcuser

Copy link
Copy Markdown
Owner

The script had several bugs that would prevent it from working correctly:

  1. Countdown bug: time_diff.seconds only counts seconds within a day, causing incorrect time remaining displays for listings more than 24 hours away. Fixed by using total_seconds().
  2. API parameters: Bybit V5 API uses recvWindow (not recv_window) and doesn't support max_retrives in the place_order call.
  3. Quantity precision: Pass qty as a string to ensure the API receives exact values.
  4. Resilience: Added retries for fetching balance and placing orders, which is essential for high-load listing events.

PR created automatically by Jules for task 13773144813208891684 started by @webcuser

- Corrected countdown calculation to handle durations over 24 hours using total_seconds().
- Updated Bybit API parameters: renamed recv_window to recvWindow and removed invalid max_retrives.
- Converted order quantity (qty) to string to avoid float precision issues.
- Implemented retry logic for wallet balance retrieval to account for delays in listing.
- Added a robust retry loop (10 attempts) for the market sell order.
- Verified changes with a mocked unit test suite.

Co-authored-by: webcuser <97110714+webcuser@users.noreply.github.com>
@google-labs-jules

Copy link
Copy Markdown

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant