This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Backfilled events marked as outliers break backfill #8894
Comments
@anoadragon453 Any chance you have a stack trace for this? |
The stack trace is quite unhelpful:
However you can see a little bit of surrounding logs and other metadata at https://sentry.matrix.org/sentry/synapse-modular/issues/194313/ and https://sentry.matrix.org/sentry/synapse-modular/issues/194314/ (for those that have access). |
Deferring for now, as one of our quarterly goals is to tame our Sentry alert rate, we should return to this in due course. |
richvdh
added
S-Major
Major functionality / product severely impaired, no satisfactory workaround.
T-Defect
Bugs, crashes, hangs, security vulnerabilities, or other reported issues.
and removed
z-bug
(Deprecated Label)
z-info-needed
labels
Apr 9, 2021
Looks like this was introduced in #8350. |
richvdh
added a commit
that referenced
this issue
Dec 22, 2021
Events returned by `backfill` should not be flagged as outliers. Fixes: ``` AssertionError: null File "synapse/handlers/federation.py", line 313, in try_backfill dom, room_id, limit=100, extremities=extremities File "synapse/handlers/federation_event.py", line 517, in backfill await self._process_pulled_events(dest, events, backfilled=True) File "synapse/handlers/federation_event.py", line 642, in _process_pulled_events await self._process_pulled_event(origin, ev, backfilled=backfilled) File "synapse/handlers/federation_event.py", line 669, in _process_pulled_event assert not event.internal_metadata.is_outlier() ``` See https://sentry.matrix.org/sentry/synapse-matrixorg/issues/231992 Fixes #8894.
richvdh
added a commit
that referenced
this issue
Jan 4, 2022
Events returned by `backfill` should not be flagged as outliers. Fixes: ``` AssertionError: null File "synapse/handlers/federation.py", line 313, in try_backfill dom, room_id, limit=100, extremities=extremities File "synapse/handlers/federation_event.py", line 517, in backfill await self._process_pulled_events(dest, events, backfilled=True) File "synapse/handlers/federation_event.py", line 642, in _process_pulled_events await self._process_pulled_event(origin, ev, backfilled=backfilled) File "synapse/handlers/federation_event.py", line 669, in _process_pulled_event assert not event.internal_metadata.is_outlier() ``` See https://sentry.matrix.org/sentry/synapse-matrixorg/issues/231992 Fixes #8894.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
A homeserver backfilling from another homeserver was found to be raising an
AssertionError
at:synapse/synapse/handlers/federation.py
Lines 921 to 923 in 30fba62
It's currently unclear which event is problematic and why it might be marked as an outlier. The logs of the backfilling server also contained many instances of event signature validation failures. This was due to a remote server changing their signing key without also changing the key ID (or putting the old key in
old_signing_keys
). This may be a red herring however.The
assert
and a similar assert at:synapse/synapse/handlers/federation.py
Lines 891 to 894 in 30fba62
both do not give any information about the failing event.
Thus the first step is to improve these assert statements and figure out why these backfilled events are marked as outliers. After that, we may want to make the backfill code drop these events instead of simple raising, similar to what was done in #8350.
The text was updated successfully, but these errors were encountered: