From dc7edbdbf03b13ee8e9f8b28b112cee9dee34363 Mon Sep 17 00:00:00 2001 From: Eric Eastwood Date: Thu, 31 Mar 2022 16:59:23 -0500 Subject: [PATCH] Clarify that we mark as outliers because we don't have any state for them As discussed at https://github.com/matrix-org/synapse/pull/12179#discussion_r837263852 --- docs/development/room-dag-concepts.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/development/room-dag-concepts.md b/docs/development/room-dag-concepts.md index 3eb4d5acc463..76709487f802 100644 --- a/docs/development/room-dag-concepts.md +++ b/docs/development/room-dag-concepts.md @@ -39,7 +39,8 @@ yet correlated to the DAG. Outliers typically arise when we fetch the auth chain or state for a given event. When that happens, we just grab the events in the state/auth chain, without calculating the state at those events, or backfilling their -`prev_events`. +`prev_events`. Since we don't have the state at any events fetched in that +way, we mark them as outliers. So, typically, we won't have the `prev_events` of an `outlier` in the database, (though it's entirely possible that we *might* have them for some other