The GitHub Actions job "Oracle Integration Tests" on 
pekko-persistence-jdbc.git/emit-all-messages-across-sequence-gaps-516 has 
failed.
Run started by GitHub user mucciolo (triggered by pjfanning).

Head commit for run:
8e42df1fa718442520ae6af60b6cb0cb815b6f10 / mucciolo <[email protected]>
Emit all messages across sequence number gaps in messagesWithBatch #516

* The query windowing introduced by #180 treated a windowed batch returning
  fewer messages than batchSize as the end of the journal: bounded streams
  (recovery, currentEventsByPersistenceId) completed early and silently
  dropped every message beyond a gap left by deleted messages, and live
  streams stalled forever polling an empty window. #195 fixed only the gap
  at the head of the journal.
* Rework the unfoldAsync state from FlowControl into a QueryPlan state
  machine (QueryRemaining, QueryWindow, PollRemaining, Complete): a short
  windowed batch is no longer conclusive and falls back to one query over
  the full remaining range, which gaps cannot hide messages from.
* Keep windowing as the dense fast path of #180: after a full batch shows
  the journal to be dense, queries stay bounded to [from, from + batchSize].
* Span the full remaining range on the first query, crossing a deleted
  journal head (snapshot cleanup) in a single round trip, subsuming the
  #195 special case.
* Poll the full remaining range when tailing: a windowed poll can never
  reach messages appended beyond a trailing gap.
* Specify the gap state machine in MessagesWithBatchTest (core, in-memory
  journal stub) and the database-coupled behavior in
  MessagesWithBatchDatabaseContractTest (H2 plus the five integration
  databases): hard and soft deletes, a prefix purge through the journal's
  delete, and serialization failures.

Report URL: 
https://github.com/apache/pekko-persistence-jdbc/actions/runs/27095058103

With regards,
GitHub Actions via GitBox


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

Reply via email to