bug#24201: 25.1.50; TLS connections sometimes hang

[Eli Zaretskii]

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: "Basil L. Contovounesios" <contovob@tcd.ie>,  24201@debbugs.gnu.org,  
> eggert@cs.ucla.edu
> Date: Thu, 04 Jul 2019 15:04:54 +0200
> 
> With the following patch, connection never hangs:
> 
> diff --git a/lisp/net/network-stream.el b/lisp/net/network-stream.el
> index 2b3292b71b..cdb33a59f1 100644
> --- a/lisp/net/network-stream.el
> +++ b/lisp/net/network-stream.el
> @@ -376,7 +376,7 @@ network-stream-get-response
>       (goto-char start)
>       (while (and (memq (process-status stream) '(open run))
>                   (not (re-search-forward end-of-command nil t)))
> -       (accept-process-output stream 0.05)
> +       (accept-process-output stream 0.05 nil t)
>         (goto-char start))
>       ;; Return the data we got back, or nil if the process died.
>       (unless (= start (point))

Does this mean you have other process objects active at that time?

> It's the JUST-THIS-ONE parameter: If that's non-nil, then
> accept-process-output returns after the timeout...  and we get the data.

I don't understand: accept-process-output is supposed to hit the
timeout only when there's no data.  But you say "and we get the
data".  So what am I missing here?