DanielLeens commented on issue #12231: URL: https://github.com/apache/seatunnel/issues/12231#issuecomment-5742674184
Thanks for opening #12391 and for explicitly asking the earlier claimant to coordinate. I rechecked current `dev`: `SeaTunnelTask.close()` still catches only `IOException` around each lifecycle, so an unchecked close failure can still skip later resource-owning lifecycles. #12391 is therefore the correct focused implementation path for this issue. Please keep all work for this root cause on #12391. @CryoThrust, please let the thread know if you still have an active branch or any work that must be reconciled; otherwise, please avoid a second parallel patch. The requested teardown contract remains: preserve order, attempt every initialized lifecycle after checked or unchecked failures, retain the first failure with later failures suppressed, and cover those cases deterministically. #12391 is open and linked here, but its latest Build is failing, so it is not fixed in `dev` and is not ready to merge yet. Please resolve the CI result on that PR before treating the issue as complete. No label or assignment has been changed in this update. -- 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]
