Kevin Zhao

Thank you all for taking a look at this. From my search, this looks to be a recurring issue: https://github.com/microsoft/kafka-connect-cosmosdb/issues/290 https://github.com/microsoft/kafka-connect-cosmosdb/issues/253 Those issues above were printing the same stack traces...

@xinlian12 Thanks for getting back to me. While I'm not explicitly making the calls, I suspect the change feel pull queries I'm making are still active in other threads. This...

@xinlian12 Just wanted to know when we could expect a fix for this issue. In the meantime, do you think I can get away with not invoking `client.close()` after I"m...

@xinlian12 That's good to know. Thank you for investigating. If you're not able to reproduce using the code snippet I provided above then there must be some query somewhere preventing...

Upon further investigation, it does look like I have multiple threads from the Cosmos client running, despite exiting out of the while loop. For the screenshot below, I have 4...

Okay, I finally realized why those `cosmos-rntbd` threads stayed open despite exiting out of the change feed loop. Turns out the issue is not related to the change feed or...

Same issue with jetbrains mcp. Submitted a ticket to jetbrains here: https://youtrack.jetbrains.com/issue/IDEA-377834/IntelliJ-MCP-Server-defaults-to-.ijwb-directory-when-running-in-a-bazel-project

This is what Jetbrains told me to resolve the issue: the problem lies with the existence of the .ijwb directory created by the now deprecated "Bazel for IntelliJ" plugin. Jetbrains...

Experiencing this issue on a whole range of Rancher Desktop versions from 1.13 to 1.17 on Mac OS Sonoma 14.6.1 cc: @jandubois

I managed to fix my issue after it was pointed out to me that this config yaml file was removed from the last time I performed a Factory Reset on...