console
nextest
console | nextest | |
---|---|---|
20 | 16 | |
3,172 | 1,954 | |
2.4% | 2.1% | |
8.5 | 9.8 | |
6 days ago | 1 day ago | |
Rust | Rust | |
MIT License | 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.
console
-
Rust Tooling: 8 tools that will increase your productivity
tokio-console is a debugger for Rust async programs that use Tokio. To get started, add the console-subscriber crate to your project and add the following line which will initialise the subscriber and allow tokio-console to connect to it:
-
How to detect lock contention in rust?
You could try https://github.com/tokio-rs/console to debug and profile what happens with tokio tasks in your program.
-
Using Rust at a startup: A cautionary tale
The tokio-console CLI is a fun one. The console-subscriber supports shipping to a console server running elsewhere, apparently. That gives you a window into what's happening now.
-
Hey Rustaceans! Got a question? Ask here! (42/2022)!
Tokio console maybe? https://github.com/tokio-rs/console
-
use both of tracing-subscriber and tokio-soncole
If I add "console_subscriber::init()" line as https://github.com/tokio-rs/console recommends, tracing_subscriber cannot be initialized.
-
Any recommendations for profiling High performance rust code?
I'm building an HTTP load tester called pdc! I have run out of obvious (to me at least) places to look for performance gains. I'm achieving around 45,000 requests per second, per core. Right now I'm using hyper with a separate tokio runtime (in current thread mode) running on each core. So far having runtime on each core/NUMA node has really helped with cache coherency. Any recommendations for profiling beyond tokio console or tokio metrics (Convenient timing amirite!)?
-
Announcing `tracing` 0.1.30 with experimental `valuable`support!
It was just an accident and has been fixed https://github.com/tokio-rs/console/issues/270.
-
[Question] Is Tokio a poor fit for non-network related concurrent applications?
P.S. Tokio [now also has Tokio Console](https://github.com/tokio-rs/console) allowing you to conveniently troubleshoot your tasks if they are causing issues :)
-
How do I profile a Rust web application in production?
You can opt-in to async runtime such as tokio, and you can use tokio-rs/console for it's top-like metric
- `tokio::spawn` to handle `actix` message doesn't wait?
nextest
-
Rust Tooling: 8 tools that will increase your productivity
cargo-nextest describes itself as a “next-generation Rust test runner”. To install, you need to run cargo install cargo-nextest.
-
My favourite Git commit (2019)
> On my work I make 1-15 commits a day. If I have to spend thought cycles on the commit message, that is time that goes from other productive endeavours.
I make roughly that many commits a day as well. If something's easy to understand I'll put in a simple commit message (e.g. [1]), but I do put in the effort for more complicated ones.
[1] https://github.com/nextest-rs/nextest/commit/efd194b2e1d8d61...
[2] https://github.com/oxidecomputer/omicron/commit/b07a8f593325...
-
Rust tech stack
If you need fancier testing than what's built into Rust, cargo-nextest is becoming quite popular.
-
Customizable testing framework
https://nexte.st/ is what is getting all the attention as a replacement test harness/framework these days.
-
Hey Rustaceans! Got a question? Ask here (11/2023)!
I believe cargo-nextest supports running separate binaries concurrently.
-
Fellow Rust enthusiasts: What "sucks" about Rust?
Do you already use nextest or something else? That really leans into test parallelism and sounds like a perfect fit for how you structure the tests.
- Альтернативний спосіб запускати тести
-
buffer-unordered-weighted: a variant of StreamExt::buffer_unordered where each future has a weight
I built it for cargo-nextest, in service of a new feature where some tests can be marked as heavier than others.
-
Small changes you can make in a rust codebase that have a significant impact
IMO 100% worth checking out: https://nexte.st/
-
Why does Rusts testing tools seem so much less polished compared to its other tooling?
For me, most of my needs are covered with next-test(https://nexte.st/), not that I have ever used any of the things you mentioned 😅
What are some alternatives?
mirage - MirageOS is a library operating system that constructs unikernels
cargo-release - Cargo subcommand `release`: everything about releasing a rust crate.
tracing - Application level tracing for Rust.
cargo-limit - Productivity improvements for Rust ecosystem: warnings are skipped until errors are fixed, LSP-independent Neovim integration, etc.
loom - Concurrency permutation testing tool for Rust.
cargo-deny - ❌ Cargo plugin for linting your dependencies 🦀
prost - PROST! a Protocol Buffers implementation for the Rust Language
shadow-rs - A build-time information stored in your rust project.(binary,lib,cdylib,dylib)
evcxr
Cargo - The Rust package manager
delve - Delve is a debugger for the Go programming language.
TestNG - TestNG testing framework