Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
[ansible] ERROR! [pid ...] mitogen: Router(Broker(...)): no route for Message(..., 102, ...) #305
There is a race condition when starting new contexts relating to the logging package. It manifests as:
It is harmless and will be fixed soon! I'm creating a bug for it so people looking at the tracker will find an entry and an explanation
It is due to logging being activated before the parent stream is added, resulting in racyness depending on whether or not the Broker thread is scheduled (and processes deferred LogHandler calls) before the call to register(). There is a reason for deferring activation, but I can't immediately spot it. Maybe a thinko regarding not having the importer configured before receiving messages?