From: "Simão Afonso" <simao.afonso@powertools-tech.com>
To: git@vger.kernel.org
Subject: Credential Store: Don't acquire lock when only reading the file
Date: Thu, 29 Oct 2020 19:20:20 +0000 [thread overview]
Message-ID: <20201029192020.mcri76ylbdure2o7@safonso-t430> (raw)
When git is configured for parallel fetches `fetch.parallel = 0` and
uses the `store` credential helper, fetching all remotes might lead to a
spurious lock fail. It's a race condition when several remotes require
the credentials at the same time.
This shouldn't happen, using the `get` operation should not lock the
file.
next reply other threads:[~2020-10-29 19:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 19:20 Simão Afonso [this message]
2020-10-30 5:55 ` Credential Store: Don't acquire lock when only reading the file Jeff King
2020-10-30 11:22 ` Simão Afonso
2020-10-30 11:25 ` Jeff King
2020-10-30 11:39 ` Simão Afonso
2020-10-30 12:05 ` Simão Afonso
2020-10-30 15:01 ` Jeff King
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=20201029192020.mcri76ylbdure2o7@safonso-t430 \
--to=simao.afonso@powertools-tech.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.