retina
futures-rs
retina | futures-rs | |
---|---|---|
4 | 11 | |
212 | 5,254 | |
- | 0.9% | |
7.6 | 8.4 | |
about 1 month ago | 9 days ago | |
Rust | Rust | |
Apache License 2.0 | Apache License 2.0 |
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.
retina
-
S p a m m y s y s C a l l s in strace dumps
Yeah, excellent description of why the volume is so high, and when you're tracing a multithreaded one there's the additional noise from the way they're interleaved.
Besides filtering, I forgot to mention that some kind of aggregation/summary. strace flags are useful; even better to write a little program with eBPF (on Linux) or DTrace (on macOS/BSD/Solaris). I like being able to do stuff like this: https://github.com/scottlamb/retina/issues/5#issue-933945792
- Managing and using ONVIF IP cameras with Linux
-
Async cancellation: a case study of pub-sub in mini-redis
I suspected exactly that in this issue in one of my libraries, but when I actually looked with strace, I didn't see many syscalls returning EWOULDBLOCK. So then after that measurement, my new theory was that e.g. tokio::net::{Udp,Tcp}Socket would skip actually issuing the syscall if the mio layer hasn't returned availability since the last poll. Not true? Maybe I need to run my experiment again...
-
What's everyone working on this week (23/2021)?
I'm plugging my new RTSP library retina into moonfire-nvr. But progress may be slow this week due to family obligations.
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
What are some alternatives?
neolink - An RTSP bridge to Reolink IP cameras
tokio - A runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...
aboba - Yet another audio book player (mobile friendly)
async-std - Async version of the Rust standard library
tiny-tokio-actor - A simple tiny actor library on top of Tokio
carboxyl - Functional Reactive Programming library for Rust
moonfire-nvr - Moonfire NVR, a security camera network video recorder
mioco - [no longer maintained] Scalable, coroutine-based, fibers/green-threads for Rust. (aka MIO COroutines).
gdbstub - An ergonomic, featureful, and easy-to-integrate implementation of the GDB Remote Serial Protocol in Rust (with no-compromises #![no_std] support)
tangle - Deprecated - Use https://github.com/alexcrichton/futures-rs instead
artillery - Fire-forged cluster management & Distributed data protocol
coio-rs - Coroutine I/O for Rust