-
-
Notifications
You must be signed in to change notification settings - Fork 140
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
ENH: Print more informative error message instead of Cmd('git') failed due to: exit code(128)
#229
Comments
Cmd('git') failed due to: exit code(128)
Hi @corneliusroemer! Thanks for your words 😄 Not sure Gitpython provides anything more than |
Thanks, so this is an upstream issue then? Just thought I start here 😅 |
@corneliusroemer Hello, did you find any way to handle this issue till now? We met the same issue and the full traceback is almost the same. If you have any good idea, we can exchange and discuss. Thank you! |
@ishepard I met the same issue and the full traceback is almost the same. I did not find a good way to handle it, did you have any other good idea to get more informative error message in this case to help handle this issue? |
Is your feature request related to a problem? Please describe.
I love pydriller. Using it to step through all versions of a file in a large repo: https://github.com/corneliusroemer/pango-designation-dates
Things worked fine locally, but when I went to setup a Github action I got a cryptic error with a not so helpful error message:
When I ran that command
git diff-tree ...
locally, everything was fine.I needed to ssh into the Github action using tmate to run it locally, and that helped, I got an error that said
bad commit
- because I had shallow-cloned the repo using the default settings ofactions/checkout@v3
.I was wondering why the traceback pydriller provides doesn't state that more helpful error message. Would it be possible to include that somehow?
Describe the solution you'd like
Provide more useful and informative error information other than
Cmd('git') failed due to: exit code(128)
.Additional context
Here's the full traceback:
Thanks for your work developing this great tool!
The text was updated successfully, but these errors were encountered: