search

VSChina / vscode-ansible

VSCode extension for ansible
Other
77 stars 48 forks source link

Unhandled Promise Rejection #257

Open marmelin opened 5 years ago

marmelin commented 5 years ago

Environment

Reproduce steps

1) Install VSCode 2) Install Ansible Plugin

Svince123 commented 4 years ago

I have it too annoying bug

w0203j commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

@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 commented 4 years ago

@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 commented 4 years ago

Same issue here on:

OS: Ubuntu 19.10 Vscode: 1.42.1 Extension: 0.5.2

MetricMike commented 4 years ago

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

Underlying issue from https://github.com/redhat-developer/vscode-yaml/issues/127 was fixed in https://github.com/redhat-developer/yaml-language-server/pull/183 and released in 0.5.8, but vscode-ansible bundles version 0.4.0.

Easing that constraint should fix.

Drakkai commented 4 years ago

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 commented 4 years ago

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:

fkshom commented 4 years ago

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 commented 4 years ago

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

jhampson-dbre commented 4 years ago

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

https://github.com/VSChina/vscode-ansible/issues/203#issuecomment-674082495