-
Notifications
You must be signed in to change notification settings - Fork 16
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
cron job error: ModuleNotFoundError: No module named 'matplotlib' #161
Comments
For some strange reason, you are missing the python requirements file in your governance repo inside .github, like this one https://github.com/gov4git/roadmap-gov.public/tree/main/.github/python This file is automatically installed by Could you be using an old (non-release) commit? Try using v2.0.1? |
Thanks for your response! Some more information: I followed the documentation here, but I tried downloading v2.0.1 from here, and using that version when I run Anyways, when I continue following the directions using that version, I get the error:
I used the same access token and same command line arguments that worked (well enough for that command to complete) using v1.1.15. The full stack trace is below. Thanks again for any help you can offer!
|
I don't have a good insight on the
The error you are getting is when Also, FYI, the system is not able to deploy on repos inside GitHub personal accounts. It only works with repos inside GitHub org accounts, because Gov4Git uses the list of maintainers of the org account as people who can issue governance directives. |
Using |
Describe the bug
I followed the tutorial to set up a governance repository, and the cron job ran and then failed, with the error message listed in the title here. Here is the output log: https://github.com/EarthSciML/GasChem.jl-gov.public/actions/runs/7604258935
To Reproduce
Just followed the tutorial
Expected behavior
I would expect the github action to run successfully.
Attach the logs
https://github.com/EarthSciML/GasChem.jl-gov.public/actions/runs/7604258935
The text was updated successfully, but these errors were encountered: