Is workspace.createFileSystemWatcher working for you?

[senyai]

Hi!

I'm starting to get a little bit crazy. Let's created a watcher like this (linux, vscode 1.73.1):

workspace.createFileSystemWatcher('**');

and test the events:

mkdir repo1 repoX test1
echo 'test'>deleteme.txt - ✅ I see event
echo 'test'>repo1/deleteme.txt - ❌ No event
echo 'test'>repoX/deleteme.txt - ✅ I see event
echo 'test'>test1/deleteme.txt - ❌ No event

Can anyone confirm, please? There's a chance it's my os, I haven't updated the kernel for 3 years.

[senyai]

More info on the issue. I didn't say the steps quite right. It's not the file names that matter, it's about the order of creation. Subfolders created after createFileSystemWatcher is called are tracked, but not the ones created before.

[senyai]

With this new info I found related issue: microsoft/vscode#161224. Yes [File Watcher (parcel)] is triggered for new folders but not for existing folders. I guess it's something to do with parcel module. Will investigate further.

[senyai]

I swear createFileSystemWatcher worked on my computer before. It works on other computers but not on mine. I changed nothing! No idea where to look now. Sorry for the buzz. At least, it somewhat helped me 🙂.