-
-
Notifications
You must be signed in to change notification settings - Fork 123
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
ERROR initialize:initialize: failed to add schemas from catalog #585
Comments
That doesn't help anything. Please provide a minimal but runnable online reproduction. |
Unfortunately, this is all the output that's available in the even better TOML output pane in VScode. I have also been unable to reproduce it on other workstations. |
Based on |
I am behind a corporate web proxy in this scope. I've worked with our IT Security department to allow-list the schema catalog, but I can't be certain that the web proxy is the issue when the fetched resource that failed isn't dumped to console. |
I have the same trouble for 3 days. I tried to reinstall the plugin, but it doesn't work. I even tried running it on Ubuntu WSL.
There's nothing output in When I modify the config of the plugin, a new warning appears:
I have no idea about this problem. Windows 11, VSCode 1.91.1, Even Better TOML 0.19.2 |
I'm experiencing the same issue behind a corporate proxy, so I dug in: The root cause appears to be undici not respecting The fix was released with undici v6.14.0, which in turn made it into nodejs v22. I reckon upgrading to nodejs v22 should fix the issue (though I'm ill-equipped to do so at this time). |
I am seeing the same thing. I suspect it is due to ZScaler being rolled out in our company - at least when I turn off ZScaler, this error goes away (and is replaced by another, hopefully unrelated one). But without knowing which URL fails, I have no way of knowing how to work with IT to get this unblocked. Again, I suspect it's one of the following, but those all work fine in the browser and using External fetches should really be logged, at least in error cases. The magic happens here: if anyone knows rust, please send a PR hacking in some debug output :) taplo/crates/taplo-common/src/schema/associations.rs Lines 332 to 341 in 18b86da
|
It seems that this problem only happens in VSCode stable version. After switching between the two versions of VSCode several times, I have been using it very well in VSCode Insider for about 3 months. |
|
Getting the following error in the Even Better TOML LSP output pane:
Even Better TOML: 0.19.2
VSCode: 1.87.2
Windows: 11 (build 22631)
The text was updated successfully, but these errors were encountered: