mirror of https://github.com/matrix-org/matrix-rust-sdk.git synced 2026-04-27 10:39:25 -04:00

Files

Benjamin Bouvier d72fd34325 Make pending local echoes sticky, take 2 (#2189 )

* ui: Move EventSendState into timeline::event_item::local module

* [WIP] ui: Make pending local echoes stick to the bottom of the timeline

* test: update more test expectations

* chore: tweak comment to slightly better reflect reality

* nit: remove else after return

* fix: the item's insert position is insert_idx, not `items.len()` anymore

* fix: look for remote echo before local echo when processing send state

Previous code assumed that the latest timeline items would be the most recent, and that
if there was a remote echo, it would always be after the local echo, because of that.
That's not the case anymore, so we must look for possibly a remote echo first, and then
if we find it, apply the late update process.

Also, there might remain a day divider added by the local echo, if it were inserted last.
I'm not sure it covers all the cases, but I've now made it so that the day divider is removed
if it was the last element.

* feat: switch strategy; keep on pushing if there's nothing in the timeline yet

* Revert "test: update more test expectations"

This reverts commit 400cc93ba7c98042a28b5e8d5042899e854f6cff.

* test: reset test expectations

* Address review comments

* fix: don't mix up latest event with any status, with latest non-failed event index

---------

Co-authored-by: Jonas Platte <jplatte@matrix.org>

2023-06-30 09:37:49 +00:00

assets

chore: Use fully-qualified Docker image names

2023-02-14 10:19:06 +01:00

src

Make pending local echoes sticky, take 2 (#2189 )

2023-06-30 09:37:49 +00:00

Cargo.toml

ui: Add local echoes for reactions to Timeline

2023-06-26 15:17:48 +00:00

README.md

Fix a typo in the integration tests readme

2023-03-06 09:29:23 +01:00

README.md

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

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, the default will be fine.

Maintenance

To drop the database of your docker-compose run:

docker-compose -f assets/docker-compose.yml stop
docker volume rm -f assets_matrix-rust-sdk-ci-data

or simply:

docker-compose -f assets/docker-compose.yml down -v