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.
38c0ad1eea
Lots of "invalid handle: ..., 102" messages started appearing during exit recently because ordering changed slightly, and local handles were sent _DEAD even though the broker loop was still progressing through shutdown. The "shutdown" event is too early to close handles: it is the start of the grace period where streams and downstream contexts can finish up any work and deliver buffered data, including FORWARD_LOG messages that haven't arrived yet. So instead, - move the _DEAD logic to the "exit" event, - get rid of Context.on_shutdown() entirely, it's been unused for over a month, - get rid of the "crash" event, since it always fires prior to "exit", and its only use was to send _DEAD to local handles, which now happens during exit anyway. |
8 years ago | |
|---|---|---|
| .travis | 8 years ago | |
| ansible_mitogen | 8 years ago | |
| docs | 8 years ago | |
| examples | 8 years ago | |
| mitogen | 8 years ago | |
| tests | 8 years ago | |
| .gitignore | 8 years ago | |
| .lgtm.yml | 8 years ago | |
| .travis.yml | 8 years ago | |
| LICENSE | 8 years ago | |
| README.md | 8 years ago | |
| dev_requirements.txt | 8 years ago | |
| preamble_size.py | 8 years ago | |
| run_tests | 8 years ago | |
| setup.cfg | 8 years ago | |
| setup.py | 8 years ago | |
| tox.ini | 8 years ago | |