Skip to content

fix(math): use pure BigInt arithmetic in warmup to avoid BigInt(float) crash#188

Open
0x-SquidSol wants to merge 1 commit intodcccrypto:mainfrom
0x-SquidSol:fix/warmup-bigint-float-crash-v2
Open

fix(math): use pure BigInt arithmetic in warmup to avoid BigInt(float) crash#188
0x-SquidSol wants to merge 1 commit intodcccrypto:mainfrom
0x-SquidSol:fix/warmup-bigint-float-crash-v2

Conversation

@0x-SquidSol
Copy link
Copy Markdown
Contributor

Summary

  • Re-applies PR fix(math): use pure BigInt arithmetic in warmup to avoid BigInt(float) crash #154 which was overwritten by upstream SBF offset corrections
  • computeWarmupLeverageCap (line 93) and computeWarmupMaxPositionSize (line 136) called BigInt() on computeMaxLeverage() which returns a float (e.g., 3.003 for 3333 bps)
  • BigInt(3.003) throws TypeError — crashes for any initialMarginBps that doesn't evenly divide 10000
  • Replaced with pure BigInt arithmetic: (10000n * unlocked) / (initialMarginBps * totalCapital) and (unlocked * 10000n) / initialMarginBps

Test plan

  • Full test suite: no new failures introduced
  • Verified: initialMarginBps=3333n produces correct results instead of crashing

🤖 Generated with Claude Code

…) crash

Re-applies PR dcccrypto#154 which was overwritten by upstream SBF offset
corrections. computeWarmupLeverageCap and computeWarmupMaxPositionSize
called BigInt() on computeMaxLeverage() return value which is a
float (e.g., 3.003 for 3333 bps). BigInt(3.003) throws TypeError.

Replaced with pure BigInt arithmetic:
- leverageCap: (10000n * unlocked) / (initialMarginBps * totalCapital)
- maxPositionSize: (unlocked * 10000n) / initialMarginBps

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Apr 13, 2026

Warning

Rate limit exceeded

@0x-SquidSol has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 45 minutes and 35 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 45 minutes and 35 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: ef06614d-6031-4df5-9c1f-9fac646e0c31

📥 Commits

Reviewing files that changed from the base of the PR and between 2f80d79 and 2625a8f.

📒 Files selected for processing (1)
  • src/math/warmup.ts
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

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