mirror of
https://github.com/matrix-org/matrix-rust-sdk.git
synced 2026-05-08 07:56:55 -04:00
d78b6826b9
This patch removes everything related to the computation of `ops` from a sliding sync response. With the recent `RoomList`'s client-side sorting project, we no longer need to handle these `ops`. Moreover, the simplified sliding sync specification that is coming removes the `ops`. A `SlidingSyncList` was containing a `rooms` field. It's removed by this patch. Consequently, all the `SlidingSyncList::room_list` and `::room_list_stream` methods are also removed. A `FrozenSlidingSyncList` was containing the `FrozenSlidingSyncRoom`. This patch moves the `FrozenSlidingSyncRoom`s inside `FrozenSlidingSync`. Why is it still correct? We only want to keep the `SlidingSyncRoom::timeline_queue` in the cache for the moment (until the `EventCache` has a persistent storage). Since a `SlidingSyncList` no longer holds any information about the rooms, and since `SlidingSync` itself has all the `SlidingSyncRoom`, this move is natural and still valid. Bye bye all this code :'-).
Matrix SDK integration test
Requirements
This requires a synapse backend with a ci patched configuration. You can easily get
it up and running with docker compose via:
docker compose -f assets/docker-compose.yml up -d
docker compose -f assets/docker-compose.yml logs --tail 100 -f
Note that this works also with podman compose.
Patches
You can see the patches we do to configuration (namely activate registration and
resetting rate limits), check out what assets/ci-start.sh changes.
Running
The integration tests can be run with cargo test or cargo nextest run.
The integration tests expect the environment variables HOMESERVER_URL to be the HTTP URL to
access the synapse server and HOMESERVER_DOMAIN to be set to the domain configured in
that server. If you are using the provided docker-compose.yml, the default will be fine.
Maintenance
To drop the database of your docker compose run:
docker compose -f assets/docker-compose.yml down --volumes