Danilo Bargen

@urkle is this still an issue for you? If yes, a PR with a cargo feature `no-log-printing` would be welcome.

~~Hm, I don't really know where this is looking from. The traceback doesn't even contain a mention of `tracing_test`, but that is to be expected since it's a macro which...

I guess the buffer could be bounded as an option. Right now this is not configurable. There are no plans from my side to change this, but if the implementation...

@dan-da I agree that your suggestion makes sense. However, the implementation is tricky. I see two (or three) approaches: --- ### Having a separate log buffer per test This would...

I haven't yet investigated this issue. Do you know a way to do this reliably? > determine the name of the main crate for the package If yes, then it...

Yes, you're right, I think this is not currently supported. Right now the subscriber simply writes bytes to a `Vec` writer, and the default output doesn't contain recorded fields I...

This is how the "mock subscriber" is initialized: https://github.com/dbrgn/tracing-test/blob/main/tracing-test/src/subscriber.rs#L56-L66 It's been a while since I wrote that code, but we'd have to check how the span information is passed on...

Related to #2.

> And while using mDNS to hide non-default route candidates would likely improve the situation, I'm convinced that we will see _consent_ vs. _no consent_ diverge further. Chrome will apply...

Another datapoint here :) I work on a project where we provide a web application that can connect to a smartphone app and exchange data. We are perfectly fine asking...