syntastic icon indicating copy to clipboard operation
syntastic copied to clipboard

syntastic: error: checker ansible/ansible_lint: can't parse version string (abnormal termination?)

Open lkthomas opened this issue 1 year ago • 1 comments

syntastic: error: checker output: ansible-lint ^[[1;36m6.15^[[0m^[[1;36m.^[[0m^[[1;36m0^[[0m using ansible ^[[1;36m2.14^[[0m^[[1;36m.^[[0m^[[1;36m1^[[0m syntastic: error: checker ansible/ansible_lint: can't parse version string (abnormal termination?)

$ ansible-lint --version ansible-lint 6.15.0 using ansible 2.14.1

$ ansible --version ansible [core 2.14.1] config file = /home/lkthomas/Documents/ansible.cfg configured module search path = ['/home/lkthomas/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules'] ansible python module location = /home/lkthomas/.local/lib/python3.11/site-packages/ansible ansible collection location = /home/lkthomas/.ansible/collections:/usr/share/ansible/collections executable location = /home/lkthomas/.local/bin/ansible python version = 3.11.0 (main, Oct 24 2022, 00:00:00) [GCC 12.2.1 20220819 (Red Hat 12.2.1-2)] (/usr/bin/python3) jinja version = 3.1.2 libyaml = True

lkthomas avatar May 09 '23 01:05 lkthomas

Syntastic is no longer maintained, you should consider switching to something like ALE instead.

However, if you insist to make this work, the problem seems to be that the output of ansible-lint --version when run from Vim contains ANSI colors. Fix that, and syntastic should start working again.

lcd047 avatar May 09 '23 11:05 lcd047