summary refs log tree commit diff
path: root/tests/federation/test_federation_catch_up.py (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Remove more usages of cursor_to_dict. (#16551)Patrick Cloke2023-10-261-1/+0
| | | Mostly to improve type safety.
* Bump mypy-zope & mypy. (#16188)Patrick Cloke2023-08-291-2/+2
|
* Replace make_awaitable with AsyncMock (#16179)Patrick Cloke2023-08-241-4/+4
| | | | Python 3.8 provides a native AsyncMock, we can replace the homegrown version we have.
* Regularly try to wake up dests instead of waiting for next PDU/EDU (#15743)Mathieu Velten2023-06-161-13/+9
|
* Ensure fed-sender catchup does not block for full state (#15248)David Robertson2023-03-131-1/+86
| | | | * Reproduce bad scenario in test * Avoid catchup optimisation for partial state rooms
* Add final type hint to tests.unittest. (#15072)Patrick Cloke2023-02-141-10/+22
| | | | Adds a return type to HomeServerTestCase.make_homeserver and deal with any variables which are no longer Any.
* Type hints for tests.federation (#14991)David Robertson2023-02-061-21/+31
| | | | | | | | | | | | | * Make tests.federation pass mypy * Untyped defs in tests.federation.transport * test methods return None * Remaining type hints in tests.federation * Changelog * Avoid an uncessary type-ignore
* Modernize unit tests configuration settings for workers. (#14568)realtyem2022-12-011-7/+14
| | | | Use the newer foo_instances configuration instead of the deprecated flags to enable specific features (e.g. start_pushers).
* Remove `HomeServer.get_datastore()` (#12031)Richard van der Hoff2022-02-231-12/+14
| | | | | | | The presence of this method was confusing, and mostly present for backwards compatibility. Let's get rid of it. Part of #11733
* Flatten the synapse.rest.client package (#10600)reivilibre2021-08-171-1/+1
|
* Use mock from the stdlib. (#9772)Patrick Cloke2021-04-091-2/+1
|
* Make federation catchup send last event from any server. (#9640)Erik Johnston2021-03-181-0/+49
| | | | | | | | | | | | | | Currently federation catchup will send the last *local* event that we failed to send to the remote. This can cause issues for large rooms where lots of servers have sent events while the remote server was down, as when it comes back up again it'll be flooded with events from various points in the DAG. Instead, let's make it so that all the servers send the most recent events, even if its not theirs. The remote should deduplicate the events, so there shouldn't be much overhead in doing this. Alternatively, the servers could only send local events if they were also extremities and hope that the other server will send the event over, but that is a bit risky.
* Don't go into federation catch up mode so easily (#9561)Erik Johnston2021-03-151-1/+2
| | | | | | | | | | Federation catch up mode is very inefficient if the number of events that the remote server has missed is small, since handling gaps can be very expensive, c.f. #9492. Instead of going into catch up mode whenever we see an error, we instead do so only if we've backed off from trying the remote for more than an hour (the assumption being that in such a case it is more than a transient failure).
* Catch-up after Federation Outage (bonus): Catch-up on Synapse Startup (#8322)reivilibre2020-09-181-0/+99
| | | | | | | | | | Signed-off-by: Olivier Wilkinson (reivilibre) <olivier@librepush.net> Co-authored-by: Patrick Cloke <clokep@users.noreply.github.com> * Fix _set_destination_retry_timings This came about because the code assumed that retry_interval could not be NULL — which has been challenged by catch-up.
* Catch-up after Federation Outage (split, 4): catch-up loop (#8272)reivilibre2020-09-151-0/+165
|
* Add tests for `last_successful_stream_ordering` (#8258)reivilibre2020-09-071-0/+76
|
* Catch-up after Federation Outage (split, 1) (#8230)reivilibre2020-09-041-0/+82
Signed-off-by: Olivier Wilkinson (reivilibre) <olivier@librepush.net>