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
Add count of one time keys to sync stream #2237
Conversation
erikjohnston
assigned
richvdh
May 19, 2017
richvdh
reviewed
May 22, 2017
looks ok, but count_e2e_one_time_keys has a cache, and I'm unconvinced it will be correctly invalidated in the synchotrons when a key is claimed in the main process.
richvdh
assigned
erikjohnston
and unassigned
richvdh
May 22, 2017
Oops, yeah. It now streams the invalidations to workers. |
erikjohnston
assigned
richvdh
and unassigned
erikjohnston
May 22, 2017
|
(The sqlite failure is spurious as it built on a box that didn't have tox installed) |
richvdh
reviewed
May 22, 2017
you missed one of the calls:
synapse/synapse/storage/end_to_end_keys.py
Line 241 in f85a415
LGTM otherwise
richvdh
assigned
erikjohnston
and unassigned
richvdh
May 22, 2017
|
But i used grep and everything! :( |
| @@ -240,6 +240,9 @@ def _claim_e2e_one_time_keys(txn): | ||
| txn.call_after( | ||
| self.count_e2e_one_time_keys.invalidate, (user_id, device_id,) |
Apparently you fail at grep. |
richvdh
closed this
May 23, 2017
richvdh
reopened this
May 23, 2017
And editing code too. Sigh. applies more coffee |
erikjohnston commentedMay 19, 2017
This adds the following to a sync result:
{ "device_one_time_keys_count": { "signed_curve25519": 50 }, ... }