fix: order of operations when resetting buffer

[danielgtaylor]

This fixes an order-of-operations bug that was due to copy/paste and removal of defer statements, however defers execute in reverse order while the copied statements execute in order. This means the buffer could be sent back into the pool before getting reset, causing a potential race on the next read. This was a silly mistake that should have been caught with the race detector during tests but was unfortunately missed. Sorry about that!

Fixes #552

Summary by CodeRabbit

• Bug Fixes
  • Improved buffer lifecycle management to prevent misuse by ensuring proper reset before returning to the pool.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The recent changes to the Register function enhance buffer lifecycle management by ensuring that buffers are reset before being returned to the pool. This adjustment mitigates potential race conditions and improves memory management, thereby increasing the robustness of the codebase.

Changes

Files	Change Summary
huma.go	Moved buffer return to pool after buffer reset to prevent misuse.

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant Server
    participant BufferPool

    Client->>Server: Send Request with Buffer
    Server->>BufferPool: Get Buffer
    Server->>Buffer: Use Buffer
    Server->>Buffer: Reset Buffer
    Server->>BufferPool: Return Buffer
    BufferPool-->>Server: Buffer Returned

Loading

Assessment against linked issues

Objective	Addressed	Explanation
Race condition detected in Huma v2.22.0 (#552)	✅

🐰 In the garden where buffers play,
I hop and reset them every day!
A jump to the pool, so fresh and bright,
Keeping things safe, oh what a delight!
Memory managed, so clever and neat,
In code we trust, with no bugs to greet! 🌼

---

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

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 92.76%. Comparing base (e1ffc73) to head (731da9e).
Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #553   +/-   ##
=======================================
  Coverage   92.76%   92.76%           
=======================================
  Files          22       22           
  Lines        3883     3883           
=======================================
  Hits         3602     3602           
  Misses        236      236           
  Partials       45       45           

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