Skip to content
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

fatal: Not a git repository: '/homes/vvikraman/anaconda3/lib/python3.6/site-packages/.git #326

Closed
vvinuv opened this Issue Jun 8, 2018 · 2 comments

Comments

Projects
None yet
3 participants
@vvinuv
Copy link

vvinuv commented Jun 8, 2018

Hi
When I try to run parsl I am getting the following issue:

fatal: Not a git repository: '/homes/vvikraman/anaconda3/lib/python3.6/site-packages/.git

Is it a real issue?

I am using python3 and jupyter but run parsl in a terminal.

@yadudoc

This comment has been minimized.

Copy link
Member

yadudoc commented Jun 8, 2018

Parsl tries to check and report the git version in case the user is trying to use parsl from source. This is non-fatal and should not affect workflow execution in any way.
We'll have this cleaned up in the next release.

@yadudoc yadudoc added this to the Parsl-0.6.0 milestone Jun 8, 2018

@annawoodard

This comment has been minimized.

Copy link
Collaborator

annawoodard commented Jun 8, 2018

Thanks for the report, @vvinuv! As @yadudoc says, the issue here is that the error message is confusing-- the error itself does not affect workflow execution. It just means that we cannot determine if you've modified the parsl code. In the next release we will not print the traceback, since it is misleading.

annawoodard added a commit that referenced this issue Jun 8, 2018

Do not log traceback if version check fails
This is confusing. If the version is the vanilla version instead of in
the format '{v}-{head}-{status}', we can assume that the check failed.
There is no need to show the user the traceback, as that makes it appear
like there was a fatal error. Fixes #326 and fixes #327.

annawoodard added a commit that referenced this issue Jun 8, 2018

Do not log traceback if version check fails
This is confusing. If the version is the vanilla version instead of in
the format '{v}-{head}-{status}', we can assume that the check failed.
There is no need to show the user the traceback, as that makes it appear
like there was a fatal error. Fixes #326 and fixes #327.

ConnorPigg added a commit that referenced this issue Jun 26, 2018

Do not log traceback if version check fails
This is confusing. If the version is the vanilla version instead of in
the format '{v}-{head}-{status}', we can assume that the check failed.
There is no need to show the user the traceback, as that makes it appear
like there was a fatal error. Fixes #326 and fixes #327.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.