Layo

That's exactly what I meant @Blendify . All items expanded (by "all", I meant the ones allowed by `navigation_depth`)

I couldn't get it working and after not so long found the [jwcrypto](https://jwcrypto.readthedocs.io/en/latest/jwk.html#jwcrypto.jwk.JWK.export) library to export my JWKS's public key to PEM format. Right now I can't devote time on...

It's not supported by now?

indeed it seems it's related to the lack of documentation.

On druid 0.23.0 with a single Historical and after setting up replicants to 1 (on retention rules of every datasource) I just keep getting a single warn message for each...

I'm not using this library either but I implemented the same pattern myself and so far the only way I got it working was by defining the factory as a...

I also forgot to mention @citizen-stig that my sample code assumed to be using the vanilla FactoryBoy. Anyways, at first sight, the exception doesn't seem to be related to the...

@philgyford when a fixture needs anothers fixture you just pass them via paremeters so your fixture book_factory should look like this: ```python @pytest.fixture def book_factory(db_session, author_factory): class BookFactory(factory.alchemy.SQLAlchemyModelFactory): class Meta:...

Any news on this? Docker people already [added completions](https://github.com/docker/compose/issues/8550) for the compose plugin (v2 version) but they are simply not working on OhMyZSH. Apparently, completions are generated with `docker completion...

FYI I've opened a separate [bug](https://github.com/ohmyzsh/ohmyzsh/issues/11751) that might be related but strictly refers to the native docker CLI completions and not the OhMyZSH completion provided by plugins for docker/docker-compose