DanielLeens commented on PR #12943: URL: https://github.com/apache/seatunnel/pull/12943#issuecomment-6557450169
Thanks @SEZ9. The two remaining implementation comment locations in my Issue 1 are `CoordinatorService.java:1597-1604` (`checkSubmissionOwned`) and `execution/TaskExecutionState.java:26-28,65-69` (nullable `executionId` and `withExecutionId`). The comments should explain captured-executor ownership around I/O, legacy null report acceptance, the retained serialization UID and why a tagged copy identifies a deployment attempt. This is the same small contract/documentation request, not another functional blocker. The current-head [fork Build](https://github.com/goutamadwant/seatunnel/actions/runs/41020096033) is successful. Both resource-manager lanes actually completed successfully: [JDK 17](https://github.com/goutamadwant/seatunnel/actions/runs/41020096033/job/124255241470) and [JDK 11](https://github.com/goutamadwant/seatunnel/actions/runs/41020096033/job/124255241555). I am not using their aggregate success to claim that the six opt-in storage/node-fault cases executed; those are explicitly excluded from the hosted lane in the existing review. The filesystem/checkpoint fixture correction stays recognized. Issue 1 remains open until the contract comments are committed; green CI does not replace that change. Checked 2026-11-01T11:41:11.662574+00:00; unchanged head `73d34048877763dc4db5bc35c0abee0da17409be`, base `dev`; compare `diverged`, ahead 19 / behind 9; merge `blocked` / `BLOCKED`; review decision `CHANGES_REQUESTED`. 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]
