Alan Rominger

I couldn't make myself happy with how I was breaking with existing code patterns in the dispatcher, now I think I can be happy with this. The gist of the...

At last I've gotten around to putting up https://github.com/ansible/awx/pull/12586  See the linked PR for a reference.

https://github.com/ansible/awx/pull/12653 now puts up very heavy conflicts with this. It's not solving the same problem, but the same code structures definitely evolve in two different directions in both of these,...

I had to squash commits again in order to rebase, because some intermediate commits had conflicts with devel.

I'm not working to test https://github.com/AlanCoding/awx/pull/48, which is an evolution from https://github.com/ansible/awx/pull/12653 rebased on top of these changes. Much of those changes are non-trivial.

I wanted to be extra sure that merging this doesn't mess anything up. So let me explain some of the testing and where this led me. ### control-standalone This scenario...

Can you find any related logs from around the time it timed out? What information do the API details show at /api/v2/inventory_updates/(id)/?

The proposed solution is that we fix: https://github.com/ansible/ansible-runner/issues/964, which @jbradberry went over in general terms. In addition to this, I believe we should create some dummy files to help us...

The ansible-runner PR is merged, unblocking this. I feel very opinionated about the solution, and this is influenced by some discoveries I made doing the ansible-runner patch. The timestamps are...

@jbradberry facts are written when the gather facts task completes. It is probable that this sometimes occurs less than 2 seconds after the fact_cache is pre-populated by the control machine...