Matt Davis

@mgorny where are you hearing that? Empirically speaking, Cython 0.29.x has been working flawlessly on 3.12- PyYAML extension builds have been passing the full test suite all along through the...

Yeah, it'd be nice to hold this until after the 2.17 branch, but LGTM

This one is the problem: `-v /tmp/ansible-navigator_qg5o8i3t/:/runner/:Z ` `/runner` is the fallback workdir and homedir for ephemeral users- the container build forces the one in the EE image to be...

Rootless podman assumes host UID == container UID0/GID0, but since we "can't" default the container to `USER root`, permissions on host-shared dirs are problematic. I see a few options: 1)...

This change would also break valid scenarios where relabeling is required, eg where the default target of a `podman-remote` setup or docker client is a remote host with SELinux enabled...

Looks like we need to tweak the check at https://github.com/ansible/ansible/blob/4ff76ffe219b891acf11cf31d994a73303741851/lib/ansible/module_utils/urls.py#L1953 to return a different response than the exception object if its `read` is `None`.

2.9 is no longer supported- can you reproduce this on a currently supported version of Ansible?

Cool, thanks- I've put together a standalone inventory script that roughly matches your description, and definitely see what appears to be some unintended exponential behavior in `ansible-inventory` that isn't occurring...

They're not so much using different code paths as interacting with the same code in wildly different ways. `ansible-inventory` was added (relatively) recently to expose "partially-chewed" inventory data to AWX....

If everything were in collections, it'd be (something close to) that easy, but unfortunately to preserve some of the pre-existing non-collection Jinja plugin load semantics, we have to go back...