You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Notice that there's no way of running the 'loop' more than once. Can anyone explain this?
I think the loop should just be removed, unlike read/write, you can't call connect() more than once if it blocks.
The text was updated successfully, but these errors were encountered:
Without the history, we could only guess what originally happened. It doesn't look like it handles EAGAIN properly (EAGAIN==EWOULDBLOCK). According to the man page this would only happen if the system runs out of auto-assign ports, in which case it should probably just raise oserror. I would just remove the check for EWOULDBLOCK and remove the while 1, leaving the check for EINPROGRESS as-is.
Notice that there's no way of running the 'loop' more than once. Can anyone explain this?
I think the loop should just be removed, unlike read/write, you can't call connect() more than once if it blocks.
The text was updated successfully, but these errors were encountered: