PDGGK commented on issue #39710: URL: https://github.com/apache/beam/issues/39710#issuecomment-5248556612
@Dheeraj-1103 thanks for the interest, and sorry — this one is already taken twice over. Two PRs are open against it: #39711 by @waterWang (first, 02:20Z) and #39712 (mine, 02:30Z). Your outline matches what both of them already do, so anything you build now would be a third duplicate. If you're looking for something in this area that genuinely is unclaimed, the same bug class — consecutive unguarded `close()` calls in a `@Teardown` or `close()` — tends to recur across the `sdks/java/io/*` connectors. Grepping for teardown methods that call `close()` on two or more resources in sequence is a decent way to find one, and the fix shape is the same: run every step, keep the first failure, attach the rest with `addSuppressed`. Worth filing an issue with the specific file and line before writing code, so this doesn't happen again. -- 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]
