gnuxie b9284f0167 Reduce the throttle test theshold even more. ... The implementation is rubbish, as it doesn't avoid the exponential backoff Remove default rate limit testing. It doesn't work. No there really isn't more to say about it you're welcome to dispute it if you're going to do the work investigating. I'm not. We used to have a test here that tested whether Mjolnir was going to carry out a redact order the default limits in a reasonable time scale. Now I think that's never going to happen without writing a new algorithm for respecting rate limiting. Which is not something there is time for. https://github.com/matrix-org/synapse/pull/13018 Synapse rate limits were broken and very permitting so that's why the current hack worked so well. Now it is not broken, so our rate limit handling is. b850e4554c Honestly I don't think we can expect anyone to be able to use Mjolnir under default rate limits. well, it's not quite simple as broken, but it is broken. With the default level in synapse (which is what matrix.org uses) it is struggling to redact 15 messages within 5 minutes. that means 5 messages over the burst count. This is ofc ontop mjolnir sending reactions / responding to replies (which isn't much but... enough to mess with the rate limiter since ofc, Synapse tells requests to wait x amount of time before trying again, but that doesn't help for concurrent requests since ofc there's only 1 slot available at that future time. This means Synapse just wacks everything with exponentially longer shit without many (or any?) events going through it used to be fine because rate limiting in synapse used to be a lot more liberal because it was "broken" or something, that's not me saying it's broken that's just what synapse devs say which is probably true. if all requests went into a queue then yeah you could eliminate one problem but that's a lot of work and i don't think we should be doing it cos no one uses mjolnir like this anyways		2022-08-16 12:55:30 +01:00
..
commands	fix CI (#282)	2022-05-03 11:20:40 +01:00
abuseReportTest.ts	Retry requests in case of throttling (#178)	2022-01-25 12:19:44 +00:00
banListTest.ts	Activity tracker wouldn't update for recently joined/parted protected rooms.	2022-08-15 13:29:19 +01:00
clientHelper.ts	Stop the config being global (in almost all contexts). (#334)	2022-08-09 11:29:27 +01:00
detectFederationLagTest.ts	A room Protection designed to measure lag in a room (#217)	2022-02-24 13:43:31 +01:00
fixtures.ts	Stop the config being global (in almost all contexts). (#334)	2022-08-09 11:29:27 +01:00
helloTest.ts	Retry requests in case of throttling (#178)	2022-01-25 12:19:44 +00:00
manualLaunchScript.ts	Stop the config being global (in almost all contexts). (#334)	2022-08-09 11:29:27 +01:00
mjolnirSetupUtils.ts	Stop the config being global (in almost all contexts). (#334)	2022-08-09 11:29:27 +01:00
policyConsumptionTest.ts	Fix uses of old interface for registration helper in tests.	2022-01-25 18:23:14 +00:00
protectionSettingsTest.ts	refactor (and simplify) how protections are stored in-memory	2022-02-07 13:48:32 +00:00
reportPollingTest.ts	Report polling test temporality (#325)	2022-07-05 16:58:29 +01:00
roomMembersTest.ts	Fix: roomMemberTest off-by-one error (#324)	2022-07-05 15:33:53 +02:00
standardConsequenceTest.ts	fix CI (#282)	2022-05-03 11:20:40 +01:00
throttleQueueTest.ts	A background queue for kicking (#296)	2022-06-08 11:49:43 +02:00
throttleTest.ts	Reduce the throttle test theshold even more.	2022-08-16 12:55:30 +01:00
timelinePaginationTest.ts	Retry requests in case of throttling (#178)	2022-01-25 12:19:44 +00:00
utilsTest.ts	move LogProxy.logMessage to Mjolnir.logMessage (#194)	2022-02-15 15:44:41 +00:00