davidzollo commented on PR #12043: URL: https://github.com/apache/seatunnel/pull/12043#issuecomment-6703596900
<!-- daniel-pr-followup-20261107 --> Yes, contributing to Apache SeaTunnel. Pushed `c9cde9325ac9c9742d42d0972bc56afb0c4f55bc` by normal fast-forward push. Extended the existing worker-loss engine IT to assert completed post-restore checkpoint progress, and added a controlled post-READY checkpoint stall that must end FAILED. The stalled scenario permits one recovery retry, allows 30 seconds for progress, delays its first checkpoint 120 seconds, and retains READY/FAILED diagnostics assertions and the original successful-recovery data reconciliation. Validation: affected-module Spotless and diff whitespace checks passed; an independent maintainer source review of these deltas completed. No local compile, unit, integration, E2E, Docker or service execution was performed under the repository validation policy. No engine UI change or existing runtime artifact was used. The current-head [fork Build](https://github.com/DanielLeens/seatunnel/actions/runs/42347743244) was queued at the post-push inspection; this update does not claim runtime correctness or merge readiness. This supersedes earlier verification statements for the previous head. Existing connector registrations, configuration defaults, public contracts and prior test assertions were retained. Upstream-only POM changes in the approved conflict merges match dev exactly; no new dependency edits were made. Human review and any remaining explicit coverage/acceptance gaps are separate gates. -- 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]
