Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
Already on GitHub? Sign in to your account
Fix bugs in the /keys/changes api #1921
Conversation
richvdh
assigned
erikjohnston
Feb 15, 2017
|
LGTM |
richvdh
merged commit 7dcbcca
into
develop
Feb 15, 2017
6 of 8 checks passed
Sytest Dendron (Commit)
Build #1528 origin/rav/fix_key_changes failed in 3 min 37 sec
Details
Sytest Dendron (Merged PR)
Build finished.
Details
Sytest Postgres (Commit)
Build #2348 origin/rav/fix_key_changes succeeded in 8 min 6 sec
Details
Sytest Postgres (Merged PR)
Build finished.
Details
Sytest SQLite (Commit)
Build #2415 origin/rav/fix_key_changes succeeded in 4 min 49 sec
Details
Sytest SQLite (Merged PR)
Build finished.
Details
continuous-integration/travis-ci/pr
The Travis CI build passed
Details
continuous-integration/travis-ci/push
The Travis CI build passed
Details
richvdh
deleted the
rav/fix_key_changes
branch
Mar 8, 2017
erikjohnston
added a commit
that referenced
this pull request
Mar 13, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
richvdh commentedFeb 15, 2017
get_forward_extremeties_for_roomtakes a numericstream_ordering. We werepassing a
RoomStreamToken, which meant that it returned the currentextremities, rather than those corresponding to the
from_token. However:get_state_ids_for_eventsrequired a second ('types') parameter; this meantthat a
TypeErrorwas thrown and we ended up acting as though there was noprev state.
get_state_ids_for_eventsactually returns a map from event_id to statedictionary - just looking up the state keys in it again meant that we acted
as though there was no prev state. We now check if each member's state has
changed since any of the extremities.
Also add/fix some comments.