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 | |
|---|---|---|
| .. | ||
| _static | 8 years ago | |
| _templates | 8 years ago | |
| images | 8 years ago | |
| .gitignore | 8 years ago | |
| Makefile | 8 years ago | |
| ansible.rst | 8 years ago | |
| api.rst | 8 years ago | |
| compared.rst | 8 years ago | |
| conf.py | 8 years ago | |
| docs-requirements.txt | 8 years ago | |
| examples.rst | 8 years ago | |
| getting_started.rst | 8 years ago | |
| howitworks.rst | 8 years ago | |
| index.rst | 8 years ago | |
| internals.rst | 8 years ago | |
| pickle-substitutes.ods | 8 years ago | |
| services.rst | 8 years ago | |
| shame.rst | 8 years ago | |
| signals.rst | 8 years ago | |
| toc.rst | 8 years ago | |