-
-
Notifications
You must be signed in to change notification settings - Fork 242
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
Upgrade python version #2312
Upgrade python version #2312
Conversation
🦙 MegaLinter status:
|
Descriptor | Linter | Files | Fixed | Errors | Elapsed time |
---|---|---|---|---|---|
✅ BASH | bash-exec | 7 | 0 | 0.02s | |
✅ BASH | shellcheck | 7 | 0 | 0.48s | |
✅ BASH | shfmt | 7 | 0 | 0 | 0.39s |
✅ COPYPASTE | jscpd | yes | no | 2.79s | |
✅ DOCKERFILE | hadolint | 105 | 0 | 10.26s | |
✅ JSON | eslint-plugin-jsonc | 21 | 0 | 0 | 2.9s |
✅ JSON | jsonlint | 19 | 0 | 0.28s | |
✅ JSON | v8r | 21 | 0 | 14.78s | |
markdownlint | 309 | 0 | 229 | 7.31s | |
✅ MARKDOWN | markdown-link-check | 309 | 0 | 6.11s | |
✅ MARKDOWN | markdown-table-formatter | 309 | 0 | 0 | 22.24s |
✅ OPENAPI | spectral | 1 | 0 | 0.86s | |
bandit | 176 | 45 | 3.89s | ||
✅ PYTHON | black | 176 | 0 | 0 | 4.83s |
✅ PYTHON | flake8 | 176 | 0 | 3.59s | |
✅ PYTHON | isort | 176 | 0 | 0 | 0.85s |
✅ PYTHON | mypy | 176 | 0 | 7.68s | |
✅ PYTHON | pylint | 176 | 0 | 14.0s | |
pyright | 176 | 276 | 20.63s | ||
✅ REPOSITORY | checkov | yes | no | 31.89s | |
✅ REPOSITORY | git_diff | yes | no | 0.39s | |
✅ REPOSITORY | secretlint | yes | no | 9.26s | |
✅ REPOSITORY | trivy | yes | no | 28.48s | |
✅ SPELL | cspell | 730 | 0 | 22.64s | |
✅ SPELL | misspell | 551 | 0 | 0 | 0.91s |
✅ XML | xmllint | 3 | 0 | 0 | 0.85s |
✅ YAML | prettier | 81 | 0 | 0 | 3.54s |
✅ YAML | v8r | 23 | 0 | 62.06s | |
✅ YAML | yamllint | 82 | 0 | 1.6s |
See detailed report in MegaLinter reports
I think we'll need to take time to properly test that release out, since we are completely changing the available packages in the alpine repos and all. Plus the Python version. |
Agreed, as the latest release is today, it gives us time to check before the next one :) |
@nvuillam I see that the php_psalm one has failed because of the API limit and that one in particular they comment that it is possible to pass an environment variable with the token to solve the problem: Would you know how to do it? Because being in the context of Docker I am not clear how to get that information and how to pass it. |
Workaround for sgerrand/alpine-pkg-glibc#185
The key is to solve the case for all linters, and to do that we must use official docker build action + manage all cases tht requires github auth ^^ |
@nvuillam I have my doubts of if this concrete case that I mention is going to solve it with what you say... This case is seen to expressly use an environment variable with a very specific name: That is why I believe that this case should be treated differently and solved now with a PR if you think it is possible or create an issue if it is not feasible because it depends on other tasks. What do you think about it? |
If you find a way to solve it in a standalone PR, of course you can ^^ |
I think you didn't understand me or you didn't look at the links I posted. The problem is in phive as I have put that is the one in charge of installing the mentioned PHP linter. That is, the problem is in the Dockerfile file when installing the linter through phive so we have to pass that environment variable to run in the GitHub workflows. That is, we have to modify the descriptor to pass that environment variable to each phive command. Example:
I have created #2314 |
🦙 MegaLinter status: ❌ ERROR
See detailed report in MegaLinter reports You could have same capabilities but better runtime performances if you request a new MegaLinter flavor. |
No description provided.