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

Update dependencies (mio 0.6, slab 0.3) #61

Merged
merged 3 commits into from
Nov 1, 2016

Conversation

therustmonk
Copy link
Contributor

This PR updates dependencies of this crate.
I've done it to prepare the crate for some experiments with #56

All changes keeps backward compatibility, but some implementations changed. I've changed accept methods, because mio has changes with API and most of structs used by this crate had deprecated.
Let's consider this PR as keep crate alive changes and as first step towards the new mio's API.

@zonyitoo zonyitoo merged commit 8c48876 into zonyitoo:master Nov 1, 2016
@zonyitoo
Copy link
Owner

zonyitoo commented Nov 1, 2016

Thanks

@zonyitoo
Copy link
Owner

zonyitoo commented Nov 1, 2016

Hmm, I saw Reflect has been deprecated in the latest rustc. And coroutine_size test is failed, don't know why.

@therustmonk
Copy link
Contributor Author

Thanks for merging!
I saw this fail before changes, but haven't try to fix it, because I thought it's normal behavior.
Now I see we have to fix it too. I'll open an Issue to track this problem.

@lhecker
Copy link
Collaborator

lhecker commented Nov 1, 2016

@deniskolodin The real socket tests (those in the "tests" folder) fail with EAGAIN now though - I believe your PR might not have been a perfect update. 😅

@therustmonk
Copy link
Contributor Author

@lhecker Wow! Why all tests hadn't ran? I thought cargo test runs all tests we have 😰
Any ideas how to fix? Actually mio has large API changes, It seems we should move from deprecated to a new or we have to repair it with deprecated?

@zonyitoo
Copy link
Owner

zonyitoo commented Nov 1, 2016

If mio deprecated all its IO wrappers to ::deprecated mod, did they provide some other new wrappers for this?

I saw Error { repr: Os { code: 11, message: "Resource temporarily unavailable" } in the panic message. WHY?

return Err(make_timeout());
}
}
Err(err) => {
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You have to handle err.kind() == ErrorKind::WouldBlock!!!

return Err(make_timeout());
}
}
Err(err) => {
Copy link
Owner

@zonyitoo zonyitoo Nov 1, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The same as above, you have to handle WouldBlock

@lhecker
Copy link
Collaborator

lhecker commented Nov 1, 2016

@deniskolodin I believe cargo test only runs system/end-to-end tests when all unit tests pass. Could you or @zonyitoo add --no-fail-fast to the .travis.yml file in the next commit?

Nice catch @zonyitoo! 😂

@zonyitoo
Copy link
Owner

zonyitoo commented Nov 1, 2016

I would revert this PR. Please @deniskolodin handles ErrorKind::WouldBlock properly.

@therustmonk
Copy link
Contributor Author

Ok, I'll make it right.

@lhecker
Copy link
Collaborator

lhecker commented Nov 1, 2016

@zonyitoo @deniskolodin I fixed it real quick just now. 🙂

lhecker added a commit that referenced this pull request Nov 1, 2016
lhecker added a commit that referenced this pull request Nov 1, 2016
@zonyitoo
Copy link
Owner

zonyitoo commented Nov 1, 2016

Awesome!

@therustmonk
Copy link
Contributor Author

@lhecker Thanks a lot! 😍 But what about --no-fail-fast for travis and appveyor? 😇 I can add it if you want.

@therustmonk
Copy link
Contributor Author

PR #64 adds these flags

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.

3 participants