DanielLeens commented on PR #12623: URL: https://github.com/apache/seatunnel/pull/12623#issuecomment-6557468895
Thanks @SEZ9. I agree that merge ordering must stay explicit: #12511 supplies the post-wait restore guard and whole-job cases; this PR protects the later stopped-vertex window. Please retain the dependency/land-#12511-first note in the PR description. Neither this reply nor the current green Build means the companion has already merged. For F2, my previous statement that these vertex tests distinguish a reverted implementation was a source-level counterfactual, **not** a mutation-test run. I did not execute a reverted version and have no failing runtime output to paste. The existing tests assert completion of the future for a stopped/reset state process and preserve the skipped-transition case; CI's [exact-head Build](https://github.com/Vivek1106-04/seatunnel/actions/runs/40727927696) verifies the submitted implementation. A requested revert/mutation run would be additional evidence to collect in GitHub CI, not something I will fabricate or run locally here. My approval remains subject to the stated merge order and the effective maintainer gate. Checked 2026-11-01T11:43:09.305426+00:00; unchanged head `caa5f098fc0a5c6dd887ba8632dc43d463eb4580`, base `dev`; compare `diverged`, ahead 3 / behind 28; merge `blocked` / `BLOCKED`; review decision `REVIEW_REQUIRED`. Behind/diverged is recorded independently and does not itself request a sync. Daniel has READ repository permission. -- 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]
