Commit message (Collapse) | Author | Files | Lines | ||
---|---|---|---|---|---|
2019-12-18 | 1.7.1 | Richard van der Hoff | 14 | -15/+25 | |
2019-12-17 | Fix bug where we added duplicate event IDs as auth_events (#6560) | Erik Johnston | 2 | -7/+9 | |
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 | 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 | |