matrix/thirdparty/synapse.git - Unnamed repository; edit this file 'description' to name the repository.

	Commit message (Collapse)	Author	Age	Files	Lines
*	Fix typechecker problems exposed by signedjson 1.1.2 (#12326)	David Robertson	2022-03-29	1	-5/+11
\|
*	Add type hints to `tests/rest` (#12146)	Dirk Klimpel	2022-03-03	1	-15/+29
\| \| \| \| \| \| \|	* Add type hints to `tests/rest` * newsfile * change import from `SigningKey`
*	Add reactor to `SynapseRequest` and fix up types. (#10868)	Erik Johnston	2021-09-24	1	-2/+2
\|
*	Rewrite the KeyRing (#10035)	Erik Johnston	2021-06-02	1	-9/+9
\|
*	Remove redundant "coding: utf-8" lines (#9786)	Jonathan de Jong	2021-04-14	1	-1/+0
\| \| \| \| \| \| \|	Part of #9744 Removes all redundant `# -- coding: utf-8 --` lines from files, as python 3 automatically reads source code as utf-8 now. `Signed-off-by: Jonathan de Jong <jonathan@automatia.nl>`
*	Use mock from the stdlib. (#9772)	Patrick Cloke	2021-04-09	1	-2/+1
\|
*	Update black, and run auto formatting over the codebase (#9381)	Eric Eastwood	2021-02-16	1	-2/+5
\| \| \| \| \| \| \|	- Update black version to the latest - Run black auto formatting over the codebase - Run autoformatting according to [`docs/code_style.md `](https://github.com/matrix-org/synapse/blob/80d6dc9783aa80886a133756028984dbf8920168/docs/code_style.md) - Update `code_style.md` docs around installing black to use the correct version
*	Apply an IP range blacklist to push and key revocation requests. (#8821)	Patrick Cloke	2020-12-02	1	-2/+2
\| \| \| \| \| \| \| \| \| \| \| \|	Replaces the `federation_ip_range_blacklist` configuration setting with an `ip_range_blacklist` setting with wider scope. It now applies to: * Federation * Identity servers * Push notifications * Checking key validitity for third-party invite events The old `federation_ip_range_blacklist` setting is still honored if present, but with reduced scope (it only applies to federation and identity servers).
*	Move `wait_until_result` into `FakeChannel` (#8758)	Richard van der Hoff	2020-11-16	1	-3/+3
\| \| \| \|	FakeChannel has everything we need, and this more accurately models the real flow.
*	Rename `create_test_json_resource` to `create_test_resource` (#8759)	Richard van der Hoff	2020-11-16	1	-1/+1
\| \| \| \| \|	The root resource isn't necessarily a JsonResource, so rename this method accordingly, and update a couple of test classes to use the method rather than directly manipulating self.resource.
*	Convert federation client to async/await. (#7975)	Patrick Cloke	2020-07-30	1	-2/+2
\|
*	Remove spurious "name" parameter to `default_config`	Richard van der Hoff	2020-03-24	1	-2/+2
\| \| \| \| \|	this is never set to anything other than "test", and is a source of unnecessary boilerplate.
*	Back out ill-advised notary server hackery (#6657)	Richard van der Hoff	2020-01-08	3	-4/+131
\| \| \| \| \| \| \| \| \| \| \|	This was ill-advised. We can't modify verify_keys here, because the response object has already been signed by the requested key. Furthermore, it's somewhat unnecessary because existing versions of Synapse (which get upset that the notary key isn't present in verify_keys) will fall back to a direct fetch via `/key/v2/server`. Also: more tests for fetching keys via perspectives: it would be nice if we actually tested when our fetcher can't talk to our notary impl.
*	Workaround for error when fetching notary's own key (#6620)	Richard van der Hoff	2020-01-06	1	-0/+130
	* Kill off redundant SynapseRequestFactory We already get the Site via the Channel, so there's no need for a dedicated RequestFactory: we can just use the right constructor. * Workaround for error when fetching notary's own key As a notary server, when we return our own keys, include all of our signing keys in verify_keys. This is a workaround for #6596.