ERROR initialize:initialize: failed to add schemas from catalog

[Spitfire1900]

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)

 WARN initialize:initialize: failed to fetch catalog error=error sending request: JsValue(TypeError: fetch failed
TypeError: fetch failed
    at Object.fetch (node:internal/deps/undici/undici:11576:11)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5))

Caused by:
    JsValue(TypeError: fetch failed
    TypeError: fetch failed
        at Object.fetch (node:internal/deps/undici/undici:11576:11)
        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)) self.root=file:///c%3A/Bitbucket/myproject
ERROR initialize:initialize: failed to add schemas from catalog error=error sending request: JsValue(TypeError: fetch failed
TypeError: fetch failed
    at Object.fetch (node:internal/deps/undici/undici:11576:11)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)) self.root=file:///c%3A/Bitbucket/myproject
 WARN no notification handler registered method=$/setTrace

[JounQin]

That doesn't help anything.

Please provide a minimal but runnable online reproduction.

[Spitfire1900]

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.

[JounQin]

Based on fetch failed, it could just be a request error.

[Spitfire1900]

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.

[Licapule]

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.
Here is all output in vscode output Even Better TOML LSP pane

 INFO registered request handler method="initialize"
 INFO registered request handler method="textDocument/foldingRange"
 INFO registered request handler method="textDocument/documentSymbol"
 INFO registered request handler method="textDocument/formatting"
 INFO registered request handler method="textDocument/completion"
 INFO registered request handler method="textDocument/hover"
 INFO registered request handler method="textDocument/documentLink"
 INFO registered request handler method="textDocument/semanticTokens/full"
 INFO registered request handler method="textDocument/prepareRename"
 INFO registered request handler method="textDocument/rename"
 INFO registered notification handler method="initialized"
 INFO registered notification handler method="textDocument/didOpen"
 INFO registered notification handler method="textDocument/didChange"
 INFO registered notification handler method="textDocument/didSave"
 INFO registered notification handler method="textDocument/didClose"
 INFO registered notification handler method="workspace/didChangeConfiguration"
 INFO registered notification handler method="workspace/didChangeWorkspaceFolders"
 INFO registered request handler method="taplo/convertToJson"
 INFO registered request handler method="taplo/convertToToml"
 INFO registered request handler method="taplo/listSchemas"
 INFO registered request handler method="taplo/associatedSchema"
 INFO registered notification handler method="taplo/associateSchema"
 WARN initialize:initialize: failed to fetch catalog error=error sending request: JsValue(TypeError: fetch failed
TypeError: fetch failed
    at Object.fetch (node:internal/deps/undici/undici:12293:11)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5))

Caused by:
    JsValue(TypeError: fetch failed
    TypeError: fetch failed
        at Object.fetch (node:internal/deps/undici/undici:12293:11)
        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)) self.root=file:///c%3A/Users/lic/Documents/Projects/myproject
ERROR initialize:initialize: failed to add schemas from catalog error=error sending request: JsValue(TypeError: fetch failed
TypeError: fetch failed
    at Object.fetch (node:internal/deps/undici/undici:12293:11)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)) self.root=file:///c%3A/Users/lic/Documents/Projects/myproject
 WARN update_configuration:initialize: failed to fetch catalog error=error sending request: JsValue(TypeError: fetch failed
TypeError: fetch failed
    at Object.fetch (node:internal/deps/undici/undici:12293:11)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5))

Caused by:
    JsValue(TypeError: fetch failed
    TypeError: fetch failed
        at Object.fetch (node:internal/deps/undici/undici:12293:11)
        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)) self.root=root:///
ERROR update_configuration:initialize: failed to add schemas from catalog error=error sending request: JsValue(TypeError: fetch failed
TypeError: fetch failed
    at Object.fetch (node:internal/deps/undici/undici:12293:11)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)) self.root=root:///
 WARN update_configuration:initialize: failed to fetch catalog error=error sending request: JsValue(TypeError: fetch failed
TypeError: fetch failed
    at Object.fetch (node:internal/deps/undici/undici:12293:11)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5))

Caused by:
    JsValue(TypeError: fetch failed
    TypeError: fetch failed
        at Object.fetch (node:internal/deps/undici/undici:12293:11)
        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)) self.root=file:///c%3A/Users/lic/Documents/Projects/myproject
ERROR update_configuration:initialize: failed to add schemas from catalog error=error sending request: JsValue(TypeError: fetch failed
TypeError: fetch failed
    at Object.fetch (node:internal/deps/undici/undici:12293:11)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)) self.root=file:///c%3A/Users/lic/Documents/Projects/myproject
 WARN update_configuration:initialize: failed to fetch catalog error=error sending request: JsValue(TypeError: fetch failed
TypeError: fetch failed
    at Object.fetch (node:internal/deps/undici/undici:12293:11)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5))

