Wrong file links in problems pane about vscode-ansible HOT 7 CLOSED

Please find a way to reproduce the problem and describe it. For me clicking on the reported errors opened the files at correct lines.

Do you happen to have a custom ansible lint config? If so please include it in the report, it can affect how the linter runs. Also useful to run linter locally.

Extremely important: assure you have the latest linter version from pypi.

It is key to identify if the linter reports bad paths or something else is happening.

from vscode-ansible.

Hi,

I'm on Debian with ansible-lint packaged :

$ ansible-lint --version
ansible-lint 4.1.0+dfsg.1

I'm in an environment where I can't use pypi, but only Debian Packages.

There is (apparently) no issue with ansible-lint itself. The paths from ansible-lint report are correct.

There is no custom ansible-lint configuration that I'm aware of.

from vscode-ansible.

I've tried on macOS Big Sur with VSCode 1.56.1, ansible-lint 4.3, Python 3.9.1 and the same Ansible project.
Everything is displayed correctly.

There is probably something special on my Debian workstation. I'll let you know if I find the issue or if I have more information for you.

Thank you for your time and effort 👍

from vscode-ansible.

I've created a blank Ansible project, with no reference to external roles…
I get the same file link error.

On my Debian setup, I've tried to disable all extensions but the ones that are also installed on my Mac (Ansible Language 0.4.2, Jupyter 2021.3.832593372, Pylance 2021.5.1, Python 2021.5.82.9140558, YAML 0.18.0). Same file link error.

from vscode-ansible.

I do know for sure that at some point I changed something around the formatting output of ansible-lint. I will close this bug becuase ansible-lint 4.1 is not supported, the only version supported is the latest.

from vscode-ansible.

I understand the decision, but I still think that dropping support for the only version available in the current stable version of Debian is a bit harsh.

I'll try to find other ways to install a more recent version of ansible-lint but leaving the comfort (and peace of mind) of using only Debian packages is frustrating.

Thanks again for you work on these tools 👍

from vscode-ansible.

Please contact deb packagers and tell them that I am happy to help. I want to see them engaging with upstream projects on packaging. Sadly out of more than a 20 notable python projects I maintain I had only one case in the last years where packagers contacted the us and that was a dependency bug.

As now everyone has CI/CD pipelines it does make sense to automate packaging directly upstream. I am more than happy to welcome new github workflows that do that.

from vscode-ansible.