-
Notifications
You must be signed in to change notification settings - Fork 599
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
Switch to conduit-hyper
in place of civet
#1618
Conversation
I'm seeing an issue with this in staging, this isn't ready to merge yet. |
`conduit-hyper` now handles normalizing paths, such that `//api/v1` becomes `/api/v1` and doesn't break our router.
dfb6e98
to
6c947e3
Compare
Okay, I pushed a new version of Here is a crate I published on staging using this PR: https://jtgeibel-staging-crates-io.herokuapp.com/crates/hello-world |
Holding off on merging for now so I can deploy this by itself and be around watching metrics after, but this LGTM |
@bors r+ |
📌 Commit 6c947e3 has been approved by |
Switch to `conduit-hyper` in place of `civet` `conduit-hyper` now handles normalizing paths, such that `//api/v1` becomes `/api/v1` and doesn't break our router.
☀️ Test successful - checks-travis |
Revert "Auto merge of #1618 - jtgeibel:conduit-hyper-round2, r=sgrif" This reverts commit 69368a6, reversing changes made to 6fa8ad3. When deploying this change, we saw response times nearly triple, and our CPU usage went through the roof. Additionally, this did not appear to fix the memory issues we were hoping to address by removing civet. /cc @jtgeibel
conduit-hyper
now handles normalizing paths, such that//api/v1
becomes
/api/v1
and doesn't break our router.