dylint
tracing
dylint | tracing | |
---|---|---|
7 | 52 | |
337 | 4,958 | |
0.9% | 1.7% | |
9.7 | 7.8 | |
8 days ago | 1 day 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.
dylint
-
rustc-plugin: A framework for writing plugins that integrate with the Rust compiler
There is also https://github.com/trailofbits/dylint for writing custom lints.
-
Hey Rustaceans! Got a question? Ask here (10/2023)!
Apart from clippy (which uses rustc-internal APIs), there are two other projects which can be used to implement lints: rust-analyzer can be extended with more diagnostics, and dylint provides an interface to run custom lints for Rust.
- Dylint: Tool for running Rust lints from dynamic libraries
-
Programming Breakthroughs We Need
RE: Program is a model
There are some more advanced refactoring tools now available. These tools enable you to write code to detect bad code patterns and even automatically fix them. You can use them to write one-off transformations of code too. Rust has Dylint [1] and C# has Roslyn Analyzers [2]. Facebook has tooling [3] that helps writing CodeMods, enabling authors to generate changes for thousands of files at a time.
The thing I really would like to see is a smarter CI system. Caching of build outputs, so you don't have to rebuild the world from scratch every time. Distributed execution of tests and compilation, so you are not bottle-necked by one machine. Something that keeps track of which tests are flaky and which are broken on master, so you don't have to diagnose spurious build failures. Something that only runs the test that transitively depend on the code you change. Automatic bisecting of errors to the offending commit.
[1] https://github.com/trailofbits/dylint
[2] https://docs.microsoft.com/visualstudio/code-quality/roslyn-...
[3] one example: https://github.com/facebook/jscodeshift
-
Rust code quality and vulnerability scan tool
If you're looking for something like clippy but with custom lints, there's also dylint -- it is clippy, but with support for running dynamically loaded lints across multiple versions of Rust.
-
Missing tooling in Rust?
You might find dylint useful! It's exactly that: a tool to run custom clippy lints.
-
RiB Newsletter #27
Dylint. A tool for running Rust lints from dynamic libraries.
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?
compiler-solidity - The zkEVM Solidity compiler.
log4rs - A highly configurable logging framework for Rust
mina-vrf-rs
slog - Structured, contextual, extensible, composable logging for Rust
stateright - A model checker for implementing distributed systems.
env_logger - A logging implementation for `log` which is configured via an environment variable.
solana - Web-Scale Blockchain for fast, secure, scalable, decentralized apps and marketplaces.
log - Logging implementation for Rust
remote-apis - An API for caching and execution of actions on a remote system.
opentelemetry-rust - The Rust OpenTelemetry implementation
rust-analyzer - A Rust compiler front-end for IDEs
vector - A high-performance observability data pipeline.