X-Recipient: archive-cygwin AT delorie DOT com X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org D2660386FC2D Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=maxrnd.com Authentication-Results: sourceware.org; spf=none smtp.mailfrom=mark AT maxrnd DOT com Subject: Re: python > 3.5: Issue with unix domain sockets To: cygwin AT cygwin DOT com References: <1620046759893 DOT 5340 AT bmw DOT de> <2cde4128-6a3d-7431-6608-a2184d23964a AT cornell DOT edu> <418269b0-1248-008e-25a1-73bf19bbcb10 AT gmail DOT com> From: Mark Geisert Message-ID: <3d983211-c13a-22a9-ea93-84daf90f309d@maxrnd.com> Date: Tue, 4 May 2021 02:21:46 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.4 MIME-Version: 1.0 In-Reply-To: <418269b0-1248-008e-25a1-73bf19bbcb10@gmail.com> X-Spam-Status: No, score=-3.8 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, NICE_REPLY_A, SPF_HELO_NONE, SPF_NONE, TXREP autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="windows-1252"; Format="flowed" Errors-To: cygwin-bounces AT cygwin DOT com Sender: "Cygwin" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id 1449M5vx002157 Marco Atzeri via Cygwin wrote: > > On 04.05.2021 06:41, Mark Geisert wrote: >> Ken Brown via Cygwin wrote: >>> On 5/3/2021 8:57 AM, Maximilian.Blenk--- via Cygwin wrote: >>>> Incorrect Behavior: >>>> Server: >>>> $ python3.7 server.py >>>> starting up on ./uds_socket >>>> waiting for a connection >>>> Traceback (most recent call last): >>>>    File "server.py", line 27, in >>>>      connection, client_address = sock.accept() >>>>    File "/usr/lib/python3.7/socket.py", line 214, in accept >>>>      sock = socket(self.family, self.type, self.proto, fileno=fd) >>>>    File "/usr/lib/python3.7/socket.py", line 151, in __init__ >>>>      _socket.socket.__init__(self, family, type, proto, fileno) >>>> SystemError: returned >>>> NULL without setting an error >>>> >>>> Client: >>>> $ python3.7 client.py >>>> connecting to ./uds_socket >>>> sending b'This is the message.  It will be repeated.' >>>> closing socket >>>> Traceback (most recent call last): >>>>    File "client.py", line 27, in >>>>      data = sock.recv(16) >>>> ConnectionResetError: [Errno 104] Connection reset by peer >>> >>> I wonder if this has the same cause as the problem reported here: >>> >>>    https://cygwin.com/pipermail/cygwin/2021-February/247884.html >>> >>> Mark, can you check that? >> >> Hmm, the correlation between failing Python versions and patch placements is >> troubling.  I've reproduced the OP's findings and will dig further. >> >> ..mark >> > > 3.5 has not your patch for asyncio, as I am not updating it. > > all the others have it. It will be nice to solve this problem and avoid the freeze > that your patch solved. Agreed; fortunate here to have 3.5 frozen. I see the cause. I'm taking this to cygwin-developers and will respond here when we have a solution at hand. ..mark -- 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