-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
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
ansible-lint broken in VS Code with ansible-compat 25.1.0 and 25.0.0 #454
Comments
@neilgoodman The latest release of ansible-compat fixes this issue |
Which version is this exactly? I still have the problem with 25.1.1 and this seems to be the latest version. |
I just installed the
I don't believe this issue is resolved. I'll try running |
At some point when I was running into this issue, I got the Ansbile VSCode extension to spit out the full traceback (not sure how and it doesn't do it anymore):
I'm no Python developer but the problematic line seems to be this: options.cache_dir = get_cache_dir(pathlib.Path(options.project_dir)) I'm not sure how From the traceback I seems I'm not using a virtual env, so I'm getting into the From the traceback it also seems that Side note: The fix that @audgirka talked about is most likely 2a8732f. Strangely, this commit also removed the In any case, these changes seem to completely drop the use of |
Summary
ansible-compat 25.1.0 and 25.0.0 cause ansible-lint to throw an error within the Ansible 25.1.0 plugin in VS Code, breaking linting from within the editor:
Issue Type
OS / ENVIRONMENT
I am on Arch Linux:
I'm using VS Code 1.96.4 and Ansible plugin v25.1.0
STEPS TO REPRODUCE
.vscode/ansible-compat-lint-vscode-bug.code-workspace
v25.1.0
)ansible/test_playbook.yaml
file and the error message should popupansible-compat
24.10.0, follow steps 1-4, error message doesn't popup and the file should highlight a linting issueDesired Behavior
For linting to work within VS Code as it did with 24.10.0
Actual Behavior
Linting breaks with the above error within VS Code and ansible-compat 25.1.0
minimum complete verifiable example
The text was updated successfully, but these errors were encountered: