Unhandled Promise Rejection

[marmelin]

Environment

• Extension version: v0.5.2
• OS Type: Windows 10
• VSCODE:

Version: 1.40.0 (user setup)
Commit: 86405ea23e3937316009fc27c9361deee66ffbf5
Datum: 2019-11-06T17:02:13.381Z
Electron: 6.1.2
Chrome: 76.0.3809.146
Node.js: 12.4.0
V8: 7.6.303.31-electron.0
Betriebssystem: Windows_NT x64 10.0.17763

Summary

Installed Plugin repeatedly issues the following error:

[Error - 10:57:16] (node:21072) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 76)
[Error - 10:57:18] (node:21072) UnhandledPromiseRejectionWarning: #<Object>
[Error - 10:57:18] (node:21072) UnhandledPromiseRejectionWarning: #<Object>
[Error - 10:57:18] (node:21072) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 78)
[Error - 10:57:18] (node:21072) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 78)
[Error - 10:57:53] (node:21072) UnhandledPromiseRejectionWarning: #<Object>
[Error - 10:57:53] (node:21072) UnhandledPromiseRejectionWarning: #<Object>
[Error - 10:57:53] (node:21072) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 80)
[Error - 10:57:53] (node:21072) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 80)

Reproduce steps

1. Install VSCode
2. Install Ansible Plugin

[Svince123]

I have it too annoying bug

[w0203j]

Same here

[Error - 1:44:36 PM] (node:34154) UnhandledPromiseRejectionWarning: #<Object>
[Error - 1:44:36 PM] (node:34154) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 3)
[Error - 1:44:36 PM] (node:34154) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 3)
[Error - 1:44:36 PM] (node:34154) [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.
[Error - 1:44:36 PM] (node:34154) [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.

[kitos9112]

Facing the exact same issue, a very quick search via Google led me to this Github issue related to another well-known YAML LSP VSCode extension
YAML-validation

[AndrewDi]

@kitos9112 Do you mean this issue raised by another extension "YAML-validation"? but ansible plugin only use "Yaml validation. Yaml validation by leverage Yaml language server."

[kitos9112]

@AndrewDi - that's correct. Not quite familiar with the development of VScode extensions so cannot tell much more than my findings. I'm just wondering whether this is happening because of the use of a proxy.

[Varkal]

Same issue here on:

OS: Ubuntu 19.10
Vscode: 1.42.1
Extension: 0.5.2

[MetricMike]

vscode-ansible and vscode-yaml are both clients of yaml-language-server

Underlying issue from redhat-developer/vscode-yaml#127 was fixed in redhat-developer/yaml-language-server#183 and released in 0.5.8, but vscode-ansible bundles version 0.4.0.

Easing that constraint should fix.

[Drakkai]

The problem still exists

[Error - 09:09:06] (node:58748) UnhandledPromiseRejectionWarning: #<Object>
[Error - 09:09:06] (node:58748) UnhandledPromiseRejectionWarning: #<Object>
[Error - 09:09:06] (node:58748) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
[Error - 09:09:06] (node:58748) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
[Error - 09:09:06] (node:58748) [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.
[Error - 09:09:06] (node:58748) [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.

OS: Windows 10 1803
VSCode: 1.45.1
Extension: 0.5.2

[mirfire]

Happening on VSCode 1.46.1 as well.

[Error - 09:31:09] (node:11588) UnhandledPromiseRejectionWarning: #<Object>
[Error - 09:31:09] (node:11588) UnhandledPromiseRejectionWarning: #<Object>
[Error - 09:31:09] (node:11588) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
[Error - 09:31:09] (node:11588) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
[Error - 09:31:09] (node:11588) [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.
[Error - 09:31:09] (node:11588) [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.
[Error - 10:05:53] (node:11588) UnhandledPromiseRejectionWarning: #<Object>
[Error - 10:05:53] (node:11588) UnhandledPromiseRejectionWarning: #<Object>
[Error - 10:05:53] (node:11588) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 4)
[Error - 10:05:53] (node:11588) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 4)
[Error - 16:06:25] (node:11588) UnhandledPromiseRejectionWarning: #<Object>
[Error - 16:06:25] (node:11588) UnhandledPromiseRejectionWarning: #<Object>
[Error - 16:06:25] (node:11588) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 6)
[Error - 16:06:25] (node:11588) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 6)

OS: Windows 10 1803
VSCode: 1.46.1
Extension: 0.5.2

Installed extensions:

• [email protected]
• [email protected]
• [email protected]
• [email protected]
• [email protected]
• [email protected]
• [email protected]
• [email protected]

[fkshom]

I worte a workaround patch based on @MetricMike 's information.
The error is no longer printed, but the extent of the impact is unknown.

https://gist.github.com/fkshom/cde7c17dc2a1352ce8676b3bb56845af

[rory-ye-nv]

it's half years now, and this bug is still no one take fix.

[jhampson-dbre]

@fkshom can you open a pull request with your patch?

On the other issue for problem the maintainer said they wouldn't have time to get to this issue soon but would take a PR.

If not, I can open one. This problem as gotten so frequent for me I've considered abandoning the extension.

#203 (comment)