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

Wait for stream change cache position deviceinbox #14286

Conversation

Fizzadar
Copy link
Contributor

@Fizzadar Fizzadar commented Oct 25, 2022

Depends on/builds upon: #14269

Signed off by Nick @ Beeper (@Fizzadar).

Pull Request Checklist

This appears to have previously been done within the room depth handling
and only for local events.
…w IDs

This ensures that every time a new device inbox stream ID is generated
both stream change caches that utilise it are notified of that position,
even if there are no relevant changes at that point.

This ensures that the max position of these caches is always updated to
match the current token, which then makes it possible to wait for changes
to arrive over replication.
Where device inbox message creation is rate limited the next ID call
is still executed, this change exits early when the rate limit has
removed any messages to persist.
@Fizzadar
Copy link
Contributor Author

Fizzadar commented Dec 9, 2022

Closing for now in favour of fixing the lefover races.

@Fizzadar Fizzadar closed this Dec 9, 2022
@Fizzadar Fizzadar deleted the wait-for-stream-change-cache-position-deviceinbox branch January 24, 2023 10:51
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.

1 participant