Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't do /keys/changes on incremental sync #625

Merged
merged 6 commits into from
Mar 9, 2018
Merged

Commits on Mar 8, 2018

  1. Don't do /keys/changes on incremental sync

    Remove the call to /keys/changes when we do an incremental syn
    where the old sync token doesn't match the one in the device list
    store. To allow us to do this, always save the device list store
    before saving the sync data, so we can safely assume the device
    list store is at least as fresh as the sync token in the sync store.
    
    Thread save functions through to allow this, add a delay parameter
    so the sync can save the device list immediately and skip the wait,
    and add a wantsSave() method so the sync can skip saving the device
    list if the sync store isn't going to save anyway.
    
    Fixes element-hq/element-web#6068
    dbkr committed Mar 8, 2018
    Configuration menu
    Copy the full SHA
    4f17352 View commit details
    Browse the repository at this point in the history
  2. lint

    dbkr committed Mar 8, 2018
    Configuration menu
    Copy the full SHA
    727ad57 View commit details
    Browse the repository at this point in the history
  3. fix tests

    dbkr committed Mar 8, 2018
    Configuration menu
    Copy the full SHA
    a0578ef View commit details
    Browse the repository at this point in the history
  4. Configuration menu
    Copy the full SHA
    3d1fcc6 View commit details
    Browse the repository at this point in the history
  5. DeviceList: bring save forward if necessary

    If save is called with a delay that would want the save to happen
    sooner then the save we currently have scheduled, cancel the
    current save and schedule a new one for the sooner time.
    dbkr committed Mar 8, 2018
    Configuration menu
    Copy the full SHA
    facfcf6 View commit details
    Browse the repository at this point in the history

Commits on Mar 9, 2018

  1. Move comment up

    dbkr committed Mar 9, 2018
    Configuration menu
    Copy the full SHA
    5a23927 View commit details
    Browse the repository at this point in the history