The GitHub Actions job "Pull Requests" on pekko.git/fix/tls-graphstage-buffer-sizing has failed. Run started by GitHub user He-Pin (triggered by He-Pin).
Head commit for run: 90b20c6e50ce1c9d3aee3fcb5c23728531ee3c6b / 虎鸣 <[email protected]> Fix TLS GraphStage buffer allocation and growth #3728 Motivation: Small TCP pool buffers prevent TLS initialization and cannot satisfy output growth. Deferred ciphertext, session changes and heap allocation also need safe capacity and ownership handling. Modification: Use stage-owned heap buffers when the TCP pool is too small, sharing one initial allocation between three disjoint transport slices. Flush before growing, refresh session requirements and batching, and shrink drained output after a handshake lowers its capacity requirement. Validate pooled capacity and recycling. Rebase on main while preserving cancellation/draining coverage, add review and integration regressions, and document allocation tradeoffs. Result: TLS progresses with small TCP buffers without losing ciphertext or polluting the shared pool. Transient session capacity can be reclaimed without repeated growth, and initialization uses one backing heap allocation instead of three. Tests: - Two new review regressions failed before the fix and passed afterwards. - JDK 21: 310 related TLS/TCP tests passed, including 28 focused cases. - JDK 17 and 25: 28 focused cases passed on each runtime via ScalaTest. - Native scalafmt, headerCreateAll, +headerCheckAll and git diff --check passed. - Qoder stdout review and independent review: No must-fix findings. - Full local MiMa stopped at user request; full validation, docs, import/style and binary compatibility checks are delegated to remote CI. References: Refs #2860, Refs #3727, Refs #3728. Report URL: https://github.com/apache/pekko/actions/runs/40894015190 With regards, GitHub Actions via GitBox --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
