-
Notifications
You must be signed in to change notification settings - Fork 33
"no valid configuration file found (0 configs were invalid)" #129
Comments
@jack-om Thank you for filing this issue. Tagging @brendongo who is working on Semgrep Action errors and improvements. |
Hi @jack-om are you running the semgrep action in a way different from the default instructions?
|
If you can rerun with the environment variable |
Hi @brendongo, the .github/workflows/semgrep.yml
Current output Here are the results, after adding
Previous output The strange thing is that I didn't modify the action file between the last time it worked (Friday), and now. Here is expected output, using the same action file during an execution on Friday.
The only real difference that I see is:
|
@jack-om any chance you can join the community slack: https://r2c.dev/slack I think we have an idea of what's happening |
Confirmed that this happens if all items in a policy have both "notify" and "block" disabled. Fix should be to prevent or warn on this type of configuration. |
Going to add a check with https://github.com/returntocorp/semgrep-action/pull/133 that has a helpful message while we don't have the guarantee that rules from server will be non-empty. |
@brendongo Is this issue resolved with your pre-2021 work? |
Greetings! Testing out the platform, and enjoying things so far. Got this error in my Github Actions pipeline, and followed your request to post it for analysis. Maybe related to #112?
The text was updated successfully, but these errors were encountered: