He-Pin opened a new pull request, #3322:
URL: https://github.com/apache/pekko/pull/3322

   ### Motivation
   Pekko 2.0 changed `pekko.remote.artery.propagate-harmless-quarantine-events` 
to default to `off`, but `OutboundIdleShutdownSpec` still expects a harmless 
quarantine to publish `ThisActorSystemQuarantinedEvent`. The spec therefore 
waits for an event that the default configuration deliberately suppresses.
   
   ### Modification
   Explicitly enable harmless quarantine event propagation for 
`OutboundIdleShutdownSpec`.
   
   `HarmlessQuarantineSpec` continues to use the production default and cover 
the suppression behavior.
   
   ### Result
   The two specs again cover both directions:
   - legacy propagation enabled: the remote system observes 
`ThisActorSystemQuarantinedEvent`
   - production default disabled: harmless quarantine does not propagate the 
event
   
   No production configuration or runtime behavior changes.
   
   ### Tests
   - `sbt 'remote / Test / testOnly 
org.apache.pekko.remote.artery.OutboundIdleShutdownSpec -- -z "echo test 
(harmless=true)"'` - failed before the fix and passed in 3 consecutive post-fix 
runs
   - `sbt 'remote / Test / testOnly 
org.apache.pekko.remote.artery.OutboundIdleShutdownSpec 
org.apache.pekko.remote.artery.HarmlessQuarantineSpec'` - 10 tests passed
   - `sbt checkCodeStyle` - passed
   - `sbt headerCreateAll` - passed, no additional changes
   - `sbt +headerCheckAll` - passed
   - `scalafmt --list --mode diff-ref=origin/main` - passed
   - `git diff --check` - passed
   
   ### References
   Refs #2430


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


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

Reply via email to