From: Jeff King <peff@peff.net>
To: Steven Penny <srpen6@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: credential-store get: No such file or directory
Date: Wed, 3 Nov 2021 07:10:35 -0400 [thread overview]
Message-ID: <YYJuK70U8Sk7xSYl@coredump.intra.peff.net> (raw)
In-Reply-To: <CAP8dQmvoxWDnD_rbCdBS9cnwS90YFjjXcCPWLmjMq=ck7vo1Ww@mail.gmail.com>
On Tue, Nov 02, 2021 at 10:57:09PM -0500, Steven Penny wrote:
> > Also, what does:
> >
> > GIT_TRACE=1 git push
> >
> > say about what it's trying to execute?
>
> Aha:
>
> 22:53:19.785297 run-command.c:666 trace: run_command:
> git-remote-https origin https://github.com/89z/googleplay
> 22:53:20.024042 run-command.c:666 trace: run_command: 'git
> credential-store get'
Hmm, that's the right output, I think. Even though it's wrapped in
single-quotes I think that's just how run_command shows it. If I do
something silly like:
[credential]
helper = "!'git credential-store'"
then I get:
07:07:49.063476 run-command.c:663 trace: run_command: ''\''git credential-store'\'' get'
'git credential-store' get: 1: git credential-store: not found
> > I think it is not complaining about finding the credential file, but
> > running the credential-store helper in the first place. The "cannot run"
> > message comes from our run-command.c code.
>
> Yeah, looks like you are right, based on the trace result.
So I'm quite confused about exactly what's failing and why. At this
point I'd probably try running it under strace to see what's actually
happening at the syscall level. I don't think you said what OS you're
on; if it's Linux, then I suspect something like:
strace -f -e execve git push
might be interesting (dropping the "-e execve" will give much more
output which might also be interesting, but it's probably pretty big).
-Peff
next prev parent reply other threads:[~2021-11-03 11:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-03 0:27 credential-store get: No such file or directory Steven Penny
2021-11-03 1:19 ` Steven Penny
2021-11-03 2:25 ` Jeff King
2021-11-03 3:57 ` Steven Penny
2021-11-03 11:10 ` Jeff King [this message]
2021-11-03 16:01 ` Steven Penny
2021-11-04 9:43 ` Jeff King
2021-11-04 14:12 ` Steven Penny
2021-11-04 14:55 ` 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
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 \
--in-reply-to=YYJuK70U8Sk7xSYl@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=srpen6@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).