From be2eae9d228193320cd8a4fa696505c6efb6772c Mon Sep 17 00:00:00 2001 From: squahtx Date: Tue, 7 Dec 2021 16:19:22 +0000 Subject: deploy: 26b5d2320f62b5eb6262c7614fbdfc364a4dfc02 --- latest/development/cas.html | 2 +- latest/development/contributing_guide.html | 6 +++--- latest/development/database_schema.html | 2 +- latest/development/experimental_features.html | 2 +- latest/development/git.html | 2 +- latest/development/internal_documentation/index.html | 2 +- latest/development/room-dag-concepts.html | 17 ++++++++--------- latest/development/saml.html | 2 +- latest/development/url_previews.html | 2 +- 9 files changed, 18 insertions(+), 19 deletions(-) (limited to 'latest/development') diff --git a/latest/development/cas.html b/latest/development/cas.html index 896e2756a5..e72fed5ab8 100644 --- a/latest/development/cas.html +++ b/latest/development/cas.html @@ -99,7 +99,7 @@ - IntroductionWelcome and OverviewSetupInstallationUsing PostgresConfiguring a Reverse ProxyConfiguring a Forward/Outbound ProxyConfiguring a Turn ServerDelegationUpgradingUpgrading between Synapse VersionsUpgrading from pre-Synapse 1.0UsageFederationConfigurationHomeserver Sample Config FileLogging Sample Config FileStructured LoggingTemplatesUser AuthenticationSingle-Sign OnOpenID ConnectSAMLCASSSO Mapping ProvidersPassword Auth ProvidersJSON Web TokensRegistration CaptchaApplication ServicesServer NoticesConsent TrackingURL PreviewsUser DirectoryMessage Retention PoliciesPluggable ModulesWriting a moduleSpam checker callbacksThird-party rules callbacksPresence router callbacksAccount validity callbacksPassword auth provider callbacksPorting a legacy module to the new interfaceWorkersUsing synctl with WorkersSystemdAdministrationAdmin APIAccount ValidityBackground UpdatesDelete GroupEvent ReportsMediaPurge HistoryRegister UsersRegistration TokensManipulate Room MembershipRoomsServer NoticesStatisticsUsersServer VersionManholeMonitoringRequest log formatScriptsDevelopmentContributing GuideCode StyleGit UsageTestingOpenTracingDatabase SchemasExperimental featuresSynapse ArchitectureLog ContextsReplicationTCP ReplicationInternal DocumentationSingle Sign-OnSAMLCASRoom DAG conceptsState ResolutionThe Auth Chain Difference AlgorithmMedia RepositoryRoom and User StatisticsScriptsOtherDependency Deprecation Policy + IntroductionWelcome and OverviewSetupInstallationUsing PostgresConfiguring a Reverse ProxyConfiguring a Forward/Outbound ProxyConfiguring a Turn ServerDelegationUpgradingUpgrading between Synapse VersionsUpgrading from pre-Synapse 1.0UsageFederationConfigurationHomeserver Sample Config FileLogging Sample Config FileStructured LoggingTemplatesUser AuthenticationSingle-Sign OnOpenID ConnectSAMLCASSSO Mapping ProvidersPassword Auth ProvidersJSON Web TokensRegistration CaptchaApplication ServicesServer NoticesConsent TrackingURL PreviewsUser DirectoryMessage Retention PoliciesPluggable ModulesWriting a moduleSpam checker callbacksThird-party rules callbacksPresence router callbacksAccount validity callbacksPassword auth provider callbacksBackground update controller callbacksPorting a legacy module to the new interfaceWorkersUsing synctl with WorkersSystemdAdministrationAdmin APIAccount ValidityBackground UpdatesDelete GroupEvent ReportsMediaPurge HistoryRegister UsersRegistration TokensManipulate Room MembershipRoomsServer NoticesStatisticsUsersServer VersionFederationManholeMonitoringUnderstanding Synapse Through Grafana GraphsUseful SQL for AdminsDatabase Maintenance ToolsState GroupsRequest log formatAdmin FAQScriptsDevelopmentContributing GuideCode StyleGit UsageTestingOpenTracingDatabase SchemasExperimental featuresSynapse ArchitectureLog ContextsReplicationTCP ReplicationInternal DocumentationSingle Sign-OnSAMLCASRoom DAG conceptsState ResolutionThe Auth Chain Difference AlgorithmMedia RepositoryRoom and User StatisticsScriptsOtherDependency Deprecation PolicyRunning Synapse on a Single-Board Computer diff --git a/latest/development/contributing_guide.html b/latest/development/contributing_guide.html index 9439edb8f3..9fa46d9014 100644 --- a/latest/development/contributing_guide.html +++ b/latest/development/contributing_guide.html @@ -99,7 +99,7 @@ - IntroductionWelcome and OverviewSetupInstallationUsing PostgresConfiguring a Reverse ProxyConfiguring a Forward/Outbound ProxyConfiguring a Turn ServerDelegationUpgradingUpgrading between Synapse VersionsUpgrading from pre-Synapse 1.0UsageFederationConfigurationHomeserver Sample Config FileLogging Sample Config FileStructured LoggingTemplatesUser AuthenticationSingle-Sign OnOpenID ConnectSAMLCASSSO Mapping ProvidersPassword Auth ProvidersJSON Web TokensRegistration CaptchaApplication ServicesServer NoticesConsent TrackingURL PreviewsUser DirectoryMessage Retention PoliciesPluggable ModulesWriting a moduleSpam checker callbacksThird-party rules callbacksPresence router callbacksAccount validity callbacksPassword auth provider callbacksPorting a legacy module to the new interfaceWorkersUsing synctl with WorkersSystemdAdministrationAdmin APIAccount ValidityBackground UpdatesDelete GroupEvent ReportsMediaPurge HistoryRegister UsersRegistration TokensManipulate Room MembershipRoomsServer NoticesStatisticsUsersServer VersionManholeMonitoringRequest log formatScriptsDevelopmentContributing GuideCode StyleGit UsageTestingOpenTracingDatabase SchemasExperimental featuresSynapse ArchitectureLog ContextsReplicationTCP ReplicationInternal DocumentationSingle Sign-OnSAMLCASRoom DAG conceptsState ResolutionThe Auth Chain Difference AlgorithmMedia RepositoryRoom and User StatisticsScriptsOtherDependency Deprecation Policy + IntroductionWelcome and OverviewSetupInstallationUsing PostgresConfiguring a Reverse ProxyConfiguring a Forward/Outbound ProxyConfiguring a Turn ServerDelegationUpgradingUpgrading between Synapse VersionsUpgrading from pre-Synapse 1.0UsageFederationConfigurationHomeserver Sample Config FileLogging Sample Config FileStructured LoggingTemplatesUser AuthenticationSingle-Sign OnOpenID ConnectSAMLCASSSO Mapping ProvidersPassword Auth ProvidersJSON Web TokensRegistration CaptchaApplication ServicesServer NoticesConsent TrackingURL PreviewsUser DirectoryMessage Retention PoliciesPluggable ModulesWriting a moduleSpam checker callbacksThird-party rules callbacksPresence router callbacksAccount validity callbacksPassword auth provider callbacksBackground update controller callbacksPorting a legacy module to the new interfaceWorkersUsing synctl with WorkersSystemdAdministrationAdmin APIAccount ValidityBackground UpdatesDelete GroupEvent ReportsMediaPurge HistoryRegister UsersRegistration TokensManipulate Room MembershipRoomsServer NoticesStatisticsUsersServer VersionFederationManholeMonitoringUnderstanding Synapse Through Grafana GraphsUseful SQL for AdminsDatabase Maintenance ToolsState GroupsRequest log formatAdmin FAQScriptsDevelopmentContributing GuideCode StyleGit UsageTestingOpenTracingDatabase SchemasExperimental featuresSynapse ArchitectureLog ContextsReplicationTCP ReplicationInternal DocumentationSingle Sign-OnSAMLCASRoom DAG conceptsState ResolutionThe Auth Chain Difference AlgorithmMedia RepositoryRoom and User StatisticsScriptsOtherDependency Deprecation PolicyRunning Synapse on a Single-Board Computer @@ -537,7 +537,7 @@ do!
Most-recent-in-time events in the DAG which are not referenced by any other events' prev_events yet.
prev_events
The forward extremities of a room are used as the prev_events when the next event is sent.
The current marker of where we have backfilled up to and will generally be the -oldest-in-time events we know of in the DAG.
This is an event where we haven't fetched all of the prev_events for.
Once we have fetched all of its prev_events, it's unmarked as a backwards -extremity (although we may have formed new backwards extremities from the prev -events during the backfilling process).
When we persist a non-outlier event, we clear it as a backward extremity and set +all of its prev_events as the new backward extremities if they aren't already +persisted in the events table.
events
We mark an event as an outlier when we haven't figured out the state for the room at that point in the DAG yet.
outlier
We won't necessarily have the prev_events of an outlier in the database, -but it's entirely possible that we might. The status of whether we have all of -the prev_events is marked as a backwards extremity.
For example, when we fetch the event auth chain or state for a given event, we mark all of those claimed auth events as outliers because we haven't done the state calculation ourself.