-
-
Notifications
You must be signed in to change notification settings - Fork 301
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: Failed to build container image #137
Comments
Tracking upstream pypa/pip#9644 |
From my understanding of the incident, I have put the following together, hope it helps resolve the bug:Problem statement:This morning, I woke up to disturbing news: [AdebayoEmmanuel/AdebayoEmmanuel] Run failed: Waka Readme - main (db943f7) - My Wakatime Readme action failed! Troubleshooting done + Findings + Recommendation:
Recommendation + RCA:From the error message on the workflow logs, we understand that while declaring the requirements In --require-hashes mode, all requirements must have their versions pinned with == . Whereas, in PyGithub’s requirements.txt file, the requirements were not pinned as required. E.g, pyjwt[crypto]>=2.4.0. This whole situation resulted to errors that made Docker build to fail with exit code 1 and overall broke the scheduled job. Let’s try:
|
@joe733 |
Replacing action athul/waka-readme@master to athul/[email protected] as recommended here #136 appears to be a working workaround. My workflow ran successfully using @v0.2.1. We can explore the options I recommended above for permanent fix on the master and the latest release @v0.2.2. |
Hi @AdebayoEmmanuel, thanks for the analysis and recommendation. In any case Workarounds:
I'll be working on option 3, along container build tests. Feel free to comment your suggestions below. |
- upstream issue: pypa/pip#9644 - runs tests within a container, uses the same `dockerfile` - ignores `pdm.lock`, removes `requirement.txt` - update manual contribution steps - bumps project version **Related Items** _Issues_ - Closes athul#137
- upstream issue: pypa/pip#9644 - runs tests within a container, uses the same `dockerfile` - ignores `pdm.lock`, removes `requirement.txt` - update manual contribution steps - bumps project version **Related Items** _Issues_ - Closes athul#137
- upstream issue: pypa/pip#9644 - runs tests within a container, uses the same `dockerfile` - ignores `pdm.lock`, removes `requirement.txt` - update manual contribution steps - bumps project version **Related Items** _Issues_ - Closes athul#137
- upstream issue: pypa/pip#9644 - runs tests within a container, uses the same `dockerfile` - ignores `pdm.lock`, removes `requirement.txt` - update manual contribution steps - bumps project version **Related Items** _Issues_ - Closes athul#137
- upstream issue: pypa/pip#9644 - runs tests within a container, uses the same `dockerfile` - ignores `pdm.lock`, removes `requirement.txt` - update manual contribution steps - bumps project version **Related Items** _Issues_ - Closes athul#137
- upstream issue: pypa/pip#9644 - runs tests within a container, uses the same `dockerfile` - ignores `pdm.lock`, removes `requirement.txt` - update manual contribution steps - bumps project version **Related Items** _Issues_ - Closes athul#137
- upstream issue: pypa/pip#9644 - runs tests within a container, uses the same `dockerfile` - ignores `pdm.lock`, removes `requirement.txt` - update manual contribution steps - bumps project version **Related Items** _Issues_ - Closes athul#137
- upstream issue: pypa/pip#9644 - runs tests within a container, uses the same `dockerfile` - ignores `pdm.lock`, removes `requirement.txt` - update manual contribution steps - bumps project version **Related Items** _Issues_ - Closes athul#137
- upstream issue: pypa/pip#9644 - runs tests within a container, uses the same `dockerfile` - ignores `pdm.lock`, removes `requirement.txt` - update manual contribution steps - bumps project version **Related Items** _Issues_ - Closes athul#137
Switch back to |
@joe733
waka-time is by far my favorite accountability partner. ❤️ |
It's $ pip install --require-hashes .
Processing /home/us-er/project
ERROR: Can't verify hashes for these file:// requirements because they point to directories:
file:///home/us-er/project You can read the documentation here: https://pip.pypa.io/en/stable/topics/secure-installs/#secure-installs. |
Hi, just received an GitHub Actions workflow failed email and it is this job failed.
Failed Action: https://github.com/LiamSho/LiamSho/actions/runs/5594196665
This workflow use
athul/waka-readme@master
. Set it to useathul/[email protected]
works well.It seems like the docker container was failed to build.
I recommend to add a container build test workflow in this project.
The text was updated successfully, but these errors were encountered: