From: Iakov Nakhimovski <iakov.nakhimovski@gmail.com>
To: git@vger.kernel.org
Subject: fatal: could not fetch SHA from promisor remote with git 2.40
Date: Mon, 22 May 2023 17:44:11 +0200 [thread overview]
Message-ID: <CAM9q8UoE5OGLkZ7MduXqWjxyGV7xNFBXsEbaYG1H61zZ9AO_XA@mail.gmail.com> (raw)
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
reply other threads:[~2023-05-22 15:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAM9q8UoE5OGLkZ7MduXqWjxyGV7xNFBXsEbaYG1H61zZ9AO_XA@mail.gmail.com \
--to=iakov.nakhimovski@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).