Skip to content

Conversation

Forostovec
Copy link

@Forostovec Forostovec commented Aug 11, 2025

Replace strconv.ParseInt(..., 10, 8) with strconv.ParseUint(..., 10, 8) and cast to byte so inputs in the full 0–255 range (including 255) are parsed correctly. Behavior for 0–127 remains unchanged. No other files touched.

Summary by CodeRabbit

  • New Features

    • Debug tool now accepts byte inputs in the full 0–255 range, enabling entry of values above 127 and displaying their hex output as before.
  • Bug Fixes

    • Invalidates negative byte inputs, providing clear parse errors instead of accepting signed values.

@github-actions github-actions bot added the C:CLI label Aug 11, 2025
Copy link
Contributor

coderabbitai bot commented Aug 11, 2025

📝 Walkthrough

Walkthrough

Adjusted per-byte input parsing in the debug client from signed to unsigned integers. The code now uses ParseUint for 8-bit values and casts to byte accordingly, shifting accepted input range from -128..127 to 0..255. Error handling and surrounding logic/output remain unchanged.

Changes

Cohort / File(s) Summary of Changes
Unsigned byte parsing
client/debug/main.go
Replaced strconv.ParseInt(..., 8) with strconv.ParseUint(..., 8); cast result via byte(u). Accepts 0–255 instead of -128–127. Negative inputs now fail parsing; 128–255 become valid. No other logic changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

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
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

‼️ IMPORTANT
Auto-reply has been disabled for this repository in the CodeRabbit settings. The CodeRabbit bot will not respond to your replies unless it is explicitly tagged.

  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai generate unit tests to generate unit tests for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
client/debug/main.go (1)

307-319: Harden whitespace handling and error messages; preallocate capacity

Current splitting by " " can produce empty tokens on extra spaces (e.g., "[10 21]") leading to parse errors. Use strings.Fields to normalize whitespace, TrimSpace the input, and preallocate the byte slice. Also add token context to the error.

-           stringBytes := args[0]
-           stringBytes = strings.Trim(stringBytes, "[")
-           stringBytes = strings.Trim(stringBytes, "]")
-           spl := strings.Split(stringBytes, " ")
-
-           byteArray := []byte{}
-           for _, s := range spl {
-               u, err := strconv.ParseUint(s, 10, 8)
-               if err != nil {
-                   return err
-               }
-               byteArray = append(byteArray, byte(u))
-           }
+           raw := strings.TrimSpace(args[0])
+           raw = strings.TrimPrefix(raw, "[")
+           raw = strings.TrimSuffix(raw, "]")
+           tokens := strings.Fields(raw)
+
+           byteArray := make([]byte, 0, len(tokens))
+           for _, s := range tokens {
+               u, err := strconv.ParseUint(s, 10, 8)
+               if err != nil {
+                   return fmt.Errorf("invalid byte %q: %w", s, err)
+               }
+               byteArray = append(byteArray, byte(u))
+           }
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Knowledge Base: Disabled due to Reviews > Disable Knowledge Base setting

📥 Commits

Reviewing files that changed from the base of the PR and between bb1dcdc and 68e292f.

📒 Files selected for processing (1)
  • client/debug/main.go (1 hunks)
🧰 Additional context used
🧬 Code Graph Analysis (1)
client/debug/main.go (1)
math/uint.go (1)
  • ParseUint (240-246)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: Summary
🔇 Additional comments (1)
client/debug/main.go (1)

314-318: Correctly switches to unsigned parsing for 0–255 range

Using strconv.ParseUint(..., 10, 8) and casting to byte is the right approach. It preserves 0–127 behavior and properly supports 128–255 while rejecting negatives as intended.

@aljo242
Copy link
Contributor

aljo242 commented Aug 11, 2025

can you test this change?

@Forostovec
Copy link
Author

can you test this change?

Done

@Forostovec Forostovec changed the title client/debug: use ParseUint in raw-bytes to support 0–255 fix: use ParseUint in raw-bytes to support 0–255 Aug 11, 2025
@Forostovec
Copy link
Author

can you test this change?

fixed lint

@Forostovec Forostovec closed this Sep 4, 2025
@Forostovec Forostovec deleted the fix/debug-raw-bytes-parseuint branch September 4, 2025 08:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants