From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm1-x32d.google.com (mail-wm1-x32d.google.com [IPv6:2a00:1450:4864:20::32d]) by sourceware.org (Postfix) with ESMTPS id 3C52A394D8BE for ; Tue, 4 May 2021 05:42:43 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 3C52A394D8BE Received: by mail-wm1-x32d.google.com with SMTP id o26-20020a1c4d1a0000b0290146e1feccdaso514312wmh.0 for ; Mon, 03 May 2021 22:42:43 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=c7VU/ztOhmPQeqqqZQ5wyDgTp9ubsJ0PsK4b5UiaAUU=; b=UCIkge6CEL242oprUQDmGHPqiRs8I7tAVQtmaWl1EEE7JOw0TS303dWfhHBY4c+zzT rj1ov34lAZ+AEjysQMcw7/qYpxbF4BEtxJ4NWOg6Knrla9fM5HwTu6Cu6QapnyLJW11E N5rvw0KpaUpgyETWqnE1YmfOAhyitWLnEe0cMEoFO4LyiWKadhSgaWA/sB9vRf1f+ya1 8+01XV1ZJmGZp2RP6bZyLQp6BeSlmHXtaxgUWe0sJjx87f4QuAw/kD0p1KqA5LF6w6On 8hELe5696t7TV1WALDUp+RABKDSEnSjAwVARLkAIShY1I62DuPKRuctVYn6TRuwb4CQo srOA== X-Gm-Message-State: AOAM530Gj4TZUg0aSvbXEmGSEshUey+fJbjw8S9uQxZYmLaQhZ74IGJv qbYRjR6OSIX+pmOeYhFsW1S3NVThu03q6g== X-Google-Smtp-Source: ABdhPJyEPLWBbNn3VFoMSFrCY9BdgBfNdZq5m5bX+RohJOfHUCRrjIfP4xuszjXX58jU+Ld+JA2abQ== X-Received: by 2002:a1c:988f:: with SMTP id a137mr18648243wme.81.1620106962352; Mon, 03 May 2021 22:42:42 -0700 (PDT) Received: from ?IPv6:2003:cc:9f04:e3c3:ad45:1bfc:da20:3be6? (p200300cc9f04e3c3ad451bfcda203be6.dip0.t-ipconnect.de. [2003:cc:9f04:e3c3:ad45:1bfc:da20:3be6]) by smtp.gmail.com with ESMTPSA id x64sm1449626wmg.46.2021.05.03.22.42.41 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 03 May 2021 22:42:41 -0700 (PDT) Subject: Re: python > 3.5: Issue with unix domain sockets To: cygwin@cygwin.com References: <1620046759893.5340@bmw.de> <2cde4128-6a3d-7431-6608-a2184d23964a@cornell.edu> From: Marco Atzeri Message-ID: <418269b0-1248-008e-25a1-73bf19bbcb10@gmail.com> Date: Tue, 4 May 2021 07:42:40 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: it Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-1.6 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, NICE_REPLY_A, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham 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@cygwin.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: , X-List-Received-Date: Tue, 04 May 2021 05:42:44 -0000 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.