DanielLeens commented on PR #11718:
URL: https://github.com/apache/seatunnel/pull/11718#issuecomment-5423970175

   Thanks for confirming, @SEZ9 — understood, nothing to review yet on my end.
   
   I've noted the plan is unchanged: a single follow-up commit on this PR 
covering Item 1 (best-effort in-container kill of the wedged `seatunnel.sh` 
client on the timeout path, without disturbing the 
`runningCount`/thread-leak-check interaction already documented in the class), 
Item 2 (scoping the Javadoc to the `executeJob(String)` overload only), and 
Item 6 (the local/IDE non-daemon-worker caveat).
   
   Current head remains `d73c2b90bf`, unchanged and still approved/mergeable 
as-is. I'll wait for your ping once the commit lands, then do the focused pass 
on the in-container-kill piece plus a quick check of the two doc fixes against 
the call sites, as agreed.
   


-- 
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]

Reply via email to