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

   ### Motivation
   
   The durable state suite does not cover a large user stash followed by a new 
command after unstashing completes.
   
   ### Modification
   
   Stash a deterministic command sequence, observe a processing barrier, 
unstash and assert every reply in order, then verify the next command succeeds.
   
   ### Result
   
   Coverage protects ordered draining and continued processing without 
sleep-based coordination.
   
   ### Tests
   
   - Passed: `persistence-typed-tests / Test / testOnly 
org.apache.pekko.persistence.typed.state.scaladsl.DurableStateRevisionSpec`.
   - Passed: `checkCodeStyle`.
   - Passed: `+headerCheckAll`.
   - Full `validatePullRequest` is left to remote CI.
   
   ### References
   
   - Refs [akka/akka-core#32137](https://github.com/akka/akka-core/pull/32137).
   - Upstream commit: 
[a95c177fe9d3dce2e9f83eb3c4cd02e963101658](https://github.com/akka/akka-core/commit/a95c177fe9d3dce2e9f83eb3c4cd02e963101658).
   - The user-stash regression in `DurableStateRevisionSpec.scala` adapts the 
5000-event recovery/stash/unstash scenario from Akka's 
`DurableStateStashOverflowSpec.scala` in akka/akka-core#32137, retaining that 
source's exact 2020-2023 copyright notice alongside the existing Pekko file 
notice. CountStashed synchronization, exact sequence ordering and the 
subsequent-command assertions are Pekko additions.
   - Source snapshot: Akka `v2.9.0` 
(`bf20e967571574994ccb3cae411401f5a9021ab9`). Its 
[license](https://github.com/akka/akka-core/blob/v2.9.0/LICENSE) names 
2026-10-23 as the Change Date and Apache License 2.0 as the Change License. 
`LICENSE` and `NOTICE` record the source, and original copyright notices are 
retained. Headers were generated/checked with the project sbt tasks.
   


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