Kubectl process lingers after VS Code is closed and has a handle on the opened folder about mindaro HOT 3 OPEN

Hi @maras28, thanks so much for reporting this issue. I'm logging a bug for us to investigate this further. We'll update this thread as soon as we get to the root cause.

from mindaro.

Thank you @maras28 for reporting this issue. I can confirm I'm able to reproduce the behavior you see where the current folder cannot be deleted when the extension is installed.

However, in my case, this doesn't seem related to kubectl as I reproduce this without the corresponding logic. Also, looking at the handles blocked in the Resource Monitor, I can only see that code (so VS Code) is blocking the folder.

Have you seen the handle being taken specifically by kubectl in your case?
In parallel, I'm still investigating to understand the root cause of this.

from mindaro.

I also use the Resource Monitor. I just did the steps above twice in two different VS Code instances and I have two kubectl processes with a handle to the folder I tried.

from mindaro.