The GitHub Actions job "Pull Requests" on 
pekko.git/fix/tls-graphstage-buffer-sizing has succeeded.
Run started by GitHub user He-Pin (triggered by He-Pin).

Head commit for run:
3c4452d18aa44c60419f8d940aa0fd64d0183ac7 / 虎鸣 <[email protected]>
Fix TLS GraphStage buffer allocation and growth #3728

Motivation:
TLS GraphStage cannot initialize when the TCP pool is smaller than the
SSLEngine packet requirement, and fixed-size pooled buffers cannot satisfy
growth. The partial-record regression test also races handshake processing.

Modification:
Use stage-owned heap buffers when needed, sharing the initial allocation
between three disjoint transport slices. Flush before growing, preserve
pending data, refresh session requirements and batching, and shrink drained
output after renegotiation. Keep foreign buffers out of the TCP pool.
Add buffer and cancellation regressions and document allocation behavior.
Synchronize the test harness with session verification and check query
counts after cancellation acknowledges completion of unwrap processing.

Result:
Small TCP buffers no longer prevent TLS progress. Buffer growth and recycling
preserve data and ownership, and the partial-record test checks session
query behavior without racing the stage.

Tests:
- JDK 17: 312 TLS/TCP tests passed, including 28 focused buffer/close cases.
- Negative control: unconditional underflow session queries fail with 3 != 2;
  the temporary mutation was restored.
- Native scalafmt, headerCreateAll, checkCodeStyle and git diff --check passed.
- +mimaReportBinaryIssues passed on Scala 2.13.18 and 3.3.9.
- sortImports encountered a Scalafix/Scalameta NoSuchMethodError; its unrelated
  edits were reverted and the native formatter check passed.
- docs/paradox stopped at user request; validatePullRequest and the remaining
  Scala test matrix are delegated to remote CI.

References:
Refs #2860, Refs #3727, Refs #3728.

Report URL: https://github.com/apache/pekko/actions/runs/40912405167

With regards,
GitHub Actions via GitBox


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to