Skip to content
This repository has been archived by the owner on Nov 25, 2024. It is now read-only.

Updating latest events is sensitive to event ordering #1170

Open
kegsay opened this issue Jun 29, 2020 · 1 comment
Open

Updating latest events is sensitive to event ordering #1170

kegsay opened this issue Jun 29, 2020 · 1 comment
Labels
C-Roomserver T-Task Refactoring, removal, replacement, enabling or disabling functionality, other engineering tasks. X-Needs-Discussion We aren't really sure about this yet so let's talk about it some more

Comments

@kegsay
Copy link
Member

kegsay commented Jun 29, 2020

This may or may not be a problem, but there is no prose to suggest it has been thought about.

calculateLatest which works out forward extremities only looks at the oldLatest then switches them out for new events... if you get events out of order we'll grow the forward extremities indefinitely.

@neilalexander
Copy link
Contributor

In theory we should probably produce some glue events automatically if the number of extremities reaches a certain number, but I don't know if it's really happening in practice anymore — the highest number of forward extremities on d.m.org across all 3600 rooms is 5 apparently.

@kegsay kegsay added X-Needs-Info This issue is blocked awaiting information from the reporter X-Needs-Discussion We aren't really sure about this yet so let's talk about it some more T-Task Refactoring, removal, replacement, enabling or disabling functionality, other engineering tasks. and removed needs investigation X-Needs-Info This issue is blocked awaiting information from the reporter labels Dec 5, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
C-Roomserver T-Task Refactoring, removal, replacement, enabling or disabling functionality, other engineering tasks. X-Needs-Discussion We aren't really sure about this yet so let's talk about it some more
Projects
None yet
Development

No branches or pull requests

2 participants