Skip to content

Return if the stream is nonblocking #42

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

Merged
merged 2 commits into from
Jun 27, 2013

Conversation

bjoernhaeuser
Copy link
Collaborator

If the stream is nonblocking we actually get this invalid packet and
should just stop.

@noplay you introduced the new behaviour. I think we need to stop the stream if we got such an packet. What do you think? This could have also caused the problem you had with your tests?

If the stream is nonblocking we actually get this invalid packet and
should just stop.
@julien-duponchelle
Copy link
Owner

Perhaps we can test if it's an EOF packet

@bjoernhaeuser
Copy link
Collaborator Author

Just updated, what do you think?

@julien-duponchelle
Copy link
Owner

Yeah i think it's ok. I think we can add a test in order to avoid breaking it

@bjoernhaeuser
Copy link
Collaborator Author

I think the other tests problems you had are the same I had. This should fix both.

julien-duponchelle added a commit that referenced this pull request Jun 27, 2013
Return if the stream is nonblocking
@julien-duponchelle julien-duponchelle merged commit 51a2c7d into master Jun 27, 2013
@julien-duponchelle julien-duponchelle deleted the non_blocking_connections branch June 27, 2013 09:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants