Skip to content
This repository was archived by the owner on Apr 26, 2024. It is now read-only.

During room intial sync, only calculate current state once.#56

Merged
NegativeMjark merged 1 commit intodevelopfrom
room_initial_sync_perf
Feb 9, 2015
Merged

During room intial sync, only calculate current state once.#56
NegativeMjark merged 1 commit intodevelopfrom
room_initial_sync_perf

Conversation

@erikjohnston
Copy link
Member

No description provided.

@NegativeMjark
Copy link
Contributor

LGTM

NegativeMjark added a commit that referenced this pull request Feb 9, 2015
During room intial sync, only calculate current state once.
@NegativeMjark NegativeMjark merged commit 5c5f5c1 into develop Feb 9, 2015
@erikjohnston erikjohnston deleted the room_initial_sync_perf branch February 11, 2015 10:41
babolivier added a commit that referenced this pull request Sep 1, 2021
…r_id

Revert "Remove "user_id" from GET /presence. (#7606)"
Fizzadar added a commit to Fizzadar/synapse that referenced this pull request Feb 20, 2023
…rg#56)

* Update Beeper preview query to correctly handle edit events

We first want to ignore edit events from potential preview events as
these often replace events further back in history but come mots recent
on order.

We then do a second join for edit events that replace the selected (non
edit) preview event, and use where present, meaning edits on the latest
preview event show correctly.

* Rewrite preview query edit handling

* Fix join events w/relations

* Add preview edits test case

* Expand preview edit test to cover multiple edits

* Only generate previews if we have timeline events

* Remove cache on preview generation

Points towards there still being cache invalidation races somewhere...

Co-authored-by: Brad Murray <bradtgmurray@gmail.com>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants