FileSystemWatcher
drops events for nested files on Codespaces
#48658
Replies: 2 comments 6 replies
-
Hi from the codespaces team, thank for reaching out and i'm sorry for the inconvenience. I've created an internal issue to track the bug and have sent it to the right team for prioritization. However, I can't guarantee when it'll be prioritized at this time. |
Beta Was this translation helpful? Give feedback.
-
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Question
Body
Tl;dr:
On Codespaces the extension host's
FileSystemWatcher
seems to drop events for files that are at a certain depth within a nested folder structure. Here is a quick demo of what I am talking about (with log level set to trace and the "Output" tab showing the "Remote Server"):screen.recording.mov
I cannot recreate behaviour outside of Codespaces. I.e locally or inside of a normal devcontainer. Is this normal/expected or is there an issue here?
More details:
Hi,
I work at iterative.ai and we've built a VS Code extension (DVC for VS Code). One of the main use cases is that you can run, compare, visualize, and track machine learning experiments right in VS Code. The extension can provide real-time updates to pre-defined plots. In order to do this we rely on the extension host's
FileSystemWatcher
. That looks like this:Screen.Recording.2023-02-23.at.1.27.04.pm.mov
We got some reports that "plots live updates" stopped working in Codespaces from our customer success team (iterative/vscode-dvc#3264). Investigating further it appears that the
FileSystemWatcher
's behaviour is different in Codespaces.Please let me know if there is a better place to raise this issue and I will happily move it there.
Thank you.
The original discussion is here: microsoft/vscode-discussions#486 (no response)
Beta Was this translation helpful? Give feedback.
All reactions