Thomas Eizinger

Conditional CI runs have largerly mitigated this.

Yeah, I thought we had something like this at some point.

It is not fixed but also not strictly necessary at the moment. It could be useful during debugging with a relay to know which version of the Client is talking...

Would "open log directory" be the better button-action perhaps? Users can zip a few files themselves, right?

> Hi François, and thanks for this! @thomaseizinger do you know if there's reason for the mismatch in the suffix? If it's a bug I think it makes more sense...

> Do let me know how I can help with this... Unfortunately, this is currently blocking an upgrade for me, so I'd like to help resolve this. 🙂 Same here....

Is there a discussion somewhere on why the `random_from_rng` functions don't use the fallible rng traits? https://github.com/dalek-cryptography/curve25519-dalek/blob/c3a82a8a38a58aee500a20bde1664012fcfa83ba/x25519-dalek/src/x25519.rs#L90 It seems to me that the APIs would be more flexible like this:...

`sentry-tracing` is one of these integrations that would greatly benefit from this feature: https://docs.rs/sentry-tracing/latest/sentry_tracing/#tracking-errors Instead of a special symbol, could we perhaps specialise on the `error` name itself and require...

> > Another idea could be a wrapper struct. > > This is how `?` and `%` are implemented today (for `?` take a look at [tracing_core::field::DebugValue](https://docs.rs/tracing-core/latest/tracing_core/field/struct.DebugValue.html) and [the debug...

> so I'm thinking to create a wrapper type that either records the inner T or `tracing::field::Empty`. This is already possible: ```rust let my_option = Some(2); let my_value = my_option.map(tracing::field::display);...