Ticket #161 (assigned Feature)
EAGAIN
| Reported by: | mrpingouin | Owned by: | toots |
|---|---|---|---|
| Priority: | 1 | Milestone: | |
| Component: | Liquidsoap | Version: | |
| Keywords: | Cc: | ||
| Mac OSX: | yes | Linux: | yes |
| NetBSD: | yes | Other Operating System: | yes |
| FreeBSD: | yes |
Description
Just a minor thing to remember and address one day...
I was listening to a stream via input.http and got disconnected because of network lag (I had a big download next at the same time). At each disconnection I obtained the following:
2008/08/13 17:49:50 [stream.vorbis:2] Read error Unix.Unix_error(2, "read", "")
My first thought was that we should make common errors more user-friendly, i.e. put an explaination instead of the exception directly. My second thought is that maybe we shouldn't even see that one, since it's actually EAGAIN: does it come from a place where we improperly use Unix.read? By the way, this error is followed by an End_of_file each time.
Change History
Note: See
TracTickets for help on using
tickets.
