Commit Graph

14 Commits

Author SHA1 Message Date
Lucio Franco fd2d034e97
ci: Re-enable ci (#389)
* ci: Re-enable ci

* ci: Re-enable ci

* Actually use stable
2019-12-11 15:01:02 -05:00
Lucio Franco c3c6780d31
service: Update docs and prepare for 0.3 release (#369)
* service: Update docs and prepare for 0.3 release

* Update rustmft

* Disable main tower crate
2019-11-29 11:48:08 -05:00
Lucio Franco abe5b78542
Remove tokio alpha.6 patches (#357)
* Remove tokio alpha.6 patches

* Remove ci patch
2019-09-30 21:15:26 -04:00
Taiki Endo 03dc7069aa Update pin-project to 0.4 (#350) 2019-09-30 14:58:27 -04:00
Jon Gjengset d5b36b54a5
Re-enable all CI (#353)
CI has to run on nightly for the time being.

Also includes changes to make buffer tests more reliable.
2019-09-24 18:56:37 -04:00
Jon Gjengset 6baf381879
Consistently apply deny/warn rules (#352)
This makes all tower subcrates have the following lints as warn (rather
than allow): `missing_docs`, `rust_2018_idioms`, `unreachable_pub`, and
`missing_debug_implementations`. In addition, it consistently applies
`deny(warning)` *only* under CI so that deprecations and macro changes in minor
version bumps in dependencies will never cause `tower` crates to stop
compiling, and so that tests can be run even if not all warnings have been
dealt with. See also https://github.com/rust-unofficial/patterns/blob/master/anti_patterns/deny-warnings.md

Note that `tower-reconnect` has the `missing_docs` lint disabled for now
since it contained _no_ documentation previously. Also note that this
patch does not add documentation to the various `new` methods, as they
are considered self-explanatory. They are instead marked as
`#[allow(missing_docs)]`.
2019-09-23 17:28:14 -04:00
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
Carl Lerche 8a646dd25c
ci: fix isRelease condition (#274) 2019-04-27 09:32:40 -07:00
Carl Lerche 14f4259518
Prepare release (#273)
The following crates are to be released:

- tower
- tower-buffer
- tower-discover
- tower-layer
- tower-limit
- tower-load-shed
- tower-retry
- tower-service
- tower-test
- tower-timeout
- tower-util
2019-04-26 21:31:25 -07:00
Carl Lerche 92f4a0cb72
Rename tower-util -> tower (#197) 2019-03-15 10:53:19 -07:00
Carl Lerche 749e46b3f5
ci: `cd` into crate instead of `-p $crate` (#176)
Cargo is buggy when specifying the crate to run a command against.
2019-03-01 09:03:23 -08:00
Carl Lerche 8bb8c2d48e
Try fixing doc deploy again (#173) 2019-02-28 14:25:41 -08:00
Carl Lerche cb67f5d6c3
Try fixing deploy docs (#172) 2019-02-28 12:20:55 -08:00
Carl Lerche de799582fb
Switch CI to Azure Pipelines (#171) 2019-02-28 12:08:29 -08:00