After the last issues in a file reported by ansible-lint are fixed, those still get shown about vscode-ansible HOT 8 CLOSED

I have the same issue. VSCodium on Ubuntu 21.04:
Version: 1.56.0
Commit: cfa2e218100323074ac1948c885448fdf4de2a7f
Date: 2021-05-09T15:54:41.116Z
Electron: 12.0.4
Chrome: 89.0.4389.114
Node.js: 14.16.0
V8: 8.9.255.24-electron.0
OS: Linux x64 5.11.0-16-generic snap

ansible-lint 5.0.8 using ansible 2.10.8
Ansible Language extension v0.4.2

from vscode-ansible.

Same issue

Ansible Language extension v0.4.3
ansible-lint 5.0.8 using ansible 2.10.9

Version: 1.56.2
Commit: 054a9295330880ed74ceaedda236253b4f39a335
Date: 2021-05-12T17:44:30.902Z (4 days ago)
Electron: 12.0.4
Chrome: 89.0.4389.114
Node.js: 14.16.0
V8: 8.9.255.24-electron.0
OS: Darwin x64 20.4.0

from vscode-ansible.

I confirm the bug and I would be very happy to review a PR that address it.

from vscode-ansible.

I've installed the 0.4.4 update and still get this issue. I used code-server with autosave on delay.

"files.autoSave": "afterDelay"
"files.autoSaveDelay": 1000

from vscode-ansible.

You did not mention if manually saving the file works (expect up to 3s delay). For me it does seem to work. You may want to check the loggers and see what happens.

from vscode-ansible.

Thanks for reply.
I've tested it with "files.autoSaveDelay": 6000 and also with "files.autoSave": "off". Still get an issue reported till I close/open the yaml file.

from vscode-ansible.

#122 fixed the issue. Thank you!

from vscode-ansible.

i can confirm that insattlling version 0.4.5 fixed the issue. thank you!

from vscode-ansible.