-
Notifications
You must be signed in to change notification settings - Fork 74
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
Support tokio 1.0 #46
Comments
Nonetheless, updating was already on my radar (to trim to dependency tree for clients who have already migrated). If you want to take a shot at it, go ahead 😁 |
Ah you're right, I was getting a panic in the tests saying they need to run in a tokio runtime, even though they were. Thought it was a 0.2/1.0 mismatch issue, but that was not wiremock. All is good now. I can still look at this in the next few days if no one else does, would be nice to just pull in one version. Thanks! |
I might get to work on this today/tomorrow - let's see 😁 |
With tokio 1.0 released Ive been moving things over to it. It would be good to get
wiremock
up to 1.0 too. I had a quick look, I think all deps support 1.0 now exceptasync-std
. There is a PR for that update inasync-std
async-rs/async-std#924.If this is something that you want to do I can take a look at it. Thanks.
The text was updated successfully, but these errors were encountered: