From: Jeff King <email@example.com>
To: Junio C Hamano <firstname.lastname@example.org>
Cc: "Simão Afonso" <email@example.com>, firstname.lastname@example.org
Subject: Re: [PATCH v2] crendential-store: use timeout when locking file
Date: Wed, 25 Nov 2020 04:37:07 -0500 [thread overview]
Message-ID: <X74lw+fyurzqVbg1@coredump.intra.peff.net> (raw)
On Tue, Nov 24, 2020 at 02:08:01PM -0800, Junio C Hamano wrote:
> Simão Afonso <email@example.com> writes:
> > +credentialStore.fileTimeout::
> > + The length of time, in milliseconds, for git-credential-store to retry
> > + when trying to lock the credentials file. Value 0 means not to retry at
> > + all; -1 means to try indefinitely. Default is 1000 (i.e., retry for
> > + 1s).
> I do not remember what was said in the first round of the review,
> but I wonder if this is the best name for users. I think it is good
> enough, but do ".lockTimeout" or ".lockTimeoutMS" make it even
> easier to grok, perhaps?
Yeah, I think those are a bit more obvious.
> > +
> > + if (hold_lock_file_for_update_timeout(&credential_lock, fn, 0, timeout_ms) < 0)
> > + die_errno("unable to get credential storage lock in %d ms", timeout_ms);
> Should this be die_errno()? Looking at lock_file_timeout(), I am
> not sure if the value of errno is valid in all codepaths that return
I think it's the right thing here. Inside hold_lock_file_for_update_timeout(),
we'd pass errno to unable_to_lock_die(), etc. So if there is a code path
in lock_file_timeout() that isn't setting errno properly, we should
probably be fixing that.
Another option would be to just pass LOCK_DIE_ON_ERROR here, but I think
for this use I prefer the smaller "unable to lock" to the big "another
git process may have crashed" advice message we'd give in that case.
next prev parent reply other threads:[~2020-11-25 9:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-30 18:07 [PATCH] credential-store: " Simão Afonso
2020-10-30 19:49 ` Junio C Hamano
2020-11-24 19:32 ` [PATCH v2] crendential-store: " Simão Afonso
2020-11-24 22:08 ` Junio C Hamano
2020-11-25 9:37 ` Jeff King [this message]
2020-11-25 18:31 ` [PATCH v3] " Simão Afonso
2020-11-26 7:37 ` Jeff King
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:
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.
Code repositories for project(s) associated with this inbox:
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).