This is an automated email from the ASF dual-hosted git repository.
He-Pin pushed a change to branch issue-2860-tls-graphstage-path
in repository https://gitbox.apache.org/repos/asf/pekko.git
discard 4166c150c7 chore: replace derived-from header with pure ASF header on
new files
discard a01a2d31f1 chore: scalafmt TlsGraphStageEdgeCasesSpec
discard bdd7870116 test(bench-jmh): add TlsBenchmark comparing TlsGraphStage
vs legacy actor path
discard 666b0fcdd3 test(stream): run TlsSpec against both TLS implementations
+ add GraphStage edge cases
discard 000474055f fix(stream): address TlsGraphStage close-handshake,
BUFFER_UNDERFLOW, and error-flush gaps
discard cc73eced66 feat: wire TlsGraphStage routing layer + JVM-global config
switch
discard 0c77486557 feat: Add TlsGraphStage direct-push engine for internal
GraphStage path
add 02f3cb303d feat(stream): add TlsGraphStage GraphStage path for TLS
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (4166c150c7)
\
N -- N -- N refs/heads/issue-2860-tls-graphstage-path
(02f3cb303d)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
