futures-rs
tracing
futures-rs | tracing | |
---|---|---|
11 | 52 | |
5,235 | 4,939 | |
0.6% | 1.7% | |
8.4 | 7.8 | |
about 1 month ago | 8 days ago | |
Rust | Rust | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
futures-rs
-
Which async channel is best?
So this is actually better than true fairness (true fairness would lead to deadlock if a sender is forgotten). It is a pity that the there does not seem to be resources that document this design. There is this old thread where Carl provides some background, but I found it personally a bit hard to follow.
-
Async cancellation: a case study of pub-sub in mini-redis
Is this still true after it switched to using FuturesOrdered?
-
I don't really understand how I'm supposed to use async
Done.
-
Confused about how to use tokio to process a vector in parallel
You can use Streams, which are the async version of Iterators; They aren't stable yet, so you'll have to use a crate such as futures.
-
What crates would you consider essential?
futures
-
How to architect Rust code on Async/Await
For traits, like AsyncRead and AsyncWrite, go with the futures crate.
-
Async Rust in Practice: Performance, Pitfalls, Profiling
Here is the PR: https://github.com/rust-lang/futures-rs/pull/2551
Yield = wake the `waker_ref`. Avoiding the yield would be clone().wake().
That said, "poll immediately" isn't actually a thing nor was it ever a thing except in incorrect implementations.
-
What sort of mature, open-source libraries do you feel Rust should have but currently lacks?
Rust lacks an implementation of ReactiveX. futures/futures-signals seems to be the the ecosystem equivalent but I'm sure there'd be a lot of interest in an actual implementation.
-
Why isn't `rc::Weak<T>` marked `UnwindSafe`when T is `RefUnwindSafe`?
The opposite problem exists as well. Many types are actually unwind safe, but do not get the autotrait. In that case authors would have to manually declare them UnwindSafe. Because this is rarely done, having an API with a trait bound T: UnwindSafe is rarely viable in terms of ergonomics. It now obliges client code to wrap all calls to your API in AssertUnwindSafe which, if they use types from third party libraries, obliges them to assert this is fine. example
-
futures 0.3.9 released with big improvement in compile time
Also, we plan to give users more control in the future. See https://github.com/rust-lang/futures-rs/issues/2207, https://github.com/rust-lang/futures-rs/issues/2295, etc. for this
tracing
-
Decrusting the tracing crate [video] by Jon Gjengset
The video description is as follows:
In this stream, we peel back the crust on the tracing crate — https://github.com/tokio-rs/tracing/ — and explore its interface, structure, and mechanisms. We talk about spans, events, their attributes and fields, and how to think about them in async code. We also dig into what subscribers are, how they pick up events, and how you can construct your own subscribers through the layer abstraction. For more details about tracing, see https://docs.rs/tracing/latest/tracing/.
-
Vendor lock-in is in the small details
> What's been your biggest issues around ergonomics/amenities for OpenTelemetry?
I can't speak generally, but in the Rust ecosystem the various crates don't play well together. Here's one example: <https://github.com/tokio-rs/tracing/issues/2648> There are four crates involved (tracing-attributes, tracing-opentelemetry, opentelemetry, and opentelemetry-datadog) and none of them fit properly into any of the others.
-
Grimoire - A recipe management application.
The tracing (logging) mechanism in an asynchronous codebase (tracing).
-
How easy is it to swap out your async runtime?
Tracing is Tokio's alternative for async code.
-
Hey Rustaceans! Got a question? Ask here (27/2023)!
At a technical level, in Rust, both [tracing]https://crates.io/crates/tracing) and log are entire ecosystems (though for the latter at least there's also third party logging frameworks), and there's at least a bridge from log to tracing.
-
How can I write a tracing subscriber that saves to a database?
I am using https://github.com/tokio-rs/tracing for logging purposes in my application. I would like to develop a feature wherein logs should be saved to a database table (via sea-orm). Something similar is this, but it does not solve my needs fully.
-
A locking war story
I've used the tracing infrastructure with tracing_flame to profile some hot paths in async code: https://github.com/tokio-rs/tracing/tree/master/tracing-flame
-
I was wrong about rust
Oh nice! IIRC when I checked, it was the Unicode tables that smashed the code size. I recently hit the same issue with the tracing crate, where a crate feature (for env var filtering) pulled in regex and my binary was suddenly 1MB bigger.
-
Debugging and profiling embedded applications.
I know about tools such as tracing, jaeger or tracy. While having a complete tracing could be a potential solution, these tools don't work with no_std.
-
Custom Axum Logging for Routes?
tracing by itself only outputs log data, you need to consume them in a subscriber, the tracing-subscriber crate exists for this. (example)
What are some alternatives?
tokio - A runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...
log4rs - A highly configurable logging framework for Rust
async-std - Async version of the Rust standard library
slog - Structured, contextual, extensible, composable logging for Rust
carboxyl - Functional Reactive Programming library for Rust
env_logger - A logging implementation for `log` which is configured via an environment variable.
mioco - [no longer maintained] Scalable, coroutine-based, fibers/green-threads for Rust. (aka MIO COroutines).
log - Logging implementation for Rust
tangle - Deprecated - Use https://github.com/alexcrichton/futures-rs instead
opentelemetry-rust - The Rust OpenTelemetry implementation
coio-rs - Coroutine I/O for Rust
vector - A high-performance observability data pipeline.