Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

net: read/write timeout error should say "read timeout" or "write timeout", not EAGAIN #1078

Closed
rsc opened this issue Sep 4, 2010 · 5 comments

Comments

Projects
None yet
4 participants
@rsc
Copy link
Contributor

commented Sep 4, 2010

from golang-nuts:

Hello,

Sorry that I made you loose your time, I've found the problem, I was
setting SetTimeout wrong, so it always returned because the timeout
was very short. Maybe the error could be clearer, something like a
"read timeout" could be much more useful than this.

Thanks anyway, and sorry again.

2010/9/3 Roger Pau Monn=C3=A9 <royger@gmail.com>:
> I've just pushed a new version, that saves a log of every session with
> every peer, create a "logs" folder inside "wgo" folder, and run
it. I
> see this error in almost every file. Although the program is able to
> download a torrent.
>
> 2010/9/3 Roger Pau Monn=C3=A9 <royger@gmail.com>:
>> I'm using Mac OS X 10.6.4 and amd64 version of go (release
>> 2010-08-25). It happens with this program:
>>
>> http://github.com/royger/wgo (check the Wire.go file)
>>
>> I will try to make a simpler example tomorrow.
>>
>> Thanks, Roger.
>>
>> 2010/9/3 Russ Cox <rsc@golang.org>:
>>>> I'm working with net.Conn (tcp4), and I get a lot of "resource
>>>> temporarily unavailable" using io.ReadFull, what can I do to avoid
>>>> this? Or what should I do when I receive this error?
>>>
>>> You're not supposed to get that error.
>>> Read is supposed to take care of the
>>> blocking for you.
>>>
>>> Can you post a program that demonstrates
>>> the problem, and also say which operating
>>> system and architecture you're using?
>>>
>>> Thanks.
>>> Russ
>>>
@rsc

This comment has been minimized.

Copy link
Contributor Author

commented Dec 9, 2011

Comment 1:

Labels changed: added priority-later.

@rsc

This comment has been minimized.

Copy link
Contributor Author

commented Dec 12, 2011

Comment 2:

Labels changed: added priority-go1.

@robpike

This comment has been minimized.

Copy link
Contributor

commented Jan 13, 2012

Comment 3:

Owner changed to builder@golang.org.

@mikioh

This comment has been minimized.

Copy link
Contributor

commented Jan 16, 2012

Comment 4:

Looks like this issue was fixed in:
changeset:   10443:b5c1528ecf37
user:        Russ Cox <rsc@golang.org>
date:        Sun Nov 13 22:44:52 2011 -0500
wasn't it?
@rsc

This comment has been minimized.

Copy link
Contributor Author

commented Jan 16, 2012

Comment 5:

Status changed to Fixed.

@rsc rsc added fixed labels Jan 16, 2012

@rsc rsc added this to the Go1 milestone Apr 10, 2015

@rsc rsc removed the priority-go1 label Apr 10, 2015

@golang golang locked and limited conversation to collaborators Jun 24, 2016

This issue was closed.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.