| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Store key validity time in the storage layer | Richard van der Hoff | 2019-05-23 | 1 | -8/+14 |
| | | | | | | | | | This is a first step to checking that the key is valid at the required moment. The idea here is that, rather than passing VerifyKey objects in and out of the storage layer, we instead pass FetchKeyResult objects, which simply wrap the VerifyKey and add a valid_until_ts field. | ||||
| * | Rewrite store_server_verify_key to store several keys at once (#5234) | Richard van der Hoff | 2019-05-23 | 1 | -2/+12 |
| | | | | | | Storing server keys hammered the database a bit. This replaces the implementation which stored a single key, with one which can do many updates at once. | ||||
| * | Run Black on the tests again (#5170) | Amber Brown | 2019-05-10 | 1 | -1/+2 |
| | | |||||
| * | Remove periods from copyright headers (#5046) | Andrew Morgan | 2019-04-11 | 1 | -1/+1 |
| | | |||||
| * | Fix from_server buglet in get_keys_from_perspectives | Richard van der Hoff | 2019-04-08 | 1 | -0/+1 |
| | | | | | | make sure we store the name of the server the keys came from, rather than the origin server, after doing a fetch-from-perspectives. | ||||
| * | test for get_keys_from_perspectives | Richard van der Hoff | 2019-04-04 | 1 | -0/+67 |
| | | |||||
| * | add a test for get_keys_from_server | Richard van der Hoff | 2019-04-04 | 1 | -0/+63 |
| | | |||||
| * | Rewrite KeyringTestCase as a HomeServerTestCase (#4986) | Richard van der Hoff | 2019-04-03 | 1 | -107/+104 |
| | | | | | | This is a bit fiddly due to the keyring doing weird things with logcontexts. | ||||
| * | Make add_hashes_and_signatures operate on dicts | Erik Johnston | 2019-01-29 | 1 | -30/+26 |
| | | |||||
| * | Check logcontexts before and after each test (#4190) | Richard van der Hoff | 2018-11-27 | 1 | -6/+12 |
| | | | | | | | | | | | | | * Add better diagnostics to flakey keyring test * fix interpolation fail * Check logcontexts before and after each test * update changelog * update changelog | ||||
| * | Run tests under PostgreSQL (#3423) | Amber Brown | 2018-08-13 | 1 | -4/+2 |
| | | |||||
| * | fix up a forced long line | Amber Brown | 2018-08-11 | 1 | -1/+2 |
| | | |||||
| * | Run black. | black | 2018-08-10 | 2 | -43/+22 |
| | | |||||
| * | run isort | Amber Brown | 2018-07-09 | 2 | -9/+11 |
| | | |||||
| * | Pass around the reactor explicitly (#3385) | Amber Brown | 2018-06-22 | 1 | -4/+5 |
| | | |||||
| * | Make tests py3 compatible | Adrian Tschira | 2018-04-16 | 1 | -1/+1 |
| | | | | | | | | | | | | This is a mixed commit that fixes various small issues * print parentheses * 01 is invalid syntax (it was octal in py2) * [x for i in 1, 2] is invalid syntax * six moves Signed-off-by: Adrian Tschira <nota@notafile.com> | ||||
| * | Create dbpool as normal in tests | Richard van der Hoff | 2018-01-27 | 1 | -2/+2 |
| | | | | | | | | | ... instead of creating our own special SQLiteMemoryDbPool, whose purpose was a bit of a mystery. For some reason this makes one of the tests run slightly slower, so bump the sleep(). Sorry. | ||||
| * | Optimise LoggingContext creation and copying | Richard van der Hoff | 2018-01-16 | 1 | -7/+7 |
| | | | | | | | | | It turns out that the only thing we use the __dict__ of LoggingContext for is `request`, and given we create lots of LoggingContexts and then copy them every time we do a db transaction or log line, using the __dict__ seems a bit redundant. Let's try to optimise things by making the request attribute explicit. | ||||
| * | Add some more tests for Keyring | Richard van der Hoff | 2017-09-20 | 1 | -37/+140 |
| | | |||||
| * | Fix concurrent server_key requests (#2458) | Richard van der Hoff | 2017-09-19 | 1 | -3/+55 |
| | | | | | Fix a bug where we could end up firing off multiple requests for server_keys for the same server at the same time. | ||||
| * | Clean up and document handling of logcontexts in Keyring (#2452) | Richard van der Hoff | 2017-09-18 | 1 | -0/+74 |
| | | | | | | | I'm still unclear on what the intended behaviour for `verify_json_objects_for_server` is, but at least I now understand the behaviour of most of the things it calls... | ||||
| * | Fix flake8 warnings for tests | Mark Haines | 2016-02-19 | 1 | -1/+0 |
| | | |||||
| * | copyrights | Matthew Hodgson | 2016-01-07 | 2 | -2/+2 |
| | | |||||
| * | Invoke EventBuilder directly instead of going via the EventBuilderFactory | Paul "LeoNerd" Evans | 2015-10-19 | 1 | -35/+3 |
| | | |||||
| * | Capture __init__.py | Paul "LeoNerd" Evans | 2015-10-19 | 1 | -0/+15 |
| | | |||||
| * | Use assertIn() instead of assertTrue on the 'in' operator | Paul "LeoNerd" Evans | 2015-10-19 | 1 | -6/+6 |
| | | |||||
| * | Another signing test vector using an 'm.room.message' with content, so that ↵ | Paul "LeoNerd" Evans | 2015-10-19 | 1 | -1/+49 |
| | | | | | the implementation will have to redact it | ||||
| * | Initial minimial hack at a test of event hashing and signing | Paul "LeoNerd" Evans | 2015-10-19 | 1 | -0/+98 |
 |
index : matrix/thirdparty/synapse.git | |
| Unnamed repository; edit this file 'description' to name the repository. |
| summary refs log tree commit diff |