DanielLeens commented on issue #12231:
URL: https://github.com/apache/seatunnel/issues/12231#issuecomment-5645800633

   @Adarsh-Me, please do not start a parallel fix for this issue. @CryoThrust 
made the first concrete claim and posted a scoped plan for ordered cleanup, 
preserving the first failure with suppressed later failures, and deterministic 
checked/unchecked and multi-failure coverage. I also rechecked current dev and 
the complete matching open-PR search; the unchecked-close gap remains present 
and no matching PR is open, but that does not release the active claim after 
only a few days.
   
   If you would like to contribute, please choose another unclaimed issue. The 
eventual fix for this one must attempt every initialized lifecycle in the 
existing teardown order, preserve failure visibility, and prove that later 
resource-owning lifecycles are closed after checked and unchecked earlier 
failures. No labels or formal assignees were changed.


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