unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Henrik Ahlgren <pablo@seestieto.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 43226@debbugs.gnu.org, Michael Albinus <michael.albinus@gmx.de>
Subject: bug#43226: 28.0.50; Running Tramp tests on MS-Windows leaves zombie processes on the remote
Date: Wed, 26 Oct 2022 14:34:09 +0300	[thread overview]
Message-ID: <87wn8mhl8u.fsf@seestieto.com> (raw)
In-Reply-To: <83lep3ogpt.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 25 Oct 2022 22:17:50 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

> Maybe Michael (CC'ed) can explain how this is supposed to work,
> because I don't think I understand.  The actual process run by Emacs
> is ssh, not cat, so how is EOF supposed to get to the remote "cat"?

Not exactly sure, but clearly there is some difference between POSIX
platforms and Windows on how process-send-eof works in certain
situations when dealing with Tramp remote connections, and this breaks
some functionality of Magit, not just Tramp's own tests. 

In my test I just used cat to emulate "git apply -" to trace what it
receives from the standard input.

This issue is documented on the FAQ section of the Magit manual:

  A.2.13 I am unable to stage when using Tramp from MS Windows
  ------------------------------------------------------------

  Magit may be unable to stage (or otherwise apply) individual hunks when
  you are connected to remote machine using Tramp and the local machine
  uses MS Windows.

     There appears to be a problem with ‘process-send-eof’ in this
  scenario, as mentioned at the end of ‘tramp-tests.el’.  I have contacted
  the Tramp maintainer about this.  For now this unfortunately means that
  it just doesn’t work and we cannot do anything about it.  If you have
  more information, then please comment on
  <https://github.com/magit/magit/issues/3624>.

After some debugging I figured out that by simply adding
(process-send-string process "\004") in magic-process.el before (maybe
even instead?) of process-send-eof, it works perfectly well. Maybe it's
a valid workaround, or even the proper fix, but clearly there is some
point of having a separate function for sending EOF.

In the C implementation of process-send-eof (Emacs 27.1), it seems to only
send EOF if the process has pty_flag set:

  if (XPROCESS (proc)->pty_flag)
    send_process (proc, "\004", 1, Qnil);

I think this could be the reason: after all I believe PTYs are a fairly
recent feature in Windows and Emacs does not support it yet? OTOH, this
function seems to work when running ssh directly from start-file-process
which apparently doesn't use cmdproxy.exe. Anyway, I have no means of
compiling Emacs on Windows to debug the C source to see if pty_flag is
set on the non-cmdproxy.exe case.







  reply	other threads:[~2022-10-26 11:34 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-05 16:38 bug#43226: 28.0.50; Running Tramp tests on MS-Windows leaves zombie processes on the remote Eli Zaretskii
2020-09-05 19:04 ` bug#43226: Fwd: bug#26911: 25.2; eshell "cd .." doesn't work correctly with TRAMP Michael Albinus
2020-09-05 19:04 ` Michael Albinus
2020-09-05 19:16   ` bug#43226: 28.0.50; Running Tramp tests on MS-Windows leaves zombie processes on the remote Michael Albinus
2020-09-05 19:25     ` Eli Zaretskii
2020-09-06  8:49       ` Michael Albinus
2020-09-06 15:14         ` Eli Zaretskii
2020-09-06 15:54           ` Michael Albinus
2020-09-06 16:07             ` Eli Zaretskii
2022-10-25  9:39               ` Henrik Ahlgren
2022-10-25 11:26                 ` Eli Zaretskii
2022-10-25 13:56                   ` Henrik Ahlgren
2022-10-25 16:49                     ` Michael Albinus
2022-10-25 19:17                     ` Eli Zaretskii
2022-10-26 11:34                       ` Henrik Ahlgren [this message]
2022-10-26 12:01                         ` Eli Zaretskii
2022-10-26 14:15                           ` HA
2022-10-29 14:48                             ` Michael Albinus

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wn8mhl8u.fsf@seestieto.com \
    --to=pablo@seestieto.com \
    --cc=43226@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=michael.albinus@gmx.de \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).