We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
It looks like the linter finds a lot of errors in tempfiles or so. Do I miss a setting somewhere?
v24.10.0
1.93.1
ansible [core 2.17.5] config file = /home/jan/dev/jansible/ansible.cfg configured module search path = ['/home/jan/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules'] ansible python module location = /usr/lib/python3.12/site-packages/ansible ansible collection location = /home/jan/.ansible/collections:/usr/share/ansible/collections executable location = /usr/bin/ansible python version = 3.12.7 (main, Oct 1 2024, 11:15:50) [GCC 14.2.1 20240910] (/usr/bin/python) jinja version = 3.1.4 libyaml = True
Arch Linux
▶ ansible-lint --version [WARNING]: log file at /var/log/ansible.log is not writeable and we cannot create it, aborting
ansible-lint 24.9.3.dev0 using ansible-core:2.17.5 ansible-compat:24.9.1 ruamel-yaml:0.18.6 ruamel-yaml-clib:0.2.8
No response
The text was updated successfully, but these errors were encountered:
@janvanveldhuizen We need a bit more information to look into this. Can you provide the steps for recreating this bug so we can try to replicate it?
Sorry, something went wrong.
No branches or pull requests
Summary
It looks like the linter finds a lot of errors in tempfiles or so. Do I miss a setting somewhere?
Extension version
v24.10.0
VS Code version
1.93.1
Ansible Version
OS / Environment
Arch Linux
▶ ansible-lint --version
[WARNING]: log file at /var/log/ansible.log is not writeable and we cannot create it, aborting
ansible-lint 24.9.3.dev0 using ansible-core:2.17.5 ansible-compat:24.9.1 ruamel-yaml:0.18.6 ruamel-yaml-clib:0.2.8
Relevant log output
No response
The text was updated successfully, but these errors were encountered: