diegomrsantos opened a new issue, #4237: URL: https://github.com/apache/iggy/issues/4237
Parent tracker: #4232. Build reusable failure fixtures and assertions for the agreed delivery contract. Verify destination record identities and saved recovery positions independently of the runtime's processing counters. Required scenarios: - Rejected delivery followed by restart and successful replay through the actual HTTP sink. - Destination success followed by abrupt termination before checkpoint completion. Duplicates are permitted; missing records are not. - Buffered acceptance, partial delivery, and failed flush followed by recovery. - A failed record followed by later completion, including multiple partitions. - Checkpoint timeouts where the server did and did not persist the update. - Restart with delayed completions from the previous instance, and ownership changes where supported by the agreed contract. - Decode and transform errors, intentional filtering, and any supported dead-letter policy. - Incompatible plugins and unavailable source records during recovery. Use controlled synchronization and fault injection to target the relevant boundaries. Include abrupt process termination so graceful shutdown cannot hide missing delivery barriers. The common suite must run in CI, and supported plugins must have coverage for their actual acknowledgment boundary. Begin fixture development with A; add and run the relevant tests as B, C, and D are implemented. -- 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]
