Skip to content

Update parsers to 4.16.2 - #51

Open
github-actions[bot] wants to merge 7 commits into
mainfrom
update/parsers-4.16.2
Open

Update parsers to 4.16.2#51
github-actions[bot] wants to merge 7 commits into
mainfrom
update/parsers-4.16.2

Conversation

@github-actions

Copy link
Copy Markdown

About this PR

📦 Updates org.scalameta:parsers from 4.14.7 to 4.16.2

📜 GitHub Release Notes - Version Diff

Usage

Please merge!

I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.

If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.

Configure Scala Steward for your repository with a .scala-steward.conf file.

Have a fantastic day writing Scala!

⚙ Adjust future updates

Add this to your .scala-steward.conf file to ignore future updates of this dependency:

updates.ignore = [ { groupId = "org.scalameta", artifactId = "parsers" } ]

Or, add this to slow down future updates of this dependency:

dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scalameta", artifactId = "parsers" }
}]
labels: library-update, early-semver-minor, semver-spec-minor, version-scheme:semver-spec, commit-count:1

davidlar and others added 7 commits May 7, 2026 09:36
…ing (zio#3173)

PR zio#3174 stopped `AsyncBodyReader` from auto-reading after the consumer
connects, but the `State.Buffering` window — used before the route
handler first pulls the body — still returned `readMore = true`
unconditionally. With request streaming enabled and an async handler, a
fast client could fill the heap with `buffer0` bytes during the gap
between `channelRead` and the handler calling `connect`.

Gate the `Buffering` arm on a configurable cap
(`Server.Config.requestBodyPreConnectBufferSize`, default 64 KB). Once
the buffer reaches the cap, `ctx.read()` is no longer called; Netty's
TCP back-pressure stalls the client until the consumer connects and the
post-transition `ctx.read()` in `connect` resumes reading. Only the
streaming path is affected — `RequestStreaming.Disabled` uses
`HttpObjectAggregator` and never instantiates `AsyncBodyReader`.
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
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