Settings in .yamllint config file in same directory as edited YAML file not working

[stevecj]

Information

VIM version

VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Sep 17 2021 09:58:59)
Included patches: 1-3444

Operating System: CentOS Linux release 7.9.2009 (Core)

yamllint version: 1.26.0

What went wrong

Settings in .yamllint (also tried renaming it to ,yamllint.yaml) in same directory as an edited YAML file seem to be ignored. When I run yamllint manually from the same directory, the settings are used.

The contents of my config file are

extends: default

rules:
  document-start: disable  # Don't require "---" at start of file.

Reproducing the bug

Created a .yamllint file with the contents above and then edited a .yaml file in the same directory that did not have an initial "---" line.

Ale reports document-start: missing document start "---" for the first line of the edited yaml file (disabled in config).
Running yamllint <filename> in the same directory from the shell does not report that error.

:ALEInfo

 Current Filetype: yaml
Available Linters: ['circleci', 'spectral', 'swaglint', 'yamllint']
  Enabled Linters: ['circleci', 'spectral', 'swaglint', 'yamllint']
  Ignored Linters: []
 Suggested Fixers:
  'prettier' - Apply prettier to a file.
  'remove_trailing_lines' - Remove all blank lines at the end of a file.
  'trim_whitespace' - Remove all trailing whitespace characters at the end of every line.
  'yamlfix' - Fix yaml files with yamlfix.
 Linter Variables:
let g:ale_yaml_spectral_executable = 'spectral'
let g:ale_yaml_spectral_use_global = 0
let g:ale_yaml_swaglint_executable = 'swaglint'
let g:ale_yaml_swaglint_use_global = 0
let g:ale_yaml_yamllint_executable = 'yamllint'
let g:ale_yaml_yamllint_options = ''
 Global Variables:
let g:ale_cache_executable_check_failures = v:null
let g:ale_change_sign_column_color = 0
let g:ale_command_wrapper = ''
let g:ale_completion_delay = v:null
let g:ale_completion_enabled = 0
let g:ale_completion_max_suggestions = v:null
let g:ale_disable_lsp = 0
let g:ale_echo_cursor = 1
let g:ale_echo_msg_error_str = 'Error'
let g:ale_echo_msg_format = '%code: %%s'
let g:ale_echo_msg_info_str = 'Info'
let g:ale_echo_msg_warning_str = 'Warning'
let g:ale_enabled = 1
let g:ale_fix_on_save = 0
let g:ale_fixers = {}
let g:ale_history_enabled = 1
let g:ale_history_log_output = 1
let g:ale_keep_list_window_open = 0
let g:ale_lint_delay = 200
let g:ale_lint_on_enter = 1
let g:ale_lint_on_filetype_changed = 1
let g:ale_lint_on_insert_leave = 1
let g:ale_lint_on_save = 1
let g:ale_lint_on_text_changed = 'normal'
let g:ale_linter_aliases = {}
let g:ale_linters = {}
let g:ale_linters_explicit = 0
let g:ale_linters_ignore = {}
let g:ale_list_vertical = 0
let g:ale_list_window_size = 10
let g:ale_loclist_msg_format = '%code: %%s'
let g:ale_max_buffer_history_size = 20
let g:ale_max_signs = -1
let g:ale_maximum_file_size = v:null
let g:ale_open_list = 0
let g:ale_pattern_options = v:null
let g:ale_pattern_options_enabled = v:null
let g:ale_root = {}
let g:ale_set_balloons = 0
let g:ale_set_highlights = 1
let g:ale_set_loclist = 1
let g:ale_set_quickfix = 0
let g:ale_set_signs = 1
let g:ale_sign_column_always = 0
let g:ale_sign_error = '>>'
let g:ale_sign_info = '--'
let g:ale_sign_offset = 1000000
let g:ale_sign_style_error = '>>'
let g:ale_sign_style_warning = '--'
let g:ale_sign_warning = '--'
let g:ale_sign_highlight_linenrs = 0
let g:ale_statusline_format = v:null
let g:ale_type_map = {}
let g:ale_use_global_executables = v:null
let g:ale_virtualtext_cursor = 0
let g:ale_warn_about_trailing_blank_lines = 1
let g:ale_warn_about_trailing_whitespace = 1
  Command History:
(executable check - failure) swaglint
(finished - exit code 0) ['/bin/bash', '-c', '''yamllint'' -f parsable ''/tmp/vMdPOaG/120/.yamllint.yaml''']
<<<OUTPUT STARTS>>>
/tmp/vMdPOaG/120/.yamllint.yaml:1:1: [warning] missing document start "---" (document-start)
<<<OUTPUT ENDS>>>
(executable check - failure) spectral
(executable check - failure) swaglint
(finished - exit code 0) ['/bin/bash', '-c', '''yamllint'' -f parsable ''/tmp/vMdPOaG/121/.yamllint.yaml''']
<<<OUTPUT STARTS>>>
/tmp/vMdPOaG/121/.yamllint.yaml:1:1: [warning] missing document start "---" (document-start)
<<<OUTPUT ENDS>>>
(executable check - failure) spectral
(executable check - failure) swaglint
(finished - exit code 0) ['/bin/bash', '-c', '''yamllint'' -f parsable ''/tmp/vMdPOaG/122/.yamllint.yaml''']
<<<NO OUTPUT RETURNED>>>
(executable check - failure) spectral
(executable check - failure) swaglint
(finished - exit code 0) ['/bin/bash', '-c', '''yamllint'' -f parsable ''/tmp/vMdPOaG/123/.yamllint.yaml''']
<<<NO OUTPUT RETURNED>>>
(executable check - failure) spectral
(executable check - failure) swaglint
(finished - exit code 1) ['/bin/bash', '-c', '''yamllint'' -f parsable ''/tmp/vMdPOaG/125/.yamllint.yaml''']
<<<OUTPUT STARTS>>>
/tmp/vMdPOaG/125/.yamllint.yaml:1:1: [error] too many blank lines (1 > 0) (empty-lines)

[hsanson]

I am unable to reproduce this issue. I have in the same folder these two files:

hello.yaml

test:
  - hello
  - world

.yamllint

extends: default

rules:
  document-start: disable  # Don't require "---" at start of file.

Opening the hello.yaml file reports no error from ALE:

  Command History:
(executable check - success) yamllint
(finished - exit code 0) ['/bin/bash', '-c', '''yamllint'' -f parsable ''/tmp/nvimsj1Rl0/1/hello.yaml''']
<<<NO OUTPUT RETURNED>>>
(finished - exit code 0) ['/bin/bash', '-c', '''yamllint'' -f parsable ''/tmp/nvimsj1Rl0/4/hello.yaml''']
<<<NO OUTPUT RETURNED>>>
(finished - exit code 0) ['/bin/bash', '-c', '''yamllint'' -f parsable ''/tmp/nvimsj1Rl0/6/hello.yaml''']
<<<NO OUTPUT RETURNED>>>

Removing the rules inside the .yamllint file causes ALE to report the missing --- at the beginning of the file. This shows that yamllint is properly reading the configuration file.

  Command History:
(executable check - success) yamllint
(finished - exit code 0) ['/bin/bash', '-c', '''yamllint'' -f parsable ''/tmp/nvimav8Ba2/1/hello.yaml''']
<<<OUTPUT STARTS>>>
/tmp/nvimav8Ba2/1/hello.yaml:1:1: [warning] missing document start "---" (document-start)
<<<OUTPUT ENDS>>>

Relevant configuration:

• Latest ALE from master
• Neovim 0.6 compiled from master
• Enabled Linters: ['yamllint']

[stevecj]

Any idea what I can do to figure out why this problem is happening for me? I am not having similar problems with other file types.

[hsanson]

Not much I can do to help. Check the version of yamllint, ALE, and Vim/Neovim you are using. In my case I have:

• Latest ALE from master
• Latest Neovim compiled from master
• yamllint 1.26.0

[yosida95]

According to the yamllint doc, .yamllint file must be placed in the current working directory. https://yamllint.readthedocs.io/en/stable/configuration.html#configuration

So if your .yamllint file is not in the same directory as the cwd of Vim, yamllint will ignore the config file. I could reproduce the issue in this situation.

[mafrosis]

I hit this one. I had to start vim from the same directory that .yamllint is in, else I get smashed with errors