X-Recipient:	archive-cygwin AT delorie DOT com
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org 09CA13858035
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1636141338;
	bh=Lej0h8h2OH8f7GDy79tgKQozVQoZXczEsZJQWseu7/c=;
	h=Date:To:Subject:In-Reply-To:References:List-Id:List-Unsubscribe:
	List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:
	From;
	b=qlrU1m+4+5cRMD6bVM6GX7VPRDbX1abLp8xtGrYfr4mJqnbxCFsL/Wc4/EZBL6yrX
	Lieezd/M1m1StLoJc1Q2+bneLWmOQehYyuKFYFfK5BhiHmNMVc9hWWIh7kkj39F0dn
	YYlnzg2qk+T/CJhkpy8xQLhbBcoSc7rxsXkmvgeI=
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.4.1 sourceware.org 0CAF83858D28
DKIM-Filter:	OpenDKIM Filter v2.10.3 conssluserg-03.nifty.com 1A5Jf9Wg028408
X-Nifty-SrcIP:	[110.4.221.123]
Date:	Sat, 6 Nov 2021 04:41:16 +0900
To:	cygwin AT cygwin DOT com
Subject:	Re: 3.3.0: Possible regression in cygwin DLL (Win10); fixed in
	snapshot
Message-Id:	<20211106044116.698b465a5d8ed6ce2cc75c99@nifty.ne.jp>
In-Reply-To:	<CAEv6GODiM88Xfhk9R3AcEW6UTYSzACzYe4C0gPoTYm=u9ZTqRQ@mail.gmail.com>
References:	<CAEv6GOB8PXHgHoz7hdJy6Bia2GWEmUDnTd252gTGinz2vuv=hA AT mail DOT gmail DOT com>
	<20211105123950 DOT b118a7f2ba38379764df4c12 AT nifty DOT ne DOT jp>
	<CAEv6GOA-y58YrftXgEgFrjqtOTHmfdu2Vrq76Lwn0suZpZ=U9w AT mail DOT gmail DOT com>
	<20211105170542 DOT 96ce6dd4ca32880ddfddd660 AT nifty DOT ne DOT jp>
	<CAEv6GODiM88Xfhk9R3AcEW6UTYSzACzYe4C0gPoTYm=u9ZTqRQ AT mail DOT gmail DOT com>
X-Mailer:	Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32)
Mime-Version:	1.0
X-Spam-Status:	No, score=-5.3 required=5.0 tests=BAYES_00, DKIM_SIGNED,
	DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, NICE_REPLY_A, RCVD_IN_DNSWL_NONE,
	RCVD_IN_MSPIKE_H2, SPF_HELO_NONE, SPF_PASS,
	TXREP autolearn=ham autolearn_force=no version=3.4.4
X-Spam-Checker-Version:	SpamAssassin 3.4.4 (2020-01-24) on
	server2.sourceware.org
X-BeenThere:	cygwin AT cygwin DOT com
X-Mailman-Version:	2.1.29
List-Id:	General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe:	<https://cygwin.com/mailman/options/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive:	<https://cygwin.com/pipermail/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe:	<https://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From:	Takashi Yano via Cygwin <cygwin AT cygwin DOT com>
Reply-To:	Takashi Yano <takashi DOT yano AT nifty DOT ne DOT jp>
Errors-To:	cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com
Sender:	"Cygwin" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT 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 DOT yano AT nifty DOT ne DOT jp>

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

- Raw text -