Crash since 24.5.0: 1 MatchError called incorrectly as line numbers start with 1 #4177
Assignees
Labels
Comments
nvuillam
added a commit
to oxsecurity/megalinter
that referenced
this issue
May 19, 2024
nvuillam
added a commit
to oxsecurity/megalinter
that referenced
this issue
May 19, 2024
* [automation] Auto-update linters version, help and documentation * [MegaLinter] Apply linters fixes * Downgrade lightning flow scanner Until bug is fixed: https://github.com/Lightning-Flow-Scanner/lightning-flow-scanner-vsce/issues/100 * Downgrade ansible-lint to v24.2.3 Related to ansible/ansible-lint#4177 * fix pylint issues * [MegaLinter] Apply linters fixes --------- Co-authored-by: nvuillam <nvuillam@users.noreply.github.com>
|
@nvuillam Unless you can update the description to include a reproducer, we will need to to close thing bug. |
|
@ssbarnea the test files are located here (and they are the same for ages :) ) https://github.com/oxsecurity/megalinter/tree/main/.automation/test/ansible/bad/ansible Does it help ? |
ssbarnea
added a commit
that referenced
this issue
May 31, 2024
ssbarnea
added a commit
that referenced
this issue
May 31, 2024
|
@ssbarnea thanks ! |
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Summary
ansible-lint returns the following error
MatchError called incorrectly as line numbers start with 1
Issue Type
OS / ENVIRONMENT
ansible-lint 24.5.0 using ansible-core:2.16.6 ansible-compat:24.5.1 ruamel-yaml:0.18.6 ruamel-yaml-clib:0.2.8STEPS TO REPRODUCE
Desired Behavior
No crash :)
Actual Behavior
crash with
1 MatchError called incorrectly as line numbers start with 1You can see the error in MegaLinter build log: https://github.com/oxsecurity/megalinter/actions/runs/9149776695/job/25153984448?pr=3559
The text was updated successfully, but these errors were encountered: