From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Subject: Re: 3.3.0: Possible regression in cygwin DLL (Win10); fixed in snapshot
Date: Sat, 6 Nov 2021 04:41:16 +0900 [thread overview]
Message-ID: <20211106044116.698b465a5d8ed6ce2cc75c99@nifty.ne.jp> (raw)
In-Reply-To: <CAEv6GODiM88Xfhk9R3AcEW6UTYSzACzYe4C0gPoTYm=u9ZTqRQ@mail.gmail.com>
On Fri, 5 Nov 2021 08:42:03 -0500
Brian wrote:
> Starting point: Cygwin 3.3.0s(0.341/5/3), Windows Version 10.0.17763 Build
> 17763, no git managers/clients initially installed.
>
> 1. Install git version 2.33.0 via the Cygwin installer (only the CLI).
> 2. Download the GCM-Core 2.0.567 release zip file (
> https://github.com/microsoft/Git-Credential-Manager-Core/releases/) and
> extract somewhere.
> 3. Copy all *.exe and *.dll files to your Cygwin /usr/libexec/git-core/
> directory.
> 4. Set up the credential helper: 'git config --global credential.helper
> manager-core'
> 5. Clone a repo.
> 6. Attempt a 'git push' using the git repo's https URL. GCM will pop up a
> browser-based UI for initial authentication. After entering username and
> PAT credentials, and receiving the 'Everything is up-to-date' message,
> confirm that your git credentials appear in the Windows Credential Manager.
> 7. Attempt another 'git push'.
> EXPECTED BEHAVIOR:
> 'Everything is up-to-date' (there should be no CLI or UI authentication
> prompts).
> OBSERVED BEHAVIOR:
> The user is again presented with an authentication prompts from git.
> 8. Replace cygwin1.dll with the 0913 snapshot.
> 9. Attempt a 'git push'. If your credentials were cached in WCM per step
> 6, you should immediately see the 'Everything is up-to-date' reply. If
> your credentials weren't stored for some reason, you will be prompted for
> authentication. A subsequent 'git push' should then use your cached
> credentials.
Thanks much for the detailed steps. I could reproduce the problem.
It seems that the cause is the overhaul for the pipe implementation.
I also found the workaround for this issue. Please try:
export CYGWIN=pipe_byte
Corinna, Ken,
What about setting pipe mode to byte by default?
--
Takashi Yano <takashi.yano@nifty.ne.jp>
next prev parent reply other threads:[~2021-11-05 19:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-04 15:02 Brian
2021-11-05 3:39 ` Takashi Yano
[not found] ` <CAEv6GOA-y58YrftXgEgFrjqtOTHmfdu2Vrq76Lwn0suZpZ=U9w@mail.gmail.com>
2021-11-05 8:05 ` Takashi Yano
2021-11-05 13:42 ` Brian
2021-11-05 19:41 ` Takashi Yano [this message]
2021-11-05 20:08 ` Ken Brown
2021-11-06 16:22 ` Ken Brown
2021-11-05 21:32 ` Brian
2021-11-06 6:24 ` ASSI
2021-11-08 16:30 ` Andrey Repin
2021-11-08 20:49 ` Adam Dinwoodie
2021-11-08 23:18 ` Brian Koontz
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=20211106044116.698b465a5d8ed6ce2cc75c99@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--cc=cygwin@cygwin.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).