You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a python filter fails, (even with filter_mode: any), the actions for that rule are skipped, but there's no indication in the final successful/failed file count. This is logical, because no files were matched for the rule with the failing filter, but for long jobs it's not great to have to scroll back up through the output to see if there was a failure in your python code, especially during development.
The code below shows the following final message:
success 3 / fail 0
# organize run .\filter_fail_test.yaml --working-dir .
# assuming the existence of 3 txt files
rules:
- name: "test"
locations: .
filter_mode: any
filters:
- extension: "txt"
- python: |
return "" + 3
actions:
- echo: "test"
- name: "test1"
locations: .
filters:
- extension: "txt"
actions:
- echo: "test1"
Describe the solution you'd like
A final message including an indication that filters failed. Perhaps:
success 3 / fail 0 / filter fail 4
OR
success 3 / fail 0 / some filters failed
Describe alternatives you've considered
My ideal would be a global halt as described in this issue, but the solution above would be less of a change.
The text was updated successfully, but these errors were encountered:
When a python filter fails, (even with
filter_mode: any
), the actions for that rule are skipped, but there's no indication in the final successful/failed file count. This is logical, because no files were matched for the rule with the failing filter, but for long jobs it's not great to have to scroll back up through the output to see if there was a failure in your python code, especially during development.The code below shows the following final message:
Describe the solution you'd like
A final message including an indication that filters failed. Perhaps:
Describe alternatives you've considered
My ideal would be a global halt as described in this issue, but the solution above would be less of a change.
The text was updated successfully, but these errors were encountered: