Bump conduit-hyper and limit max thread count

If a new request causes the maximum thread count to be exceeded, the
request will be rejected with a 503 Service Unavailable response.

Author: jtgeibel

Cargo.lock

@@ -75,7 +75,7 @@ conduit-router = "0.8"
 conduit-static = "0.8"
 conduit-git-http-backend = "0.8"
 civet = "0.9"
-conduit-hyper = "0.2.0-alpha.3"
+conduit-hyper = "0.2.0-alpha.4"
 
 futures = "0.3"
 tokio = { version = "0.2", default-features = false, features = ["net", "signal", "io-std"]}

Cargo.toml

@@ -63,18 +63,17 @@ fn main() -> Result<(), Box<dyn std::error::Error>> {
         println!("Booting with a hyper based server");
 
         let mut rt = tokio::runtime::Builder::new()
-            //.blocking_threads(threads as usize) // FIXME: Impl this in conduit-hyper
             .threaded_scheduler()
             .enable_all()
             .build()
             .unwrap();
 
-        let handler = Arc::new(app);
+        let handler = Arc::new(conduit_hyper::BlockingHandler::new(app, threads as usize));
         let make_service =
             hyper::service::make_service_fn(move |socket: &hyper::server::conn::AddrStream| {
                 let addr = socket.remote_addr();
                 let handler = handler.clone();
-                async move { Service::from_conduit(handler, addr) }
+                async move { Service::from_blocking(handler, addr) }
             });
 
         let addr = ([127, 0, 0, 1], port).into();