dajiaohuang opened a new pull request, #3715:
URL: https://github.com/apache/pekko/pull/3715

   Resolves #3592.
   
   `MergeLatest` now defaults to a configurable latest-value mode: while 
downstream is back-pressured it continues pulling inputs, conflates superseded 
combinations, and retains only the latest value per input. This limits state 
retained by `MergeLatest` itself; it does not bound buffers in upstream stages. 
Set `pekko.stream.materializer.merge-latest.mode = legacy` to retain the 
previous every-update behavior. A pending latest combination is emitted before 
completion when demand is available.
   
   Updated Scala and Java API docs, operator docs, migration guidance, and 2.0 
release notes. Added directional coverage for conflation, pending/eager 
completion, one-input behavior, and legacy buffering.
   
   Tests and checks:
   - Scala 2.13 targeted suites: 15/15 passed.
   - Scala 3.3.8 targeted suites: 15/15 passed.
   - `docs/paradox`, `+headerCheckAll`, changed Scala formatting checks, and 
`git diff --check` passed.
   - `checkCodeStyle` passed Scala formatting but did not pass the Java 
formatter: it flagged three untouched files under `actor`/`actor-tests`. The 
task environment used JDK 26; Pekko's instructions specify JDK 17 for Java 
formatter tasks, and JDK 17 was not available in this task setup. No Java 
source was changed.
   - `validatePullRequest` exited 0 but listed no impacted projects or test 
tasks, so it is not counted as broader test evidence.
   
   No CI status was queried.


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