OpenCloud
/
MatrixSynapse
mirror of https://github.com/matrix-org/synapse
1
0
Fork 0
Code Issues Releases Wiki Activity

Clarify that we mark as outliers because we don't have any state for them (#12345) 

As discussed at https://github.com/matrix-org/synapse/pull/12179#discussion_r837263852
pull/12408/head
Eric Eastwood 2022-04-06 16:34:33 -05:00 committed by GitHub
parent f931c0602a
commit 350062661c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
changelog.d/12345.doc Normal file
View File

@ -0,0 +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.

3
docs/development/room-dag-concepts.md
View File

@ -39,7 +39,8 @@ yet correlated to the DAG.
Outliers typically arise when we fetch the auth chain or state for a given 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, event. When that happens, we just grab the events in the state/auth chain,
without calculating the state at those events, or backfilling their 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, 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 (though it's entirely possible that we *might* have them for some other