Natalie Klestrup Röijezon

Sure. The documentation is still a bit lacking since it's still in semi-prototype mode, but feel free to ask if (when?) anything is unclear.

> Users provide a bunch of closures for the controller fn to provide retry rules and other things, and the various user errors that can be emitted from each part...

Hm, so the idea is that `kube_rt` wraps all errors internally as `Bundled`, which `color_eyre` would pick up on when generating the `Report`?

Personally I'm leaning more towards just adding a bound that `ReconcilerErr: snafu::ErrorCompat`, which is pretty trivial to implement for custom error types regardless of whether you want to care about...

Yeah I was looking into that. > if its possible to extract snafu backtraces and convert them to std::backtrace::Backtrace `snafu::Backtrace` can be configured using Cargo features to be an alias...

Okay, I got it to bundle the `backtrace::Backtrace` (https://gitlab.com/teozkr/kube-rt/-/merge_requests/1), but `color_eyre::Report::from` doesn't seem to be picking it up (when I run it with `RUST_BACKTRACE=full` the backtrace is still from where...

Hitting this problem for `CARGO_PKG_LICENSE` as required by [built](https://docs.rs/built/latest/built/), fwiw.

Even more oddly, this only seems to happen (to me) for pinned tabs _in no container_.

We might also want to explicitly filter out `#[serde(bound)]` clauses, to avoid accidentally adding bounds for existing users (which would be a breaking change).

Everything should be resolved now (apart from `ser_bound()` which I'm still not sure about how to fix...). Feel free to skip d7e56b5 if you'd like to keep that as-is. I...