Xiretza

FYI, I've rebased this on master and factored out all the unrelated changes in this branch of mine, you might want to work off that if you continue with this:...

@Half-Shot: > We'd really like to feel confident in hookshot's stability, and then we could probably give a green light from our side. https://github.com/matrix-org/matrix-hookshot/issues/594 has been fixed, are there any...

No, same issue with qt6 and master (346a39ba1).

@YasserKa what's your `:version` output with qt6? As I said, qt6 doesn't fix it for me, so I'd be curious if there are any obvious differences: ``` qutebrowser v2.5.4 Git...

> Which user agent are you on? The default, `Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) QtWebEngine/6.5.2 Chrome/108.0.5359.220 Safari/537.36`. As an update, this still happens with 3.0.0 in a...

You're probably right, how about adding something like `ret(only_ok)` that makes the behaviour opt-in?

Personally I would still find it useful to have an attribute that logs only successful returns. I don't really care about errors, they bubble up to the top and get...

If we're talking about doing breaking changes, how about this concept: - `#[instrument(ret(OPTS))]` emits the return value regardless of type - `#[instrument(ret(ok(OPTS)))]` emits only `Ok` return values (fails to compile...

Just happened to me with 1.11.33 on Arch. I sent logs (using this issue URL), can I do anything else to help this get fixed?

The last item is required for codebases that use both `autocxx` to generate bindings to C++ functions using [`extern_rust_type!()`](https://docs.rs/autocxx/latest/autocxx/extern_rust/attr.extern_rust_type.html), and also manually use `cxx` to expose Rust functions using the...