public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: lwp-request stopped working with snapshots
Date: Tue, 14 Oct 2014 19:50:00 -0000	[thread overview]
Message-ID: <20141014195043.GH2681@calimero.vinschen.de> (raw)
In-Reply-To: <87y4si4ewp.fsf@Rainer.invalid>

[-- Attachment #1: Type: text/plain, Size: 1145 bytes --]

On Oct 14 21:41, Achim Gratz wrote:
> Corinna Vinschen writes:
> > lwp-request is one of the tools using connect to try if a former
> > non-blocking connect worked.  This is ugly but, sigh, valid behaviour,
> 
> What should it be doing instead?  LWP upstream has switched to a new
> maintainer recently IIRC, so it might be a good time to suggest a few
> cleanups.

Calling select or poll instead.  But, anyway, uglyness is in the eye of
the beholder and ultimately it *is* a valid approach and it worked
before.  So it was clearly a newly introduced bug in Cygwin.

> > The latest changes to the socket code didn't take this scenario into
> > account.  I applied a fix and uploaded a new snashot to
> > https://cygwin.com/snapshots/
> >
> > Please give it a try.
> 
> I sure will do this first thing tomorrow, thanks!

Oh, good!  I just realized that I missed to handle EALREADY, so I
applied YA patch and just replaced the snapshot with a new one.


Thanks,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2014-10-14 19:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-14 18:22 Achim Gratz
2014-10-14 19:34 ` Corinna Vinschen
2014-10-14 19:42   ` Achim Gratz
2014-10-14 19:50     ` Corinna Vinschen [this message]
2014-10-15  5:50       ` Achim Gratz
2014-10-15  9:51         ` Achim Gratz
2014-10-15 13:05       ` Andrey Repin
2014-10-15 14:26         ` Corinna Vinschen

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

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

  git send-email \
    --in-reply-to=20141014195043.GH2681@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin@cygwin.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.
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).