You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
3c6b72b452
When Ansible abnormally shuts down, the broker begins force-disconnecting every context, including those for which connection is currently in-progress. When that happens, .call(init_child) throws ChannelError, and that needs returned back to the worker, assuming the worker still even exists. This solution is incomplete: with sick nodes, it's also possible the worker died naturally, and so the worker should perhaps respond by retrying the connection. Previously, the unhandled ChannelError would spam the console when e.g. fork() began returning EAGAIN. |
6 years ago | |
|---|---|---|
| .github | 6 years ago | |
| .travis | 6 years ago | |
| ansible_mitogen | 6 years ago | |
| docs | 6 years ago | |
| examples | 6 years ago | |
| mitogen | 6 years ago | |
| tests | 6 years ago | |
| .gitignore | 7 years ago | |
| .lgtm.yml | 7 years ago | |
| .travis.yml | 6 years ago | |
| LICENSE | 7 years ago | |
| README.md | 6 years ago | |
| dev_requirements.txt | 6 years ago | |
| preamble_size.py | 6 years ago | |
| run_tests | 6 years ago | |
| setup.cfg | 7 years ago | |
| setup.py | 6 years ago | |
| tox.ini | 7 years ago | |