Commit message (Collapse) | Author | Files | Lines | ||
---|---|---|---|---|---|
2020-02-25 | Increase expected state events in tests for new room by one | Andrew Morgan | 1 | -1/+6 | |
2020-02-24 | Move buildkite config to the pipelines repo (#5943) | Amber Brown | 2 | -0/+16 | |
Note: I kept it in the repo for now ~anoa | |||||
2020-02-24 | Add m.id_access_token flag (#5930) | Andrew Morgan | 2 | -1/+7 | |
Adds a flag to `/versions`' `unstable_features` section indicating that this Synapse understands what an `id_access_token` is, as per https://github.com/matrix-org/synapse/issues/5927#issuecomment-523566043 Fixes #5927 | |||||
2020-02-24 | Removed unused jenkins/ folder and script (#5938) | Amber Brown | 2 | -16/+1 | |
2020-02-24 | Revert "Use the v2 lookup API for 3PID invites (#5897)" | Andrew Morgan | 10 | -320/+183 | |
This reverts commit 978f263e7c5d1eb440efaf07abc5009408ade25d, reversing changes made to 4f6ee99818d9c338944a10585d0aea4c7349d456. | |||||
2020-02-14 | Blacklist some flaky tests | Andrew Morgan | 1 | -0/+6 | |
2020-02-14 | Pin black to 19.3b0 | Andrew Morgan | 1 | -1/+1 | |
2020-02-14 | Fix with isort==4.3.21 and black==19.3b0 | Andrew Morgan | 13 | -24/+19 | |
2020-02-14 | Delete duplicate user deactivation | Andrew Morgan | 1 | -7/+0 | |
2020-02-14 | Fix account_validity incorrect email response content | Andrew Morgan | 1 | -2/+5 | |
2020-02-14 | Fix incorrect run_in_background import statement | Andrew Morgan | 1 | -1/+1 | |
2020-02-14 | Fix signedjson deleted method | Andrew Morgan | 1 | -4/+12 | |
2020-02-11 | Dinsic Blacking with black==18.6b2 | Andrew Morgan | 353 | -10315/+8823 | |
2020-01-24 | Fix resetting password via a phone number (#21) dinsic_2020-02-10 | Andrew Morgan | 2 | -1/+2 | |
2020-01-22 | Validate client_secret parameter according to spec (#20) | Andrew Morgan | 4 | -1/+34 | |
2019-12-16 | Add auth events as per spec. (#6556) | Erik Johnston | 2 | -67/+35 | |
Previously we tried to be clever and filter out some unnecessary event IDs to keep the auth chain small, but that had some annoying interactions with state res v2 so we stop doing that for now. | |||||
2019-12-16 | Add option to allow profile queries without sharing a room (#6523) | Will Hunt | 5 | -1/+28 | |
2019-12-16 | Incorporate review | Brendan Abolivier | 2 | -6/+1 | |
2019-12-16 | Update changelog.d/6553.bugfix | Brendan Abolivier | 1 | -1/+1 | |
Co-Authored-By: Andrew Morgan <1342360+anoadragon453@users.noreply.github.com> | |||||
2019-12-16 | Lint | Brendan Abolivier | 1 | -2/+1 | |
2019-12-16 | Add test case | Brendan Abolivier | 1 | -0/+133 | |
2019-12-16 | Exclude rejected state events when calculating state at backwards extrems ↵ | Richard van der Hoff | 2 | -1/+2 | |
(#6527) This fixes a weird bug where, if you were determined enough, you could end up with a rejected event forming part of the state at a backwards-extremity. Authing that backwards extrem would then lead to us trying to pull the rejected event from the db (with allow_rejected=False), which would fail with a 404. | |||||
2019-12-16 | Persist auth/state events at backwards extremities when we fetch them (#6526) | Richard van der Hoff | 3 | -165/+83 | |
The main point here is to make sure that the state returned by _get_state_in_room has been authed before we try to use it as state in the room. | |||||
2019-12-16 | sanity-checking for events used in state res (#6531) | Richard van der Hoff | 6 | -43/+128 | |
When we perform state resolution, check that all of the events involved are in the right room. | |||||
2019-12-16 | Sanity-check room ids in event auth (#6530) | Richard van der Hoff | 2 | -0/+14 | |
When we do an event auth operation, check that all of the events involved are in the right room. | |||||
2019-12-16 | Check the room_id of events when fetching room state/auth (#6524) | Richard van der Hoff | 2 | -24/+56 | |
When we request the state/auth_events to populate a backwards extremity (on backfill or in the case of missing events in a transaction push), we should check that the returned events are in the right room rather than blindly using them in the room state or auth chain. Given that _get_events_from_store_or_dest takes a room_id, it seems clear that it should be sanity-checking the room_id of the requested events, so let's do it there. | |||||
2019-12-16 | Add `include_event_in_state` to _get_state_for_room (#6521) | Richard van der Hoff | 2 | -18/+22 | |
Make it return the state *after* the requested event, rather than the one before it. This is a bit easier and requires fewer calls to get_events_from_store_or_dest. | |||||
2019-12-16 | Move get_state methods into FederationHandler (#6503) | Richard van der Hoff | 3 | -86/+107 | |
This is a non-functional refactor as a precursor to some other work. | |||||
2019-12-16 | Refactor get_events_from_store_or_dest to return a dict (#6501) | Richard van der Hoff | 2 | -29/+16 | |
There was a bunch of unnecessary conversion back and forth between dict and list going on here. We can simplify a bunch of the code. | |||||
2019-12-16 | Exclude rejected state events when calculating state at backwards extrems ↵ | Richard van der Hoff | 2 | -1/+2 | |
(#6527) This fixes a weird bug where, if you were determined enough, you could end up with a rejected event forming part of the state at a backwards-extremity. Authing that backwards extrem would then lead to us trying to pull the rejected event from the db (with allow_rejected=False), which would fail with a 404. | |||||
2019-12-16 |