We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
5.6.0-dev.20240729
Not a regression
No response
microsoft/vscode#221583
It appears that TS sometimes tries creating a directory watcher for in memory files. For example, I see these calls in the TS Server logs:
Info 46165[16:37:11.625] Starting updateGraphWorker: Project: /dev/null/inferredProject1* Info 46166[16:37:11.646] DirectoryWatcher:: Added:: WatchInfo: ^/vscode-chat-code-block/899b87a4-39f1-4438-af0b-c7a57080a918/response_0/0#... 0 undefined Project: /dev/null/inferredProject1* WatchType: Failed Lookup Locations Info 46167[16:37:11.646] event: {"seq":0,"type":"event","event":"createDirectoryWatcher","body":{"id":4619,"path":"^/vscode-chat-code-block/899b87a4-39f1-4438-af0b-c7a57080a918/response_0/0...","recursive":false,"ignoreUpdate":true}} Info 46168[16:37:11.647] Elapsed:: 0.07062499225139618ms DirectoryWatcher:: Added:: WatchInfo: ^/vscode-chat-code-block/899b87a4-39f1-4438-af0b-c7a57080a918/response_0/0#... 0 undefined Project: /dev/null/inferredProject1* WatchType: Failed Lookup Locations
These are purely in-memory files so we shouldn't create watchers or directory watchers for them\
Watchers should not be created. There's no directory that can change here
The text was updated successfully, but these errors were encountered:
Going to add some workarounds on the VS Code side but would be best to avoid these calls in the first place
Sorry, something went wrong.
~/Library
sheetalkamat
No branches or pull requests
π Search Terms
π Version & Regression Information
5.6.0-dev.20240729
Not a regression
β― Playground Link
No response
π» Code
microsoft/vscode#221583
It appears that TS sometimes tries creating a directory watcher for in memory files. For example, I see these calls in the TS Server logs:
π Actual behavior
These are purely in-memory files so we shouldn't create watchers or directory watchers for them\
π Expected behavior
Watchers should not be created. There's no directory that can change here
Additional information about the issue
No response
The text was updated successfully, but these errors were encountered: