vscode-yaml: DeprecationWarning for Unhandled promise rejections
“Yaml Support” log shows this error:
[Error - 6:11:37 PM] (node:2616) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code
and a lot of errors like this:
[Error - 6:11:37 PM] (node:2616) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 4): #<Object>
redhat.vscode-yaml v0.0.17
Window 10 v1809 x64 Version: 1.28.0 Commit: 431ef9da3cf88a7e164f9d33bf62695e07c6c2a9 Date: 2018-10-05T14:58:53.203Z Electron: 2.0.9 Chrome: 61.0.3163.100 Node.js: 8.9.3 V8: 6.1.534.41 Architecture: x64
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 5
- Comments: 19 (4 by maintainers)
Commits related to this issue
- Merge pull request #127 from redhat-developer/addTriggerCharacters Added trigger characters — committed to bleach31/vscode-yaml by JPinkney 5 years ago
I get these errors once the extension, regardless of whether or not the file is valid Yaml.
+1
I get the same error multiple time
I’ve seen this happening in an environment where my access to the json schema server is blocked (due to firewall or vpn) and “yaml.schemaStore.enable”: true. I believe the extension is trying to download some schemas from the json schema server automatically and failing. I was able to use local schemas using the file protocol and “yaml.schemas” variable. In that case the extension worked just fine. The solution could be as simple as fixing proxy settings or any other connectivity issue.
Thanks everyone for the debugging info! I haven’t found the cause yet but all the diagnostics everyone gave should give me a few places to look!
@JPinkney sorry, when you say “next release” is exactly which release of vscode?
I’m getting the same error, regardless of whether or not the file is valid or not. It only happens when opening a YAML file, the first one. My vscode version is 1.29, and running on MacOS Mojave
If there’s any other information needed to pinpoint the issue, let me know.