-
-
Notifications
You must be signed in to change notification settings - Fork 894
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
Bad git executable #1882
Comments
Thanks for sharing - I agree. The code for this is here, in case anyone wants to give it a shot: Lines 463 to 476 in 64ec0b1
|
This relates to the inconsistency discussed in #1815 (comment) and could be partially fixed by making initial refresh exception and logging messages include the path, as subsequent refresh messages have done since #1812. (I say "partially" because that would still not directly tell the user how that specific git executable path was set or discovered.) |
This is the full message:
This error message could be much more helpful.
Which git executable is it trying to run?
Why? Where did it find that path? Is it using the PATH? Is it using GIT_PYTHON_GIT_EXECUTABLE?
The text was updated successfully, but these errors were encountered: