Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] CI: Bandit: 1 configuration not found (python-code-quality.yml) #3682

Open
neteler opened this issue May 2, 2024 · 3 comments
Open
Labels
bug Something isn't working CI Continuous integration

Comments

@neteler
Copy link
Member

neteler commented May 2, 2024

Describe the bug

This just came to my attention while checking open PRs:

Actions workflow (python-code-quality.yml) complains about:

1 configuration not found

Warning: Code scanning cannot determine the alerts introduced by this pull request, because 1 configuration present on refs/heads/main was not found:
Actions workflow (python-code-quality.yml)

    ❓  .github/workflows/python-code-quality.yml:python-checks/bandit-version:1.7.8/black-version:23.1.0/flake8-version:3.9.2/min-python-version:3.7/os:ubuntu-22.04/pylint-version:2.12.2/python-version:3.10

See e.g.:

#3671

image

--> https://github.com/OSGeo/grass/runs/24278615418

If this is known/expected just close this report.

@neteler neteler added bug Something isn't working CI Continuous integration labels May 2, 2024
@echoix
Copy link
Member

echoix commented May 2, 2024

I see where it comes from. A similar thing happened for CodeQL when we adjusted the languages names. Since the strategy matrix values are used to generate the configuration slug, changing any strategy matrix will create a different configuration.

Here, it's because it still expects results from the configuration that had the old black version like before.

The way out:

  1. in GitHub security scanning tab, delete the old configuration. This will solve for this time.
    Or
  2. Change the strategy matrix values with tool versions to job-level or workflow-level env vars instead. We will probably need to adjust the required status checks to the new name of the check if it used that job, and that would be a good thing.

@wenzeslaus
Copy link
Member

I don't see anything in the security tab for the name of the configuration or a button to delete it. I see links to the workflow. Rest is read-only. Screenshots attached. Let me know if there is anything I can explore more.

Screenshot from 2024-05-05 20-35-59
Screenshot from 2024-05-05 20-35-31

@echoix
Copy link
Member

echoix commented May 6, 2024

I went and delete it a while after, the same or next day after no answer. I was able to "fix" that part easily myself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working CI Continuous integration
Projects
None yet
Development

No branches or pull requests

3 participants