Pārlūkot izejas kodu

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
tags/v1.57.0rc1
Eric Eastwood pirms 2 gadiem
committed by GitHub
vecāks
revīzija
350062661c
Šim parakstam datu bāzē netika atrasta zināma atslēga GPG atslēgas ID: 4AEE18F83AFDEB23
2 mainītis faili ar 3 papildinājumiem un 1 dzēšanām
  1. +1
    -0
      changelog.d/12345.doc
  2. +2
    -1
      docs/development/room-dag-concepts.md

+ 1
- 0
changelog.d/12345.doc Parādīt failu

@@ -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.

+ 2
- 1
docs/development/room-dag-concepts.md Parādīt failu

@@ -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


Notiek ielāde…
Atcelt
Saglabāt