From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Matt Armstrong Newsgroups: gmane.emacs.devel Subject: Re: master 2c79a8f 2/2: Use posix_spawn if possible. Date: Fri, 28 Jan 2022 09:12:22 -0800 Message-ID: <87v8y33hu1.fsf@rfc20.org> References: <7CFD5E28-8266-4004-BF66-255146D72722@gnu.org> <83r18whunp.fsf@gnu.org> <36bbd45c-0a87-13b7-1589-afe943329e20@fastmail.com> <83ee4whqpf.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="13563"; mail-complaints-to="usenet@ciao.gmane.io" Cc: p.stephani2@gmail.com, alan@idiocy.org, mituharu@math.s.chiba-u.ac.jp, emacs-devel@gnu.org To: Eli Zaretskii , Saulius Menkevicius Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Jan 28 18:29:18 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nDV3k-0003K4-UV for ged-emacs-devel@m.gmane-mx.org; Fri, 28 Jan 2022 18:29:17 +0100 Original-Received: from localhost ([::1]:42574 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nDV3k-0004vY-0m for ged-emacs-devel@m.gmane-mx.org; Fri, 28 Jan 2022 12:29:16 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:55440) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nDUnd-0000Pr-BY for emacs-devel@gnu.org; Fri, 28 Jan 2022 12:12:37 -0500 Original-Received: from relay5-d.mail.gandi.net ([217.70.183.197]:48181) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nDUnX-00053L-Of; Fri, 28 Jan 2022 12:12:36 -0500 Original-Received: (Authenticated sender: matt@rfc20.org) by mail.gandi.net (Postfix) with ESMTPSA id C5E881C0005; Fri, 28 Jan 2022 17:12:24 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rfc20.org; s=gm1; t=1643389947; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=xxhGvnevti73TegqtaPWrBpvuh2gOt46W6W2M0wUTeo=; b=CiqYJJWPehwLS5b/021bX9xeHYzKKMwJInkmPZNPDVsc8ZGyAnS0PJtkfBlGR++g69vwpG pdhAR+hbAVXZSP8tmmPql1d2BdY1ppsZZywUcKUVOjQqM5a8oqdyN4nbuW7SdXaWzkpugJ wCVblNye0oEuOdPFxl4+LDbFCuLqL7U2nBSHS0upNoHou+8zdvmn1oRngXyWpiU85XCk4/ RcKiD99kJk54tHXsMpGMOtVWT83EQFMxYDtRPiL/Ke1FQFif5H16Dpw3Jjgi3vXvhxItiG 2vlpPv2HtP8byhB82y/D00v5AyGa+mXAKn6aIw6V15AiHVN9VEvjb/aZeOlJbA== Original-Received: from matt by naz with local (Exim 4.95) (envelope-from ) id 1nDUnO-002BOj-5f; Fri, 28 Jan 2022 09:12:22 -0800 In-Reply-To: <83ee4whqpf.fsf@gnu.org> Received-SPF: pass client-ip=217.70.183.197; envelope-from=matt@rfc20.org; helo=relay5-d.mail.gandi.net X-Spam_score_int: -8 X-Spam_score: -0.9 X-Spam_bar: / X-Spam_report: (-0.9 / 5.0 requ) DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=unavailable autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:285518 Archived-At: Eli Zaretskii writes: >> Date: Tue, 25 Jan 2022 14:25:23 +0200 >> From: Saulius Menkevicius >> Cc: p.stephani2@gmail.com, alan@idiocy.org, mituharu@math.s.chiba-u.ac.jp, >> emacs-devel@gnu.org >> >> I certainly cannot answer that, it probably does some kind of sniffing >> on FDs and changes behaviour. >> >> To actually figure that out I would need to build a minimal test fixture >> for this bug/issue and submit to dotnet/runtime repo on github for them >> to check and/or fix it. > > I think there's no way around this. We need at least to understand > what part of posix_spawn code interferes with pipe-based I/O used by > these LSP servers, and why. I don't find an emacs bug filed for this issue. Saulius, it would be good to file one. This issue tickled a memory I had of Python moving away from posix_spawn due to various portability issues: https://bugs.python.org/issue35823. The issues they ran into and solved may inform this investigation.