-
Notifications
You must be signed in to change notification settings - Fork 91
Autocompletion doesn't work when ExecutionEnvironment is enabled #472
Comments
I am also experiencing this. Extension v.1.0.90 - 1.0.98 Reverting to v0.14.71 allows me to get autocomplete, flyover docs, etc. Also of interesting note... Downgrading to 0.14.71, and then upgrading back to 1.0.90, results in this working again. I'm guessing that 0.14.71 is populating the cache. |
@nbruniaux, could you please try out what @ptoal suggested? Please let us know if the problem still exists. |
Hello, I couldn't test @ptoal's suggestion but autocompletion is now partially working for me. selinux was in enforcing mode, I switched it to permissive mode and restarted vscode... autocompletion started working! I still have a problem with adjacent collections, autocomplete doesn't work for them but it seems that an issue is already open for that: #123 |
I did a bit more digging on this. I don't think it's specific to a version, after all. I may have been changing multiple things at the same time, during troubleshooting. Taking a bit more of a methodical approach:
After resetting my ansible configuration in VSCode, things seem to be working correctly now. I think what may have happened is that I had paths for my virtualenv in the extension settings and this caused a problem with the language server. I don't really know. All I know for sure is that before, the |
@nbruniaux, thanks for updating. Feel free to close the issue if you do not face the issue anymore. Meanwhile, here's a quick tip to support the playbook adjacent collection: This should work and should give auto-completions straight away. |
Summary
Autocompletion doesn't work when EE is enabled
ansible-lint works fine.
Extension version
1.0.93
VS Code version
1.72.2
Ansible Version
OS / Environment
Red Hat Enterprise Linux release 8.6 (Ootpa)
Relevant log output
The text was updated successfully, but these errors were encountered: