-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Sparse checkout seems to be triggered when not intended #1378
Comments
3.5.3 sparse checkout support seems to break in our CI. See actions/checkout#1378
3.5.3 sparse checkout support seems to break in our CI. See actions/checkout#1378
I will take a look to see what is the issue here! |
Hey @bzbarsky-apple after taking a look to this issue and making some test I figure out that it likely to be an error in relation with I made some debug on ![]() I'm trying to figure out why this is happening but from the moment that is everything that I can do for you! I will inform you with any news if any. |
The problem might be that if ![]() I'm just speculating here because I don't know how Also here is an Regarding this issue I have run testing with edge cases like setting up |
Where would that If you are able to reproduce this in a setting where you can modify the checkout code that's running, I would be very interested to know whether INPUT_SPARSE_CHECKOUT is in fact set in |
Hey @bzbarsky-apple I have been taking a deeper look to this and now I can confirm that the issue is from If you go to the
When reading the yaml the That is why |
Interesting. So this is from |
Yes, but there is nothing we can do here, the issue is from I have added an issue to see if they can fix it! Wandalen/wretry.action#85 |
I actually have the opposite problem but same error with github actions when I use ACT to run actions locally for testing. I get the |
I was actually using git 2.37.1 |
I have run some test using the git version Is it possible to have the logs ? Or at least the configuration that you are using on Also I've been taking a look to the git repo and that error make sense to have it if you have a git version < I wasn't able to find any other place on the code that referes that error after |
3.5.3 sparse checkout support seems to break in our CI. See actions/checkout#1378 Cherry-Picked from: 7f6723f
3.5.3 sparse checkout support seems to break in our CI. See actions/checkout#1378 Cherry-Picked from: 7f6723f
3.5.3 sparse checkout support seems to break in our CI. See actions/checkout#1378 Cherry-Picked from: 7f6723f
3.5.3 sparse checkout support seems to break in our CI. See actions/checkout#1378 Cherry-Picked from: 7f6723f
3.5.3 sparse checkout support seems to break in our CI. See actions/checkout#1378 Cherry-Picked from: 7f6723f
@bzbarsky-apple this can be closed! Wandalen/wretry.action#85 (comment) |
Perfect, thanks! |
3.5.3 sparse checkout support seems to break in our CI. See actions/checkout#1378 Cherry-Picked from: 7f6723f
3.5.3 sparse checkout support seems to break in our CI. See actions/checkout#1378 Cherry-Picked from: 7f6723f
3.5.3 sparse checkout support seems to break in our CI. See actions/checkout#1378 Cherry-Picked from: 7f6723f
3.5.3 sparse checkout support seems to break in our CI. See actions/checkout#1378 Cherry-Picked from: 7f6723f
We have some GitHub CI that uses the checkout action like so:
As of this morning all checkouts stopped working with this error:
You can compare a failing run at https://github.com/project-chip/connectedhomeip/actions/runs/5223466703/jobs/9430364364 with a passing run from a few hours earlier at https://github.com/project-chip/connectedhomeip/actions/runs/5222975743/jobs/9429182655.
The failing run is running this git command:
while the passing one ran this one:
note the extra
--filter=blob:none
that is present in the failing command. This is presumably a change from #1369. I do see that that bit is conditoned onsettings.sparseCheckout
in that PR, but we are not settingsparseCheckout
to anything anywhere in our repository...The text was updated successfully, but these errors were encountered: