Release v15.30.0
Summary
Adds append-aware observer completion waiting so clients can wait for observers after appends, receive complete failed-partition results, and use documented append workflows.
Added
IAppendResultForObserverCompletionas a shared append-tail contract across append results, including event-store/namespace/sequence context and tail sequence number (#1845)WaitForCompletionclient extension inCratis.Chronicle.ObservationreturningAppendResultWaitForCompletionResultwith completion status and failed partitions (#1845)IObservers.WaitForCompletiongRPC contract plus request/response messages for observer completion waits (#1845)- Documentation for
WaitForCompletionusage after bothAppendandAppendManyoperations (#1845) - Integration coverage for append/observer workflows with failing and concurrently processing observers to verify active observer processing behavior during failures (#1845)
Changed
AppendResultandAppendManyResultnow expose observer wait context throughIAppendResultForObserverCompletionfor direct use by the wait extension method (#1845)- Append result handling now consistently reports operation tail sequence numbers for completion waits (
SequenceNumbervs lastSequenceNumbersitem) (#1845) - Observer-completion waiting now scopes failed-partition retrieval to affected observers to reduce unnecessary data reads (#1845)
Fixed
- Observer-completion waiting no longer exits on first failed partition; it now waits until affected observers are complete-or-failed and returns the complete failed-partition set for the operation (#1845)
- Append and append-many operations now succeed in testing scenarios where observer services are unavailable, preventing spec regressions introduced by observer wait wiring (#1845)
Removed
- None.
Security
- None.
Deprecated
- None.