This might be working as intended but, I have a project that has some symlink directories for testing, one of these pointed to my Windows NTFS partition, and the ntfs process was at 20% for a long time. I thought at first it was some bug, but indeed it was vscode presumably indexing my Windows partition thinking it was part of my project. Maybe there could be something done about cases like this.
This might be working as intended but, I have a project that has some symlink directories for testing, one of these pointed to my Windows NTFS partition, and the ntfs process was at 20% for a long time. I thought at first it was some bug, but indeed it was vscode presumably indexing my Windows partition thinking it was part of my project. Maybe there could be something done about cases like this.