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

   ### Motivation
   
   Issue #3110 tracks stream operators that should honor `SupervisionStrategy` 
for user functions.
   
   `zipWith` / `zipWithN` invoke user-provided zipper functions, but failures 
were not supervised: exceptions failed the stream unconditionally.
   
   ### Modification
   
   - Added zipper exception supervision handling in both implementations:
     - `ZipWithApply.scala.template` (covers all `ZipWith` arities)
     - `Graph.scala` (`ZipWithN`)
   - Supervision semantics for zipper failures:
     - `Stop` → fail stage
     - `Resume` / `Restart` → drop failing zipped element and continue
   - Updated pending accounting on resumed/restarted failures so the stage can 
continue satisfying current demand without stalling.
   - Updated Scala/Java API docs and operator docs:
     - `zipWith.md`
     - `zipWithN.md`
   - Added directional tests in:
     - `FlowZipWithSpec`
     - `GraphZipWithNSpec`
     covering explicit Stop, default Stop, Resume, Restart.
   
   ### Result
   
   `zipWith` and `zipWithN` now honor `ActorAttributes.SupervisionStrategy` for 
zipper function failures, with regression coverage for dropped-element paths.
   
   which is now Apache licensed
   
   ### Tests
   
   - `sbt "stream-tests/Test/testOnly 
org.apache.pekko.stream.scaladsl.FlowZipWithSpec 
org.apache.pekko.stream.scaladsl.GraphZipWithNSpec"` (37/37 passed)
   - `sbt "stream/mimaReportBinaryIssues"` (clean)
   - `sbt "docs/paradox"` (passed)
   
   ### References
   
   Refs #3110
   


-- 
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