cygwin 3.3.x: another problem that may be related to pipes

[Takashi Yano]

On Mon, 15 Nov 2021 13:47:44 -0500
Ken Brown wrote:
> On 11/15/2021 11:52 AM, Takashi Yano wrote:
> > On Mon, 15 Nov 2021 11:37:30 -0500
> > Ken Brown wrote:
> >> On 11/15/2021 11:08 AM, Corinna Vinschen wrote:
> >>> The idea was to do change to synchronous pipes only for 3.4.  I have a
> >>> bit of headaches to change the pipes to synchronous as bug fix on the
> >>> 3.3 branch.  Your first ideas might be better there...
> >>
> >> I agree.  I'd rather fix the bugs with asynchronous pipes on the 3.3 branch and
> >> only switch to synchronous pipes for 3.4.
> > 
> > I also agree with you.
> > 
> > So, currently we have three options.
> > 
> > 1) Call CancelIo() immediately after STATUS_PENDING like my patch.
> > 2) Wait for pipe handle after STATUS_PENDING for nonblocking mode
> >     like Ken's patch.
> > 3) Create evt event even for nonblocking mode as Corinna mentioned.
> > 
> > Which is the best solution, do you think?
> 
> I'm completely unbiased, of course, but I like option 2.

OK. Shall I make a patch? Or would you like to do that?
What should we do for master branch? I think topic/pipe
is still under test. So, should we apply the same patch
to master as well as cygwin-3_3-branch?

-- 
Takashi Yano <takashi.yano@nifty.ne.jp>