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

CI: still seeing "fatal: unsafe repository" #1161

Open
cbm755 opened this issue Jun 30, 2022 · 4 comments
Open

CI: still seeing "fatal: unsafe repository" #1161

cbm755 opened this issue Jun 30, 2022 · 4 comments
Labels

Comments

@cbm755
Copy link
Collaborator

cbm755 commented Jun 30, 2022

fatal: unsafe repository ('/home/jovyan/octsympy' is owned by someone else)
To add an exception for this directory, call:
	git config --global --add safe.directory /home/jovyan/octsympy

Maybe we need to git config as well (or instead) of sudo git config... At least I don't think that "global" thing means "all users". More like "all repos"

@alexvong243f
Copy link
Collaborator

alexvong243f commented Jul 1, 2022

The current situation is kind of awkward and complicated. Since actions/checkout#760 is now closed (it was still opened when we introduced the workarounds if I recalled correctly), one might think the issue should have been resolved.

Unfortunately, testing seems to suggest otherwise. The situation can be summarized using the following tables:

Previous results bist doctests *pythonic*
w/o workarounds failed to build with "fatal: unsafe repository" failed to build with "fatal: unsafe repository" (no such tests)
w/ workarounds build successfully w/o "fatal: unsafe repository" build successfully but show "fatal: unsafe repository" (no such tests)
Current results (before merging ci_pkg_uninst) bist, doctests bist-pythonic, doctests-pythonic
w/o workarounds build successfully but show "fatal: unsafe repository" failed to build with "fatal: unsafe repository"
w/ workarounds build successfully but show "fatal: unsafe repository" build successfully w/o "fatal: unsafe repository"
Current results (after merging ci_pkg_uninst) bist doctests pythonic-dist-doctest
w/o workarounds failed to build with "fatal: unsafe repository" build successfully but show "fatal: unsafe repository" failed to build with "fatal: unsafe repository"
w/ workarounds build successfully w/o "fatal: unsafe repository" build successfully w/o "fatal: unsafe repository" build successfully w/o "fatal: unsafe repository"

@cbm755
Copy link
Collaborator Author

cbm755 commented Jul 1, 2022

Was that before or after c6edc2a? I thought that cleaned up some of the messages.

@alexvong243f
Copy link
Collaborator

Yeah, there was before c6edc2a, I was looking at the main branch only. I'll update the tables.

@cbm755
Copy link
Collaborator Author

cbm755 commented Jul 1, 2022

Let's merge that PR first.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants