47d8807b69
## Motivation Currently, `tracing` uses GitHub Actions for CI. However, we have previously used both Travis and Azure Pipelines CI. Some artifacts of previous CI configurations, such as badges and config files, still exist in the repo. This can be confusing, since some of these CI configurations imply things that aren't currently true (such as old MSRV versions). ## Solution This branch removes the following: - Azure Pipelines badges from cargo metadata. These currently show up as "never built" on crates.io, since the Azure build is turned off. So, we should just remove them. - `.travis.yml`. We don't use Travis and there's no sense keeping around an old config file. - `azure-pipelines.yml`. Similarly, we no longer need this. Fixes: #669 Signed-off-by: Eliza Weisman <eliza@buoyant.io>
tracing-futures
Utilities for instrumenting futures-based code with tracing.
Overview
tracing is a framework for instrumenting Rust programs to collect
structured, event-based diagnostic information. This crate provides utilities
for using tracing to instrument asynchronous code written using futures and
async/await.
The crate provides the following traits:
-
Instrumentallows atracingspan to be attached to a future, sink, stream, or executor. -
WithSubscriberallows atracingSubscriberto be attached to a future, sink, stream, or executor.
License
This project is licensed under the MIT license.
Contribution
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in Tracing by you, shall be licensed as MIT, without any additional terms or conditions.