Mirrors
/
synapse-old
mirror of https://github.com/matrix-org/synapse.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

deploy: 350062661c

This commit is contained in:
MadLittleMods 2022-04-06 21:35:09 +00:00
parent db3b2588bc
commit fb8eea7ced
4 changed files with 6 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
develop/development/room-dag-concepts.html
View File

@ -176,7 +176,8 @@ yet correlated to the DAG.</p>
<p>Outliers typically arise when we fetch the auth chain or state for a given <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, 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
<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, <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 (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> reason). Other things that make outliers different from regular events:</p>

3
develop/print.html
View File

@ -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 <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, 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
<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, <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 (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> reason). Other things that make outliers different from regular events:</p>

2
develop/searchindex.js
View File

File diff suppressed because one or more lines are too long

2
develop/searchindex.json
View File

File diff suppressed because one or more lines are too long