Natalie Klestrup Röijezon

More concretely, this is because schemars currently serializes enums as: ```yaml properties: enum: oneOf: - type: object - properties: variantOne: # properties... required: [variantOne] - type: object properties: variantTwo: #...

FWIW I ended up implementing this in kube-rs as a schemars `Visitor`: https://github.com/kube-rs/kube-rs/pull/779.

I think we would need to do something like this to ensure that schemars knows how to identify and propagate errors: ```rust pub trait OutputVisitor { type Error; fn visit_root_schema(&mut...

Most linux distributions, even those that still default /usr/bin/python to Python 2.x have a /usr/bin/python2 binary as well to explicitly request 2.x (and the opposite applies for 3.x as well)....

> I think `let v = *v;` would do something different (e.g. dereference a `String` to `str`), but `let v = {v};` (or just `{v}` if there’s only one use...

Had this issue too, with 2.12.4. This happens for me when MyPostgresProfile is a class (which the Ammonite example should become too), but not when it's a trait.

:+1: I think issues like #61 make it pretty clear that native TLS is usually a mistake (or at least shouldn't be the default option).

> Maybe we could have something like a ONCE'd TestEnv::shared setup, so that each #[tokio::test] can get a dynamically created namespace to perform their test? That way, the whole namespaced...

Another thing: Many tests probably shouldn't need anything else than the API and maybe the controllers, so that should be able to get the provisioning time down a fair bit...

To be honest, it kind of feels like we're just "infecting" more and more aspects of the library with having to thread through `Context`, while requiring the user to pay...