forked from MirrorHub/synapse
Use `PreserveLoggingContext()` to ensure that logging contexts are not lost when exiting a read/write lock. When exiting a read/write lock, callbacks on a `Deferred` are triggered as a signal to any waiting coroutines. Any waiting coroutine that becomes runnable is likely to follow the Synapse logging context rules and will restore its own logging context, then either run to completion or await another `Deferred`, resetting the logging context in the process.
2 lines
84 B
Plaintext
2 lines
84 B
Plaintext
Fix a long-standing bug where `ReadWriteLock`s could drop logging contexts on exit.
|