Hi! We are running a Jenkins server with a number of worker nodes both Linux and Windows and have recently got a problem on some of the Windows nodes. The following git call sequence: git clone --filter=blob:none --no-checkout <internal-gitlab-hosted-repo-url> . git sparse-checkout init --cone git sparse-checkout set <list of dirs> git checkout <sha> and then after some commits when trying to reuse the working tree: git clean -f -x -d git sparse-checkout set <same list of dirs> git fetch --filter=blob:none git checkout <sha_new> fails with: "fatal: could not fetch SHA from promisor remote". The "SHA" in the error message does not match the requested one. After googling for the error message we found https://stackoverflow.com/questions/75514869/cannot-rebase-after-fetch-fetch-says-fatal-could-not-fetch-sha-from-promisor which seemed similar. We checked and confirmed that things work just fine with git 2.38.0.windows.1 (and 2.35.1.windows.2) but not with 2.40.0.windows.1. Downgrading solved the immediate problem. Now, we could not find any other references to the issue and unable to reproduce this in an isolated environment which is worrying as we would need to update git at some point and would like to be sure that the issue is fixed by then. Question: is this issue known and tracked somewhere in git development? Appreciate any tips and comments. Best regards, Iakov
