public inbox for git@vger.kernel.org
 help / color / mirror / Atom feed
From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Ivan Ivanov <qmastery16@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Test "t0300-credentials" is failing on Arch/Artix: asks to enter the Username/Password in an infinite loop
Date: Fri, 6 Mar 2026 01:23:38 +0000	[thread overview]
Message-ID: <aaosmo1Iluc5KeZw@fruit.crustytoothpaste.net> (raw)
In-Reply-To: <CAAaskFANnrqTAjQOHhAgzES9=S+y7w9u-LMWbRbi8FayVdvzFw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2044 bytes --]

On 2026-03-06 at 01:05:58, Ivan Ivanov wrote:
> To clarify, in addition to t0300-credentials.out ,
> t0301-credential-cache.out and t0302-credential-store.out are also
> failing, however a similar-by-nature t0303-credential-external.out
> succeeds fine. Very strange. Seeing how it's leaking to the primary
> console, I suspect something may be wrong with shell handling: i.e.
> for t0302-credential-store test I am seeing these prompts that are
> waiting input for a user (could write any message here or just press
> Enter to get a new prompt) :
> 
> Username for 'https://example.com':
> Password for 'https://%20@example.com':
> Username for 'http://example.com':
> Password for 'http://example.com':
> Username for 'https://other.tld':
> Password for 'https://other.tld':
> Password for 'https://other@example.com':
> Username for 'http://path.tld/bar.git':
> Password for 'http://path.tld/bar.git':
> Password for 'https://user-overwrite@example.com':
> Username for 'https://example.com':
> Password for 'https://example.com':
> Password for 'https://user1@example.com':
> Username for 'https://example.com':

To help us understand more, can you provide the output of `git version
--build-options` on the affected version, as well as the shell you're
using (bash, dash, etc. and version) and any configuration options
you're using to build?

Using Debian unstable with Debian's dash 0.5.12-12 as `/bin/sh`, I don't
see this problem when running with the following command in zsh:

    time make -j12 all && (cd t && ulimit -c unlimited && GIT_PROVE_OPTS=-j12 GIT_TEST_DEFAULT_HASH=sha256 ./t0300*.sh --verbose --debug)

Note that Git should not prompt on the command line because of the
following code in `t/lib-credential.sh`:

    write_script askpass <<\EOF
    echo >&2 askpass: $*
    what=$(echo $1 | cut -d" " -f1 | tr A-Z a-z | tr -cd a-z)
    echo "askpass-$what"
    EOF
    GIT_ASKPASS="$PWD/askpass"
    export GIT_ASKPASS
-- 
brian m. carlson (they/them)
Toronto, Ontario, CA

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

  reply	other threads:[~2026-03-06  1:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-06  0:42 Test "t0300-credentials" is failing on Arch/Artix: asks to enter the Username/Password in an infinite loop Ivan Ivanov
2026-03-06  1:05 ` Ivan Ivanov
2026-03-06  1:23   ` brian m. carlson [this message]
2026-03-06  1:44     ` Ivan Ivanov
2026-03-06  1:59       ` brian m. carlson
2026-03-06  2:14         ` Ivan Ivanov
2026-03-06  2:19           ` Ivan Ivanov
2026-03-06  4:38           ` Jeff King
2026-03-06 14:14             ` Ivan Ivanov
2026-03-06 16:01               ` Jeff King
2026-03-06 17:36                 ` Ivan Ivanov
2026-03-06 21:17                   ` brian m. carlson

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=aaosmo1Iluc5KeZw@fruit.crustytoothpaste.net \
    --to=sandals@crustytoothpaste.net \
    --cc=git@vger.kernel.org \
    --cc=qmastery16@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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox