Subject: bug#49449: 28: TLS connection never gets to "open" stage

From: Eli Zaretskii <[email-masked]>
Date: Sun, 11 Jul 2021 13:14:16 +0300

> Feedback-ID:[email-masked]
> From: Mattias Engdegård <[email-masked]>
> Date: Sun, 11 Jul 2021 09:42:34 +0200
> Cc: [email-masked], [email-masked]
> 
> 11 juli 2021 kl. 08.49 skrev Eli Zaretskii <[email-masked]>:
> 
> > why not reset the
> > NON_BLOCKING_CONNECT_FD bit before we call finish_after_tls_connection
> > from that place?
> 
> That's tantamount to jamming a metal screwdriver into the condition on line 3277, which was indeed the first thing I tried. Unfortunately it doesn't work -- after the sentinel is called, no further progress is made, probably because we (by lying) haven't set up the connection properly.

Did you succeed in understanding what else has to happen before that
flag could be safely reset?

And anyway, if those conditions are not yet set, I wonder why are we
calling finish_after_tls_connection at that place?