Caused by:
    JsValue(TypeError: fetch failed
    TypeError: fetch failed
        at Object.fetch (node:internal/deps/undici/undici:12293:11)
        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)) self.root=file:///c%3A/Users/lic/Documents/Projects/myproject
ERROR update_configuration:initialize: failed to add schemas from catalog error=error sending request: JsValue(TypeError: fetch failed
TypeError: fetch failed
    at Object.fetch (node:internal/deps/undici/undici:12293:11)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)) self.root=file:///c%3A/Users/lic/Documents/Projects/myproject

There's nothing output in Even Better TOML output pane.

When I modify the config of the plugin, a new warning appears:

 WARN no notification handler registered method=$/setTrace

I have no idea about this problem.

Windows 11, VSCode 1.91.1, Even Better TOML 0.19.2

[nilreml]

I'm experiencing the same issue behind a corporate proxy, so I dug in:

The root cause appears to be undici not respecting HTTP_PROXY/NO_PROXY etc. env vars, fixed here.

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).

[bersbersbers]

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 curl:

• https://www.schemastore.org/api/json/catalog.json
• https://json.schemastore.org/pyproject.json

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

	let mut index = match self.fetch_external(index_url).await {
	Ok(idx) => idx,
	Err(error) => {
	tracing::warn!(?error, "failed to fetch catalog");
	if let Ok(s) = self.cache.load(index_url, true).await {
	return Ok(serde_json::from_value((*s).clone())?);
	}
	return Err(error);
	}
	};

[Licapule]

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.

[bersbersbers]

setx NODE_EXTRA_CA_CERTS Path\To\ZScaler-Root-CA.pem fixed the issue for me.

[nerditation]

I'm seeing the same error, i.e. JsValue(TypeError: fetch failed...), but it's nothing to do with proxies in my case. I can visit the schemastore website in browser or with curl without problem.

however, the url https://www.schemastore.org/api/json/catalog.json returns a 301 Moved response. could this be the cause? I'm guessing the TypeError might be because the reponse body is not in json format?

UPDATE:

after some tinkering, it seems it is a proxy issue after all. I forgot my curl is configured to use proxy.

however, there's still something wrong, but I cannot figure out exactly. here's what I managed to figure out:

• the vscode extension host process DOES inherit the env variables of the main UI process

  this can be checked using this vscode-api-explorer extension. when I start the editor with https_proxy=http://ip:port codium, I can successfully fetch() the catalog.json in the js repl.

• the wasm lsp server DOES seems to inherit the env variables of the extension host, as I did see a change in the taplo lsp output log when I set RUST_LOG

• somehow, when the wasm lsp server calls the reqwest::fetch(), which calls the runtime's fetch() imported via wasm_bindgen, it does NOT respect the https_proxy env variable? even if I set the https_proxy variable in the evenBetterToml.taplo.environment config?

• so the fetch API imported by wasm_bindgen behaves differently than nodejs builtin fetch() API?

  https://github.com/seanmonstar/reqwest/blob/0cf27a901b4d77c1704ec52cc66eb92bbc9fd857/src/wasm/client.rs#L12-L16

at this point, I don't know where to look at. is the wasm lsp server running inside a different version of nodejs runtime or something?

[nerditation]

• so the fetch API imported by wasm_bindgen behaves differently than nodejs builtin fetch() API?

well, after some more digging, it turns out, nodejs's fetch() API does NOT respect the https_proxy env out of the box. (but it seems in the progress to support it. see nodejs/node#57165)

on the contrary, vscode patches the global fetch() function to use eletron's fetch() internally, which is essentially the chromium's fetch(), exactly for the purpose to allow the user to have a proxy configuration. it is implemented here:

https://github.com/microsoft/vscode/blob/8b14930e34f85a7963797062211b680f380fd4d4/src/vs/workbench/api/node/proxyResolver.ts#L117

see also microsoft/vscode#228696 and microsoft/vscode#228697

---

I think for now, I'll use a taplo cli as the lsp server and disable the bundled wasm one. it works for me.

meanwhile, should the bundled wasm server implement a workaround itself, e.g. something like this maybe?

undici.setGlobalDispatcher(new undici.EnvHttpProxyAgent())

since it could take some time before nodejs/node#57165 is finished, and even after it is done, it's not clear how soon will electron catch up nodejs, and vscode to catch up electron...