The GitHub Actions job "Binary Compatibility" on pekko.git/main has succeeded.
Run started by GitHub user He-Pin (triggered by He-Pin).

Head commit for run:
3b21abca495d00d53229f182ba510b28ca4101f3 / He-Pin(kerr) <[email protected]>
fix(remote): resume classic remoting reader after failed handoff (#3205)

Motivation:
Classic remoting passive read handoff can leave the original outbound reader 
stuck in notReading if the read-only handoff endpoint fails.

Modification:
Track passive read handoff fallback endpoints and resume the original writable 
reader when the read-only endpoint terminates while the original endpoint and 
UID still match. Carry fallback state across replacement read-only endpoints, 
clear stale fallback state on UID/address changes, handle ResumeReading in 
supervisor states, add logging, and add regression coverage. Also correct the 
stale classic remoting passive-connections config text.

Result:
Classic remoting can recover future inbound messages on the original 
association after a failed passive read handoff.

Tests:
- rtk sbt "remote / Test / testOnly 
org.apache.pekko.remote.ReliableDeliverySupervisorSpec" / passed (4 tests)
- rtk sbt "remote / Test / testOnly 
org.apache.pekko.remote.classic.RemotingSpec -- -z \"resume the outbound 
reader\"" / passed
- rtk sbt "remote / Test / testOnly 
org.apache.pekko.remote.classic.RemotingSpec" / passed (22 tests)
- rtk scalafmt --list --mode diff-ref=origin/main / passed (JVM Unsafe warnings 
only)
- rtk bash -lc 'git diff --check' / passed
- rtk sbt sortImports / failed: Scalafix/scala-meta NoSuchMethodError in local 
tooling; unrelated generated change was reverted
- qodercli stdout review / No must-fix findings
- independent subAgent review / No must-fix findings

References:
Fixes #3206

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

With regards,
GitHub Actions via GitBox


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

Reply via email to