Eric Eastwood 408a05ebbc Fix potential lost logcontext when PerDestinationQueue.shutdown(...) (#19178) ... Spawning from looking at the logs in https://github.com/element-hq/synapse/issues/19165#issuecomment-3527452941 which mention the `federation_transaction_transmission_loop`. I don't think it's the source of the lost logcontext that person in the issue is experiencing because this only applies when you try to `shutdown` the homeserver. Problem code introduced in https://github.com/element-hq/synapse/pull/18828 To explain the fix, see the [*Deferred callbacks*](3b59ac3b69/docs/log_contexts.md (deferred-callbacks)) section of our logcontext docs for more info (specifically using solution 2).		2025-11-13 15:17:15 -06:00
..
sender	Fix potential lost logcontext when PerDestinationQueue.shutdown(...) (#19178)	2025-11-13 15:17:15 -06:00
transport	Write union types as X | Y where possible (#19111)	2025-11-06 14:02:33 -06:00
__init__.py	Format files with Ruff (#17643)	2024-09-02 12:39:04 +01:00
federation_base.py	Write union types as X | Y where possible (#19111)	2025-11-06 14:02:33 -06:00
federation_client.py	Write union types as X | Y where possible (#19111)	2025-11-06 14:02:33 -06:00
federation_server.py	Write union types as X | Y where possible (#19111)	2025-11-06 14:02:33 -06:00
persistence.py	Write union types as X | Y where possible (#19111)	2025-11-06 14:02:33 -06:00
send_queue.py	Write union types as X | Y where possible (#19111)	2025-11-06 14:02:33 -06:00
units.py	Write union types as X | Y where possible (#19111)	2025-11-06 14:02:33 -06:00