You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 26, 2024. It is now read-only.
Add debug logs to figure out why an event was filtered (#14095)
Spawned while investigating #13944
This way we might get some more context whenever an `403 Forbidden - body: {"errcode":"M_FORBIDDEN","error":"You don't have permission to access that event."}` error is produced.
`log_config.yaml`
```yaml
loggers:
synapse:
level: INFO
synapse.visibility:
level: DEBUG
```
"_check_client_allowed_to_see_event(event=%s): Filtered out event because the user can't see the event because of their membership, membership_result.allowed=%s membership_result.joined=%s",
362
+
event.event_id,
363
+
membership_result.allowed,
364
+
membership_result.joined,
365
+
)
340
366
returnNone
341
367
342
368
# If the sender has been erased and the user was not joined at the time, we
343
369
# must only return the redacted form.
344
370
ifsender_erasedandnotmembership_result.joined:
371
+
logger.debug(
372
+
"_check_client_allowed_to_see_event(event=%s): Returning pruned event because `sender_erased` and the user was not joined at the time",
0 commit comments