Skip to content

Fix parseNumber handling of NaN and Inf#520

Open
theRebelliousNerd wants to merge 1 commit into
mainfrom
fix-parse-number-nan-inf-16844102805502032096
Open

Fix parseNumber handling of NaN and Inf#520
theRebelliousNerd wants to merge 1 commit into
mainfrom
fix-parse-number-nan-inf-16844102805502032096

Conversation

@theRebelliousNerd
Copy link
Copy Markdown
Owner

Added safety check to parseNumber in the edge case detector to correctly handle anomalous floats like NaN and Inf to avoid causing infinite complexity issues. Implemented gap tests for type coercion verification.


PR created automatically by Jules for task 16844102805502032096 started by @theRebelliousNerd

Co-authored-by: theRebelliousNerd <187437903+theRebelliousNerd@users.noreply.github.com>
@google-labs-jules
Copy link
Copy Markdown
Contributor

👋 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.

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 18, 2026

Warning

Rate limit exceeded

@theRebelliousNerd has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 39 minutes and 40 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ 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: cadd13b6-e9a1-4b1c-91a1-03fc4ee9f941

📥 Commits

Reviewing files that changed from the base of the PR and between cc0e10f and fe9a594.

📒 Files selected for processing (3)
  • internal/campaign/edge_case_detector.go
  • internal/campaign/edge_case_detector_gaps_test.go
  • internal/campaign/edge_case_detector_test.go
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix-parse-number-nan-inf-16844102805502032096

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