Ansible extention errors

[laschlo]

Issue Type: Bug

After installing Ansible extention for VSCode, output for "Ansible Playbook Language Server" keeps giving following error:

[Error - 11:45:31 AM] (node:85329) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 2): #
[Error - 11:45:31 AM] (node:85329) [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.

Steps to reproduce:

1. Install Ansible extention
2. Open Yaml file with Ansible playbook
3. Change file type to ansible
4. Make any change to playbook and save it.

If I'm not mistaken, it only gives errors once language server starts - after each restart of VSCode.
I was able to reproduce that on Win7, Fedora Linux and Mac.

Extension version: 0.5.2
VS Code version: Code 1.28.2 (7f3ce96ff4729c91352ae6def877e59c561f4850, 2018-10-17T00:18:43.347Z)
OS version: Darwin x64 18.2.0

System Info

Item	Value
CPUs	Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz (12 x 2600)
GPU Status	2d_canvas: enabled checker_imaging: disabled_off flash_3d: enabled flash_stage3d: enabled flash_stage3d_baseline: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on native_gpu_memory_buffers: enabled rasterization: enabled video_decode: enabled video_encode: enabled webgl: enabled webgl2: enabled
Load (avg)	1, 2, 2
Memory (System)	16.00GB (1.25GB free)
Process Argv
Screen Reader	no
VM	0%

[yungezz]

Thanks for reporting the issue. investigating.

[alexsaezm]

Same here. I'm trying to move a folder to a remote server when I save and VSCode do it from time to time. But most of the time, that error pops up and it does not copy anything.

Is there a way to debug the extension?

[steffencircle]

I get the same thing, every time i start a new VSCode instance and open an Ansible Playbook:

[Error - 10:21:37] (node:13676) UnhandledPromiseRejectionWarning: #<Object> [Error - 10:21:37] (node:13676) 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 - 10:21:37] (node:13676) [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.

[Drakkai]

I also can confirm that every opening of YAML file throw error:
[Error - 09:59:52] (node:1120) UnhandledPromiseRejectionWarning: #<Object>
[Error - 09:59:52] (node:1120) 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:59:52] (node:1120) [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.

[yungezz]

thanks all for reporting the bug, I'm looking at it.

[danielscamacho]

Same issue here:

[Error - 11:28:14] (node:2336) UnhandledPromiseRejectionWarning: #
[Error - 11:28:14] (node:2336) 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 - 11:28:14] (node:2336) [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.

[plcarman]

Also seeing this on VSCode Version 1.35.0 with Ansible extension version 0.5.2

[njuCZ]

sorry for late reply. I want to solve this problem, however, It seems work well in my local env on VSCode Version 1.40.0 with Ansible extension version 0.5.2
Could anyone help check whether this bug still exists ?

[jhampson-dbre]

I am receiving UnhandledPromiseRejectionWarning message with VSCode 1.40.0 Ansible extension version 0.5.2 from "Ansible Playbook Language Server" output view while connected to remote WSL.

If I reopen VSCode the same .yml file in Windows instead of Remote WSL, I do not get the UnhandledPromiseRejectionWarning message.

[MmAtBosch]

same here.

[Error - 09:01:57] (node:24504) UnhandledPromiseRejectionWarning: #
[Error - 09:01:57] (node:24504) UnhandledPromiseRejectionWarning: #
[Error - 09:01:57] (node:24504) 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:01:57] (node:24504) 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:01:57] (node:24504) [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:01:57] (node:24504) [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:25:56] (node:24504) UnhandledPromiseRejectionWarning: #
[Error - 10:25:56] (node:24504) UnhandledPromiseRejectionWarning: #
[Error - 10:25:56] (node:24504) 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:25:56] (node:24504) 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:26:06] (node:24504) UnhandledPromiseRejectionWarning: #
[Error - 10:26:06] (node:24504) UnhandledPromiseRejectionWarning: #

ansible extension v0.5.2

it looks like when i disable the remote-wsl extension, the problem does not occur.

any fix?

[jhampson-dbre]

Looks like #257 is a duplicate of this issue. It has a potential workaround listed in the comments. I haven't seen any maintainer response on this issue or the other one in some time. @yungezz are you able to revisit this now that there is a proposed fix on the other issue?

[yungezz]

add @mybayern1974 current owner to help on it.

[mybayern1974]

Hi @jhampson-dbre , thank you for raising this problem. While transparently, I have to comment that because of our engineering bandwidth constraint and we are focusing on other higher priority tasks that include azure ansible collection management, we do not have enough bandwidth on resolving this issue right now. We still value feedbacks received here and have put this task into our backlog while there is no eta yet. Meanwhile, given this is an open source project so we definitely welcome any community contribution to this project including the resolving to this issue.
Thank you for your understanding!