fix: only print top 512 bytes on buffer field debug log

[fengmk2]

Summary by CodeRabbit

• New Features
  • Enhanced buffer logging in forms to include content size and hex representation, improving debugging and monitoring.

[coderabbitai]

Walkthrough

The FormStream class in lib/formstream.js has been enhanced to include a conditional check within the buffer method. This update logs the buffer content size and its hex representation. For buffers exceeding 512 bytes, only the first 512 bytes are logged. This change aims to improve debugging and monitoring by providing detailed insights into the buffer content without overwhelming the logs.

Changes

File	Change Summary
lib/formstream.js	Added a conditional check in the buffer method to log the buffer content size and hex representation. If the buffer length exceeds 512 bytes, only the first 512 bytes are logged.

Poem

In the code where buffers flow,
A check now helps us better know.
If bytes exceed five hundred and twelve,
Only the start, in logs, will delve.
Debugging now, a breeze to see,
Thanks to this smart log decree! 🌟

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• 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 generate unit testing code for this file.
  • @coderabbitai modularize this function.
• 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as 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 resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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.

[codecov]

Codecov Report

Attention: Patch coverage is 71.42857% with 2 lines in your changes missing coverage. Please review.

Project coverage is 98.24%. Comparing base (7d1166e) to head (ead76b6).
Report is 1 commits behind head on master.

Files	Patch %	Lines
lib/formstream.js	71.42%	2 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master      #27      +/-   ##
==========================================
- Coverage   98.73%   98.24%   -0.49%     
==========================================
  Files           1        1              
  Lines         394      399       +5     
  Branches       58       59       +1     
==========================================
+ Hits          389      392       +3     
- Misses          5        7       +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 3b1c6b3 and ead76b6.

Files selected for processing (1)

• lib/formstream.js (1 hunks)

Files not reviewed due to errors (1)

• lib/formstream.js (no review received)

Additional context used

Biome

lib/formstream.js

[error] 78-78: This var should be declared at the root of the enclosing function. (lint/correctness/noInnerDeclarations)

The var is accessible in the whole body of the enclosing function.
To avoid confusion, it should be declared at the root of the enclosing function.

---

[error] 93-93: This var should be declared at the root of the enclosing function. (lint/correctness/noInnerDeclarations)

The var is accessible in the whole body of the enclosing function.
To avoid confusion, it should be declared at the root of the enclosing function.

---

[error] 254-254: This var should be declared at the root of the enclosing function. (lint/correctness/noInnerDeclarations)

The var is accessible in the whole body of the enclosing function.
To avoid confusion, it should be declared at the root of the enclosing function.

GitHub Check: codecov/patch

lib/formstream.js

[warning] 218-219: lib/formstream.js#L218-L219
Added lines #L218 - L219 were not covered by tests