Skip to content
Snippets Groups Projects
  1. Dec 30, 2020
    • Andrew Morgan's avatar
      Fix RoomDirectoryFederationTests and make them actually run (#8998) · 168ba00d
      Andrew Morgan authored
      The `RoomDirectoryFederationTests` tests were not being run unless explicitly called as an `__init__.py` file was not present in `tests/federation/transport/`. Thus the folder was not a python module, and `trial` did not look inside for any test cases to run. This was found while working on #6739.
      
      This PR adds a `__init__.py` and also fixes the test in a couple ways:
      
      - Switch to subclassing `unittest.FederatingHomeserverTestCase` instead, which sets up federation endpoints for us.
      - Supply a `federation_auth_origin` to `make_request` in order to more act like the request is coming from another server, instead of just an unauthenicated client requesting a federation endpoint.
      
      I found that the second point makes no difference to the test passing, but felt like the right thing to do if we're testing over federation.
      168ba00d
  2. Dec 15, 2020
  3. Nov 16, 2020
  4. Sep 18, 2020
  5. Sep 15, 2020
  6. Sep 10, 2020
  7. Sep 08, 2020
  8. Sep 07, 2020
  9. Sep 04, 2020
  10. Aug 27, 2020
  11. Aug 13, 2020
  12. Jul 30, 2020
  13. Jul 28, 2020
  14. Jul 24, 2020
  15. Jun 10, 2020
  16. Jun 04, 2020
  17. May 22, 2020
    • Erik Johnston's avatar
      Add ability to wait for replication streams (#7542) · 1531b214
      Erik Johnston authored
      The idea here is that if an instance persists an event via the replication HTTP API it can return before we receive that event over replication, which can lead to races where code assumes that persisting an event immediately updates various caches (e.g. current state of the room).
      
      Most of Synapse doesn't hit such races, so we don't do the waiting automagically, instead we do so where necessary to avoid unnecessary delays. We may decide to change our minds here if it turns out there are a lot of subtle races going on.
      
      People probably want to look at this commit by commit.
      1531b214
  18. Apr 03, 2020
    • Richard van der Hoff's avatar
      Fix device list update stream ids going backward (#7158) · daa1ac89
      Richard van der Hoff authored
      Occasionally we could get a federation device list update transaction which
      looked like:
      
      ```
      [
          {'edu_type': 'm.device_list_update', 'content': {'user_id': '@user:test', 'device_id': 'D2', 'prev_id': [], 'stream_id': 12, 'deleted': True}},
          {'edu_type': 'm.device_list_update', 'content': {'user_id': '@user:test', 'device_id': 'D1', 'prev_id': [12], 'stream_id': 11, 'deleted': True}},
          {'edu_type': 'm.device_list_update', 'content': {'user_id': '@user:test', 'device_id': 'D3', 'prev_id': [11], 'stream_id': 13, 'deleted': True}}
      ]
      ```
      
      Having `stream_ids` which are lower than `prev_ids` looks odd. It might work
      (I'm not actually sure), but in any case it doesn't seem like a reasonable
      thing to expect other implementations to support.
      daa1ac89
  19. Mar 30, 2020
  20. Mar 27, 2020
  21. Mar 24, 2020
  22. Feb 21, 2020
  23. Feb 07, 2020
  24. Dec 04, 2019
  25. Nov 27, 2019
  26. Aug 20, 2019
  27. Jul 29, 2019
  28. Jun 20, 2019
  29. May 29, 2019
  30. May 10, 2019
  31. Mar 20, 2019
  32. Aug 10, 2018
  33. Jul 09, 2018
  34. Jul 04, 2018
  35. Jan 26, 2016
  36. Jan 07, 2016
  37. Nov 17, 2015
  38. Apr 01, 2015
  39. Feb 11, 2015
Loading