Skip to content
This repository was archived by the owner on Apr 26, 2024. It is now read-only.

Commit 3500626

Browse files
Clarify that we mark as outliers because we don't have any state for them (#12345)
As discussed at #12179 (comment)
1 parent f931c06 commit 3500626

File tree

2 files changed

+3
-1
lines changed

2 files changed

+3
-1
lines changed

changelog.d/12345.doc

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
Updates to the Room DAG concepts development document to clarify that we mark events as outliers because we don't have any state for them.

docs/development/room-dag-concepts.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,8 @@ yet correlated to the DAG.
3939
Outliers typically arise when we fetch the auth chain or state for a given
4040
event. When that happens, we just grab the events in the state/auth chain,
4141
without calculating the state at those events, or backfilling their
42-
`prev_events`.
42+
`prev_events`. Since we don't have the state at any events fetched in that
43+
way, we mark them as outliers.
4344

4445
So, typically, we won't have the `prev_events` of an `outlier` in the database,
4546
(though it's entirely possible that we *might* have them for some other

0 commit comments

Comments
 (0)