goutamadwant opened a new pull request, #12360: URL: https://github.com/apache/seatunnel/pull/12360
### Purpose of this pull request Refs #12212. Add the requested deterministic fetcher/reader checkpoint harness without changing production behavior. - Cover failure before handoff, partial delivery, failure during snapshot, healthy snapshots and checkpoint-lock contention. - Exercise the real shared fetcher, CDC reader/emitter and serialized split state, restoring into a fresh reader. - Use bounded synchronization and verify actual lock contention before releasing delivery. The tested schedules preserve emitted offsets rather than checkpointing queued candidate positions. They did not justify a production guard or parser reconnect patch. Replay uses synthetic offsets, not MySQL binlog/GTID semantics; the original EOF and missing-row investigation remains open. ### Does this PR introduce _any_ user-facing change? No. Production code, defaults, dependencies and checkpoint formats are unchanged. ### How was this patch tested? - Java 11 focused reader tests: 14 passed, including five new scenarios. - Complete CDC-base suite: 102 passed; connector-common suite: 6 passed. - Spotless and whitespace checks passed. Independent correctness/security reviews rechecked the corrected contention assertion with no remaining actionable findings. - No real MySQL replay, sink-durability, full-repository or E2E proof is claimed. The earlier broader reactor verify was interrupted, not reported as passed. ### Check list * [ ] New Jar license notice: N/A; no dependency added. * [ ] User documentation: N/A; test-only change. * [ ] `incompatible-changes.md`: N/A; no compatibility change. * [ ] Connector integration updates: N/A; plugin mapping, distribution POM, CI labels and plugin config remain unchanged. No E2E added because no runtime behavior changed. -- 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]
