-
Notifications
You must be signed in to change notification settings - Fork 767
New issue
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
Exception on file watcher creation in VS Code with Node 14 #1392
Comments
Copying the logs:
This file watcher is broken anyway (#923), so this doesn't actually break things at the moment. The most recent version of Pylance is just better about reporting why the watcher failed to be registered. |
What can I do to Just verified that the If I manually downgrade it to node12, it worked fine. |
So this error won't cause Pylance launching failure? Then why my Pylance just doesn't work. |
This definitely should not cause Pylance to not work. If it's not working, these messages are unrelated and a new issue with the template filled out would be appreciated. |
The next release changes this message to a warning; this will at least mean it's not shown in the default log level so people think something's gone wrong. File watching outside the workspace is more generally covered in #923 and has yet to be fixed. |
This issue has been fixed in version 2021.6.1, which we've just released. You can find the changelog here: https://github.com/microsoft/pylance-release/blob/main/CHANGELOG.md#202161-9-june-2021 |
I'm seeing this behavior on v2021.8.0.
VS Code 1.59.0 |
Reopening; a recent refactor to this code has changed how we log it so that it's present again. Again, I will assert that this does not affect anything negatively; we know that these specific watchers fail, but they do not actually cause any problems for the analysis except that #923 is not yet fixed. |
I've re-fixed this for the next release. |
fixed in 2021.8.1 release. |
I'm seeing those errors in my logs when using VS Code 1.63.2 + Pylance 2022.1.1 (pyright 4f61d443) |
Same as this:
microsoft/vscode-python#16380
The text was updated successfully, but these errors were encountered: