-
-
Notifications
You must be signed in to change notification settings - Fork 340
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
Update actions/checkout action to v3 #9527
Conversation
Nope, still happens. Delightful. Ahh, the |
|
But the git version and global config can be different inside the docker image, right? |
We can try adding |
I think that version is from 2018, so it probably doesn't have the safe directory feature. ... but I don't have a repo created by |
Finally got the error to happen locally in my own NetKAN repo! The GitHub workflow prints the entire docker command that it runs, which is very helpful:
|
!!!!! So I guess the safe directory feature is a little older than mid-2022; at least back to 2018! |
Your branch is really old. Try rebasing on current master. |
Validation succeeded after the changes in KSP-CKAN/xKAN-meta_testing#90. 🎉 |
Problem
The metadata tester is broken. It now emits this every time it runs:
Causes (speculative)
git
added a "safe directories" feature in mid-2022, which causes it to print an error without even parsing the repo config if the current user doesn't own a repo, to prevent other users from forcing the current user to run code. Adding KSP 1.12.5 to the embedded build map probably updated the docker image to use a newer version ofgit
including these changes.I have not personally loaded up the current docker image and simulated running it in order to probe the details of exactly what's happening in the filesystem. But I find this a plausible explanation for the problem, and if it doesn't work out, we can continue investigating and try something else.
Changes
Now we upgrade from v2 to v3 of actions/checkout, which ignores "safe directories" by default (see actions/checkout#762 and actions/checkout#770), and should mitigate this if that's the cause.
See KSP-CKAN/xKAN-meta_testing#89, which this doesn't seem to actually fix.