unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: emacsq via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 53814@debbugs.gnu.org
Subject: bug#53814: process-status returns invalid/undocumented status file-error for network process
Date: Sun, 06 Feb 2022 12:32:22 +0000	[thread overview]
Message-ID: <fRYY5cXxkYnCAumdGdTVwiQJMTOI3qMnSnR6XWfdAFvIO9pZkYoQ7csC2rK7vrQHJHv1iioKYbHOYB8c11KMaKU23gn3ijUPzhI0nssGpYQ=@protonmail.com> (raw)
In-Reply-To: <X-LUwG3U455dtxhekJsHlH9T0xw80_I9uidPhoI3350lK-M8HSaDc_EnZ-SunHZkd6JLRLeLxsNEjqrKcbhuo5KsznvRWxKK_owCoKBW9Ck=@protonmail.com>


> So I guess it's a too many open connections error, but instead of
> saying that, it sets the status to the undocumented file-error.

I found a relevant commit from 2018 by Lars, and its commit says:

src/process.c (connect_network_socket): When an async :family
'local client fails (with a file error, for instance), mark the
process as failed.

https://github.com/emacs-mirror/emacs/commit/92ba34d89ac4f5b5bbb818e1c39a3cc12a405790#diff-18c8f6291e2c6a6f88223e509421492528e624157da1ba063401a6ffc36e63b6L3595

Does failed here mean the Qfailed status? Then why is status set to
to the car of file error returned by get_file_errno_data  which
returns file-error or some other file related bug?

Somebody who was part of this discussion then may be able to shed
some light on it.






  reply	other threads:[~2022-02-06 12:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-06  7:26 bug#53814: process-status returns invalid/undocumented status file-error for network process emacsq via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-06 10:44 ` emacsq via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-06 12:32   ` emacsq via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-02-06 23:26     ` Lars Ingebrigtsen
2022-02-06 23:27   ` Lars Ingebrigtsen
2022-02-07  6:39     ` emacsq via Bug reports for GNU Emacs, the Swiss army knife of text editors

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='fRYY5cXxkYnCAumdGdTVwiQJMTOI3qMnSnR6XWfdAFvIO9pZkYoQ7csC2rK7vrQHJHv1iioKYbHOYB8c11KMaKU23gn3ijUPzhI0nssGpYQ=@protonmail.com' \
    --to=bug-gnu-emacs@gnu.org \
    --cc=53814@debbugs.gnu.org \
    --cc=laszlomail@protonmail.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. 
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).