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.

Sign up for GitHub

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

Jump to bottom

resolves #24: update tokio #25

Merged
merged 5 commits into from May 8, 2019
Merged

resolves #24: update tokio #25

merged 5 commits into from May 8, 2019

Commits on Apr 30, 2019

  1. port to tokio-0.2

    @canndrew @povilasb
    canndrew authored and povilasb committed Apr 30, 2019
    Configuration menu
    Copy the full SHA
    5ad23d2 View commit details
    Browse the repository at this point in the history

Commits on May 1, 2019

  1. Fix tokio-0.2 port

    @canndrew @povilasb
    canndrew authored and povilasb committed May 1, 2019
    Configuration menu
    Copy the full SHA
    6f877d5 View commit details
    Browse the repository at this point in the history

Commits on May 2, 2019

  1. bugfix: enter tokio event loop earlier

    @canndrew @povilasb
    canndrew authored and povilasb committed May 2, 2019
    Configuration menu
    Copy the full SHA
    2b9895a View commit details
    Browse the repository at this point in the history

  2. Fix examples and tests 

    Make sure Network is not dropped before we actually finish running our final future.
Before Network object was moved into future::lazy() closure which would then
drop the Network before we actually we finished which resulting in panicking.
    @povilasb
    povilasb committed May 2, 2019
    Configuration menu
    Copy the full SHA
    15bd0df View commit details
    Browse the repository at this point in the history

  3. Update tokio related crates

    @povilasb
    povilasb committed May 2, 2019
    Configuration menu
    Copy the full SHA
    bb1fc7d View commit details
    Browse the repository at this point in the history