Eliza Weisman
Eliza Weisman
It would be nice to be able to filter which tasks are displayed in the tasks list. Some ways we might want to filter the tasks list: - By name...
Users should be able to turn individual warnings on and off, using the command line and/or possibly an eventual config file. I discussed this briefly in https://github.com/tokio-rs/console/issues/56#issuecomment-916256883. Here's a rough...
I was talking to @olix0r about the console's new warnings feature, and he had a suggestion that seemed worth looking into: it would be cool to add a mode where...
when a new task is spawned ,the `TasksLayer` in `console-subscriber` should capture the parent span context in which the task was spawned. we'll need to send the parent spans' data...
Right now, the `TasksLayer` in `console-subscriber` _only_ captures the span attached to every spawned task by Tokio's own `tracing` integration. these spans are useful, but they lack a lot of...
it would be cool if the console could also aggregate metrics from the incoming data and compute percentiles of stats like scheduler latency, active tasks, and poll/idle durations over a...
`h2` currently permits configuring most of the HTTP/2 protocol settings that are negotiated with the remote peer; for example, the client builder [can configure settings like maximum frame size, maximum...
When the thread ID limit defined by the `Config` is reached, we currently panic. This isn't great. As I said in tokio-rs/tracing#1485: > I do think `sharded-slab` could handle this...
In some cases, entries will not be accessed concurrently. It might be nice to have an API for mutably accessing an entry by index if it is not being concurrently...
It should be possible to clone a guard fairly trivially, by incrementing the ref count on the accessed entry.