Alex Willmer

Spoke too soon, It's back https://github.com/mitogen-hq/mitogen/actions/runs/12116635990/job/33777406222

Judging by https://github.com/mitogen-hq/mitogen/actions/runs/12117305356/job/33779477126 I don't think there's a pattern wrt to Ansible versions or Python versions. So it's probably something non-deterministic such as a race condition.

It's baaaaaack https://github.com/mitogen-hq/mitogen/actions/runs/12237211642/job/34139694093?pr=1200

Possibly related to tickets #680, #712, #745, & #749 - they mention "errno 11", which is EAGAIN/EWOULDBLOCK on Linux.

Again https://github.com/mitogen-hq/mitogen/actions/runs/18906830627/job/53967000783 ``` TASK [Fetch /tmp/512mb.zero src=/tmp/512mb.zero, dest=/tmp/fetch-{{ inventory_hostname }}-512mb.zero, flat=True] *** Wednesday 29 October 2025 11:51:41 +0000 (0:00:04.122) 0:00:36.706 ***** Error: : [mux 7705] 11:51:48.700045 E mitogen: crashed Traceback...

> To avoid confusion, we recommend using unicode_literals everywhere across a code-base or not at all, instead of turning on for only some modules. -- https://python-future.org/unicode_literals.html

> builtin: > ```python > myenum = type('Enum', (), enum) > ``` > (slightly esotic) doesn't work with `unicode_literals`: `type()` expects a string. -- https://stackoverflow.com/questions/809796/any-gotchas-using-unicode-literals-in-python-2-6

> I am beginning to think that `from __future__ import unicode_literals` does more harm than good. I don't recall exactly why we introduced it, but with the restoration of `u""`...

> `AttributeError: type object 'Connection' has no attribute '_create_control_path'` Error in the initial report. Ansible 2.6.2, Python 2.7.15, Mitogen unclear. > `AttributeError: 'Connection' object has no attribute 'delegate_to_hostname'` Error reported...

This may be fixed by v0.3.21, which includes #1215.