diff options
| author | MadLittleMods <MadLittleMods@users.noreply.github.com> | 2022-04-06 21:35:09 +0000 |
|---|---|---|
| committer | MadLittleMods <MadLittleMods@users.noreply.github.com> | 2022-04-06 21:35:09 +0000 |
| commit | fb8eea7ced5c5ad63418729be7170310b9970cd1 (patch) | |
| tree | bf2e6e019e9c434e5c3e2f62759d671bea92f4f8 /develop/print.html | |
| parent | deploy: 6902e9ff2bee4b6e0c2424b88bdac607a2e6b440 (diff) | |
| download | synapse-fb8eea7ced5c5ad63418729be7170310b9970cd1.tar.xz | |
deploy: 350062661cbc402c089ce7a20b72d83073ed8fec
Diffstat (limited to 'develop/print.html')
| -rw-r--r-- | develop/print.html | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/develop/print.html b/develop/print.html index c90ed722d0..5f1a74165e 100644 --- a/develop/print.html +++ b/develop/print.html @@ -14737,7 +14737,8 @@ yet correlated to the DAG.</p> <p>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 -<code>prev_events</code>.</p> +<code>prev_events</code>. Since we don't have the state at any events fetched in that +way, we mark them as outliers.</p> <p>So, typically, we won't have the <code>prev_events</code> of an <code>outlier</code> in the database, (though it's entirely possible that we <em>might</em> have them for some other reason). Other things that make outliers different from regular events:</p> |