Mitogen issues in AWX when used verbosity 3 and higher #400
Comments
It looks like 2 issues here:
Please leave this with me and I'll try to setup a reproduction shortly. |
Re: your offer to supply a public AWX instance, that would be immensely useful! Sorry, just digging through old chat history and noticed you message. :) |
I've spotted the bug in AWX at least. Going to open a PR for that to begin with. |
The pull request is here: ansible/awx#2565 Allow me a few hours to think about a workaround I can include in Mitogen, but it looks like potentially it would have to be a monkeypatch. |
Hi there, I have checked in a workaround for the issue on I left the worker you supplied unpatched, so dropping the |
Thanks a ton for reporting this! The workaround on master solves the problem, and hopefully future versions of AWX will include the PR I sent. This is now on the master branch and will make it into the next release. To be updated when a new release is made, subscribe to https://networkgenomics.com/mail/mitogen-announce/ Thanks for reporting this! |
- extra minify tests - more inline docs migration - issue #400
Mitogen is configured to be used in AWX. Version of mitogen: 0.2.2, AWX: 2.0.0
When used verbosity 0 (Normal), 1 (Verbose) or 2 (More verbose) everything works as expected.
When used verbosity 3 (Debug), or 4 (Connection Debug) template runs "forever" with output
Steps to reproduce:
The text was updated successfully, but these errors were encountered: