fix: release HTTP request buffers after chunk-limit rejection

[pskiran1]

What does the PR do?

Requests exceeding the HTTP chunk limit could retain accumulated body buffers and continue into inference handling after HTTP 400 was queued, causing excessive RSS growth across repeated rejected requests.
This change releases the accumulated body on rejection, discards remaining body fragments processed from already received bytes, and prevents dispatch of requests whose response is already marked finished.
The chunk limit and existing test criteria remain unchanged.

Checklist

• PR title reflects the change and is of format <commit_type>: <Title>
• Changes are described in the pull request.
• Related issues are referenced.
• Populated github labels field
• Added test plan and verified test passes.
• Verified that the PR passes existing CI.
• Verified copyright is correct on all changed files.
• Added succinct git squash message before merging ref.
• All template sections are filled out.
• Optional: Additional screenshots for behavior/output changes with before/after.

Commit Type:

• build
• ci
• docs
• feat
• fix
• perf
• refactor
• revert
• style
• test

Related PRs: #8770

Where should the reviewer start?

Test plan:

• CI Pipeline ID: 72440627

Caveats:

Background

#8770

[greptile-apps]

Confidence Score: 5/5

[Medium risk] Fixes memory leak in HTTP request handling when chunk limit is exceeded.

The PR appears safe to merge based on the reviewed changes.

Summary

This PR releases accumulated HTTP request-body data when the chunk limit is exceeded, discards body fragments already buffered by the parser, and prevents a rejected request from reaching normal dispatch.

• The only change since the previous review reformats a test import.
• The chunk limit and test criteria remain unchanged.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  A[Chunk count exceeds limit] --> B[Drain accumulated body]
  B --> C[Discard buffered fragments]
  C --> D[Queue HTTP 400 and stop reads]
  D --> E[Skip normal dispatch]

Loading

_{Reviews (4) · Last reviewed commit: "Fix pre-commit error" · Reviewed by Greptile}