Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upPort to Tokio 0.2 #307
Port to Tokio 0.2 #307
Conversation
fix cargo fmt loosen up clippy to warnings on examples snipe dev deps from core eliminate some clippy warnings for examples add publish false, and remove publish requirements rename tide-examples to just examples
Precursor: Tide core isolation revamp
Fix example link in readme
Rename `serve` to `run`, add asynchronous `serve`
Co-Authored-By: Wonwoo Choi <chwo9843@gmail.com>
Check example in readme compiles during testing
Remove #[allow(unused_mut)]
Middleware-based compression and decompression
Improve curl command consistency
* Move core traits and types to tide-core * Move cookies middleware to tide-cookies * Remove unncessary dependencies and use relative paths in README
* Update travis config * Separate out individual build jobs for faster wall-clock testing * Fix clippy not actually denying warnings (excluded examples because these are currently failing and have non-trivial fixes) * Add build job that checks --no-default-features works * Add build job that checks for intra-doc-resolution failures (excluded tide because of bugs in re-exports with the intra-doc feature) * Fix warnings * Fix doc-link in tide-cookies
Signed-off-by: Yoshua Wuyts <yoshuawuyts@gmail.com>
Signed-off-by: Yoshua Wuyts <yoshuawuyts@gmail.com>
Overall this looks good, but I think we can probably change out the |
http-service = "0.3.1" | ||
http-service-hyper = { version = "0.3.1", optional = true } | ||
http-service = { git = "https://github.com/rustasync/http-service", branch = "tokio-0.2" } | ||
http-service-hyper = { git = "https://github.com/rustasync/http-service", branch = "tokio-0.2", optional = true } |
This comment has been minimized.
This comment has been minimized.
yoshuawuyts
Sep 2, 2019
Member
Is this still needed? I believe we already published updated versions right?
This comment has been minimized.
This comment has been minimized.
vorot93
Sep 2, 2019
•
Author
Contributor
If you look closely, this actually depends on the branch. Specifically, this one:
Besides, that branch depends upon git hyper
anyway.
This comment has been minimized.
This comment has been minimized.
secretfader
Sep 3, 2019
Contributor
0.3.1
was supposed to release earlier, but I only got it done today after seeing http-rs/http-service#45
Is there a reason we aren't using overrides for the Git dependencies in this branch? (Seems that would prevent issues with publishing, but correct me if I'm wrong.)
This comment has been minimized.
This comment has been minimized.
Updates the requirements on [env_logger](https://github.com/sebasmagri/env_logger) to permit the latest version. - [Release notes](https://github.com/sebasmagri/env_logger/releases) - [Changelog](https://github.com/sebasmagri/env_logger/blob/master/CHANGELOG.md) - [Commits](sebasmagri/env_logger@v0.6.1...v0.7.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
This comment has been minimized.
This comment has been minimized.
abonander
commented
Sep 25, 2019
What's the status on this? I wanted to see if my refactor on master of |
Updates the requirements on [juniper](https://github.com/graphql-rust/juniper) to permit the latest version. - [Release notes](https://github.com/graphql-rust/juniper/releases) - [Commits](graphql-rust/juniper@juniper-0.13.1...juniper-v0.14.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
@secretfader It looks like the whole repository has been ripped inside out. This PR should be redone from scratch now. Even then I'm not sure that things won't break again in the process. |
This comment has been minimized.
This comment has been minimized.
@vorot93 hi! I'm currently working on rebasing past commits based on a single repo; this may take a few days. Thanks so much for the work you've done, and apologies for the inconvenience! -- I'm hoping we can take the work that was done here and land it again soonish! |
This comment has been minimized.
This comment has been minimized.
abonander
commented
Nov 11, 2019
Should this be closed now? https://www.reddit.com/r/rust/comments/duvdzz/announcing_asyncstd_10/f79oba0/ |
This comment has been minimized.
This comment has been minimized.
tyranron
commented
Nov 12, 2019
@abonander @yoshuawuyts why? Would you be so kind to explain the situation? |
This comment has been minimized.
This comment has been minimized.
abonander
commented
Nov 12, 2019
I'm only somewhat familiar with the circumstances. @yoshuawuyts can explain much better than I can. |
This comment has been minimized.
This comment has been minimized.
tyranron
commented
Nov 12, 2019
@abonander if so, why do you propose to close this PR referring only to a comment where author says he is banned? Is his work negligible or undesirable? From what I see in this PR it was sorta ongoing and OK, and then suddenly closed without any explanation |
This comment has been minimized.
This comment has been minimized.
abonander
commented
Nov 12, 2019
•
The tone of the author's comment in that thread implies they don't have access to the PR/repo to complete it and/or have no interest in finishing it. Giving any more detail means entering a discussion I have no desire to partake in. It was my comment they replied to so I felt obliged to acknowledge it. |
This comment has been minimized.
This comment has been minimized.
tyranron
commented
Nov 12, 2019
@abonander thanks for making this clear. |
This comment has been minimized.
This comment has been minimized.
@tyranron the behavior of several individuals in withoutboats/romio#106 but also through other outlets (dms, forums, repos) has been disappointing and below the standards we expect for community participation. This has been the reason why they've lost the privilege of publicly engaging on repositories that are part of this organization. Regarding upgrading to a modern runtime. That has already been implemented as part of #350, and I'll be kicking off the series of PRs required for a new release over the course of this week. |
This comment has been minimized.
This comment has been minimized.
tyranron
commented
Nov 12, 2019
@yoshuawuyts I've followed through the comments in withoutboats/romio#106 and in relevant Reddit posts, but clearly don't see any bad or disappointing behavior of @vorot93. I'm no one to judge your community standards, but the whole situation with banning contributors feels rather disappointing and even quite awkward. Anyway, thanks for the clarification. And I'm finishing this offtopic. |
vorot93 commentedAug 16, 2019
•
edited
Quickly sew this together to get started with Tokio 0.2 runtime. Due to an additional trait bound in http-service I cut Zstd support. Also I removed
App::run
, although I don't think it will really be missed sinceasync main
has become commonplace.Tested locally, appears to be working.