SEZ9 commented on PR #11597: URL: https://github.com/apache/seatunnel/pull/11597#issuecomment-6568151337
Thanks for pushing the asynchronous revision in `38f1ca01d7bace05a0dec8627c5143f6002ddca6`. On the operation-thread blocking point: `GetRunningJobSlotUsageOperation` now extends `AsyncOperation`, `doRun` returns a `PassiveCompletableFuture` without `get`/`join`, and the response is sent on completion with `returnsResponse=false`, including the synchronous scheduling-failure path and deregistration of the live operation. Together with the new operation and pending-task lifecycle tests, I consider this finding resolved on the diff itself. Separately, the fork Build run `41162604738` for this head finished `completed` / `cancelled` (success=7, cancelled=77, skipped=12). The cancelled set includes `124443780560` (Run / Build website) and `124443780567` / `124443780571` (Run / engine-resource-managers-it on 11 and 17). Cancellation does not change the source conclusion above, but it also leaves no executed evidence for those jobs. Could you check whether a newer attempt is running, otherwise re-run only the cancelled required jobs and link the result here? No unrelated source or dependency edits, and no rebase needed just for this. <!-- streview-comment:2215 --> -- 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]
