tower/ci
Oliver Gould 42f4b7781e
spawn-ready: Drives a service's readiness on an executor (#283)
Some layers cannot guarantee that they will poll inner services in a
timely fashion. For instance, the balancer polls its inner services to
check for readiness, but it does so randomly. If its inner service
must be polled several times to become ready, e.g., because it's driving
the initiation of a TLS connection, then the balancer may not drive the
handshake to completion.

The `SpawnReady` layer ensures that its inner service is driven to
readiness by spawning a background task.
2019-05-29 09:57:46 -07:00
..
azure-deploy-docs.yml Try fixing doc deploy again (#173) 2019-02-28 14:25:41 -08:00
azure-install-rust.yml ci: `cd` into crate instead of `-p $crate` (#176) 2019-03-01 09:03:23 -08:00
azure-is-release.yml ci: fix isRelease condition (#274) 2019-04-27 09:32:40 -07:00
azure-patch-crates.yml Prepare release (#273) 2019-04-26 21:31:25 -07:00
azure-rustfmt.yml ci: `cd` into crate instead of `-p $crate` (#176) 2019-03-01 09:03:23 -08:00
azure-test-stable.yml ci: fix isRelease condition (#274) 2019-04-27 09:32:40 -07:00
patch.toml spawn-ready: Drives a service's readiness on an executor (#283) 2019-05-29 09:57:46 -07:00