clolov commented on PR #18678: URL: https://github.com/apache/kafka/pull/18678#issuecomment-2612274214
Heya, thank you for this contribution! A question from my side - how did you detect this resource leak? I vaguely remember that in other parts of Kafka we use a functionality of the testing framework to confirm that we don't have more threads hanging around than we are expecting which helped us catch cases similar to this one, but I am wondering why that wasn't caught in this case. -- 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: jira-unsubscr...@kafka.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
