|
|
|
|
# Blacklisted due to flakiness
|
|
|
|
|
Remote users can join room by alias
|
|
|
|
|
|
|
|
|
|
# Blacklisted due to flakiness
|
|
|
|
|
POST /login can log in as a user with just the local part of the id
|
|
|
|
|
|
|
|
|
|
# Blacklisted due to flakiness
|
|
|
|
|
avatar_url updates affect room member events
|
|
|
|
|
|
|
|
|
|
# Blacklisted due to flakiness
|
|
|
|
|
displayname updates affect room member events
|
|
|
|
|
|
|
|
|
|
# Blacklisted due to flakiness
|
|
|
|
|
Room members can override their displayname on a room-specific basis
|
|
|
|
|
|
|
|
|
|
# Blacklisted due to flakiness
|
|
|
|
|
Alias creators can delete alias with no ops
|
|
|
|
|
|
|
|
|
|
# Blacklisted because matrix-org/dendrite#847 might have broken it but we're not
|
|
|
|
|
# really sure and we need it pretty badly anyway
|
|
|
|
|
Real non-joined users can get individual state for world_readable rooms after leaving
|
|
|
|
|
|
|
|
|
|
# Blacklisted until matrix-org/dendrite#862 is reverted due to Riot bug
|
|
|
|
|
Latest account data appears in v2 /sync
|
|
|
|
|
|
|
|
|
|
# Blacklisted due to flakiness
|
|
|
|
|
Outbound federation can backfill events
|
|
|
|
|
|
|
|
|
|
# Blacklisted due to alias work on Synapse
|
|
|
|
|
Alias creators can delete canonical alias with no ops
|
|
|
|
|
|
|
|
|
|
# Blacklisted because we need to implement v2 invite endpoints for room versions
|
|
|
|
|
# to be supported (currently fails with M_UNSUPPORTED_ROOM_VERSION)
|
Federation for v3/v4 rooms (#954)
* Update gomatrixserverlib
* Default to room version 4
* Update gomatrixserverlib
* Limit prev_events and auth_events
* Fix auth_events, prev_events
* Fix linter issues
* Update gomatrixserverlib
* Fix getState
* Update sytest-whitelist
* Squashed commit of the following:
commit 067b87506357c996fd6ddb11271db9469ad4ce80
Author: Neil Alexander <neilalexander@users.noreply.github.com>
Date: Fri Apr 3 14:29:06 2020 +0100
Invites v2 endpoint (#952)
* Start converting v1 invite endpoint to v2
* Update gomatrixserverlib
* Early federationsender code for sending invites
* Sending invites sorta happens now
* Populate invite request with stripped state
* Remodel a bit, don't reflect received invites
* Handle invite_room_state
* Handle room versions a bit better
* Update gomatrixserverlib
* Tweak order in destinationQueue.next
* Revert check in processMessage
* Tweak federation sender destination queue code a bit
* Add comments
commit 955244c09298d0e6c870377dad3af2ffa1f5e578
Author: Ben B <benne@klimlive.de>
Date: Fri Apr 3 12:40:50 2020 +0200
use custom http client instead of the http DefaultClient (#823)
This commit replaces the default client from the http lib with a custom one.
The previously used default client doesn't come with a timeout. This could cause
unwanted locks.
That solution chosen here creates a http client in the base component dendrite
with a constant timeout of 30 seconds. If it should be necessary to overwrite
this, we could include the timeout in the dendrite configuration.
Here it would be a good idea to extend the type "Address" by a timeout and
create an http client for each service.
Closes #820
Signed-off-by: Benedikt Bongartz <benne@klimlive.de>
Co-authored-by: Kegsay <kegan@matrix.org>
* Update sytest-whitelist, sytest-blacklist
* Update go.mod/go.sum
* Add some error wrapping for debug
* Add a NOTSPEC to common/events.go
* Perform state resolution at send_join
* Set default room version to v2 again
* Tweak GetCapabilities
* Add comments to ResolveConflictsAdhoc
* Update sytest-blacklist
* go mod tidy
* Update sytest-whitelist, sytest-blacklist
* Update versions
* Updates from review comments
* Update sytest-blacklist, sytest-whitelist
* Check room versions compatible at make_join, add some comments, update gomatrixserverlib, other tweaks
* Set default room version back to v2
* Update gomatrixserverlib, sytest-whitelist
4 years ago
|
|
|
Inbound federation rejects invites which are not signed by the sender
|
|
|
|
|
|
|
|
|
|
# Blacklisted because we don't support ignores yet
|
|
|
|
|
Ignore invite in incremental sync
|
|
|
|
|
|
|
|
|
|
# Blacklisted because this test calls /r0/events which we don't implement
|
|
|
|
|
New room members see their own join event
|
|
|
|
|
Existing members see new members' join events
|
Send-to-device support (#1072)
* Groundwork for send-to-device messaging
* Update sample config
* Add unstable routing for now
* Send to device consumer in sync API
* Start the send-to-device consumer
* fix indentation in dendrite-config.yaml
* Create send-to-device database tables, other tweaks
* Add some logic for send-to-device messages, add them into sync stream
* Handle incoming send-to-device messages, count them with EDU stream pos
* Undo changes to test
* pq.Array
* Fix sync
* Logging
* Fix a couple of transaction things, fix client API
* Add send-to-device test, hopefully fix bugs
* Comments
* Refactor a bit
* Fix schema
* Fix queries
* Debug logging
* Fix storing and retrieving of send-to-device messages
* Try to avoid database locks
* Update sync position
* Use latest sync position
* Jiggle about sync a bit
* Fix tests
* Break out the retrieval from the update/delete behaviour
* Comments
* nolint on getResponseWithPDUsForCompleteSync
* Try to line up sync tokens again
* Implement wildcard
* Add all send-to-device tests to whitelist, what could possibly go wrong?
* Only care about wildcard when targeted locally
* Deduplicate transactions
* Handle tokens properly, return immediately if waiting send-to-device messages
* Fix sync
* Update sytest-whitelist
* Fix copyright notice (need to do more of this)
* Comments, copyrights
* Return errors from Do, fix dendritejs
* Review comments
* Comments
* Constructor for TransactionWriter
* defletions
* Update gomatrixserverlib, sytest-blacklist
4 years ago
|
|
|
|
|
|
|
|
# See https://github.com/matrix-org/sytest/pull/901
|
|
|
|
|
Remote invited user can see room metadata
|
|
|
|
|
|
|
|
|
|
# We don't implement soft-failed events yet, but because the /send response is vague,
|
|
|
|
|
# this test thinks it's all fine...
|
|
|
|
|
Inbound federation accepts a second soft-failed event
|
|
|
|
|
|
|
|
|
|
# Relies on a rejected PL event which will never be accepted into the DAG
|
|
|
|
|
# Caused by https://github.com/matrix-org/sytest/pull/911
|
|
|
|
|
Outbound federation requests missing prev_events and then asks for /state_ids and resolves the state
|
|
|
|
|
|
|
|
|
|
# We don't implement lazy membership loading yet.
|
|
|
|
|
The only membership state included in a gapped incremental sync is for senders in the timeline
|
|
|
|
|
|
|
|
|
|
# Blacklisted out of flakiness after #1479
|
|
|
|
|
Invited user can reject local invite after originator leaves
|
|
|
|
|
Invited user can reject invite for empty room
|
|
|
|
|
If user leaves room, remote user changes device and rejoins we see update in /sync and /keys/changes
|
|
|
|
|
|
|
|
|
|
# Blacklisted due to flakiness
|
|
|
|
|
A prev_batch token from incremental sync can be used in the v1 messages API
|
|
|
|
|
|
|
|
|
|
# Blacklisted due to flakiness
|
|
|
|
|
Forgotten room messages cannot be paginated
|
|
|
|
|
|
|
|
|
|
# Blacklisted due to flakiness
|
|
|
|
|
Can re-join room if re-invited
|
|
|
|
|
|
|
|
|
|
# Blacklisted due to flakiness after #1774
|
|
|
|
|
Local device key changes get to remote servers with correct prev_id
|
|
|
|
|
|
|
|
|
|
# Flakey
|
|
|
|
|
Local device key changes appear in /keys/changes
|
