From: Mark Geisert <mark@maxrnd.com>
To: Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: Python regression related to unix sockets
Date: Sun, 6 Nov 2022 14:50:29 -0800 [thread overview]
Message-ID: <b9ccb2c9-e909-72c4-4eca-7fa992afcd4f@maxrnd.com> (raw)
In-Reply-To: <VI1P194MB03021C28AABC67D3CD441E7CEA399@VI1P194MB0302.EURP194.PROD.OUTLOOK.COM>
Hi Fabian,
Fabian Henze wrote:
> Hi all,
>
> This is a follow-up on a mail thread from February 2021.
>
> Mark Geisert via Cygwin wrote:
>> Fabian Henze via Cygwin wrote:
>>> Hi Cygwin users,
>>> I noticed a regression in the recent Python packages: Between version
>>> 3.6.10-1 and 3.6.12-2, accessing the SSH agent via the paramiko python
>>> package broke. When a ssh agent is used, paramiko tries to connect to
>>> it via the unix socket and just freezes. Python 3.8 is also affected,
>>> but I don't know which was the last working one.
>>> I was able to pinpoint that error to 3.6.12-socketmodule.patch [1].
>>> Reverting/removing the patch fixes the ssh agent access.
>>> A few weeks ago there was a discussion regarding "Problems with native
>>> Unix domain sockets on Win 10/2019", but it seems unrelated as the
>>> cygwin1.dll from [2] does not work for me.
>>>
>>> Can you please check if you are able to reproduce that? I uploaded a
>>> script [3] for that.
>>>
>>> Best regards,
>>> Fabian Henze
>>
>> Thanks for the report and sorry you've run into this. The patch is a workaround that's evidently too draconian. I will debug the situation using your testcase.
>> Thank you very much for the testcase.
>
> Did you (or anyone else) make any progress on this that you can share?
> Unfortunately the issue still persists in all current python versions.
> If no one has time to debug and fix this, would it be an option to remove the
> 3.6.12-socketmodule.patch that is causing the regression since it only fixes a
> theoretical problem in unit tests, but causes real-world issues? Maybe the
> upcoming (?) Python 3.10 or 3.11 bump would be a good candidate to do so?
Sorry for delay in responding; I've just returned from vacation.
Let me find my notes for this issue and see if I can improve on the patch or find
some other solution for now-current versions of Python and/or Cygwin DLL.
..mark
next prev parent reply other threads:[~2022-11-06 22:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-23 8:29 Fabian Henze
2021-02-23 10:29 ` Mark Geisert
2021-02-25 7:41 ` Mark Geisert
2022-11-02 11:46 ` Fabian Henze
2022-11-06 22:50 ` Mark Geisert [this message]
2022-11-08 6:51 ` Mark Geisert
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=b9ccb2c9-e909-72c4-4eca-7fa992afcd4f@maxrnd.com \
--to=mark@maxrnd.com \
--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).