| Commit message (Collapse) | Author | Files | Lines |
|
|
|
It turned out that merely configuring the root logger is not enough for
"catch-all" semantics. The logging subsystem also needs to be told not
to disable existing loggers (so that their messages will get propagated
to handlers up the logging hierarchy, not just silently discarded).
Signed-off-by: Ivan Shapovalov <intelfx100@gmail.com>
|
|
|
|
|
|
|
|
|
|
ujson.loads
|
|
in sytest
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
event_forward_extremities
|
|
|
|
it is cached
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
as it might work better than iterating over the top level dict
|
|
|
|
|
|
|
|
|
|
|
|
|
|
they are notified in
|
|
|
|
|
|
the pending events by the correct room_stream_id
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
string in on_new_user_event
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
hasn't advanced for that source
|
|
index only scan
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
the event
|
|
|
|
|
|
|
|
|
|
|
|
|
|
client gets duplicate events
|
|
from the main thread after the transaction completes, not from database thread before the transaction completes.
|
|
|
|
|
|
source whether we want a token for going 'forwards' or 'backwards'
|
|
|
|
|
|
|
|
|