Bas Zoetekouw

I'm also seeing this error (with current master polybar and version 4.16 of i3). Any combination of `wm-restack=i3` and `override-redirect=true` as suggested above don't solve the issue for me, however,...

I'm trying to look into this. The issue seems to be caused by the introduction of the module_respawn API in ansible in commit [4c5ce5a1a9e79a845aff4978cfeb72a0d4ecf7d6](https://github.com/ansible/ansible/commit/4c5ce5a1a9e79a845aff4978cfeb72a0d4ecf7d6#diff-5eee1653543542a8b7daf91a0911fe2620ec2b03bb77aa7e610404430be67229), an in particular by the change...

@phemmer What exactly have you inserted there? This code doesn't even seem to be called when running a module such as apt (at least, putting a generic exception there had...

@mhenniges I think the situation you describe is correct, but it still should be supported by mitogen, I think. I don't think it is hard to solve (you need to...

I think you are missing the point of this bug; sure, I'd be nice to have a workaround by setting the python interpreter to a different binary, but that still...

I'm not sure what has happened, but eveything now Just Work with ansible-core 2.12.2 and mitogen 0.3.2.

@temoto is there anything I can do to help get this bug fixed? It's rather annoyingly breaking our MySQL and Redis TLS connections. Would you appreciate a PR to make...

Same issue here. Worked perfectly in 2023.3, but after upgrade tot 2023.6 this issue started occurring.

Never mind, my issue was due to a broken serial cable. Replaced the cable, issue was gone.

This seems to be fixed in devel already