This was broken when device list updates were implemented, as Mailer
could no longer instantiate an AuthHandler due to a dependency on
federation sending.

This is because it now relies of the caches stream, which only works on
postgres. We are trying to test with sqlite.

Instead of calculating the size of the cache repeatedly, which can take
a long time now that it can use a callback, instead cache the size and
update that on insertion and deletion.

This requires changing the cache descriptors to have two caches, one for
pending deferreds and the other for the actual values. There's no reason
to evict from the pending deferreds as they won't take up any more
memory.

Signed-off-by: Marcin Bachry <hegel666@gmail.com>

Make sure that a user cannot pretend to be a guest by adding 'guest = True'
caveats.

The old test expected an incorrect wrapping due to the preview function
not using unicode properly, so it got the wrong length.

Signed-off-by: Johannes Löthberg <johannes@kyriasis.com>

Signed-off-by: Johannes Löthberg <johannes@kyriasis.com>

We might as well treat all refresh_tokens as invalid. Just return a 403 from
/tokenrefresh, so that we don't have a load of dead, untestable code hanging
around.

Still TODO: removing the table from the schema.

The 'time' caveat on the access tokens was something of a lie, since we weren't
enforcing it; more pertinently its presence stops us ever adding useful time
caveats.

Let's move in the right direction by not lying in our caveats.

Since we're not doing refresh tokens any more, we should start killing off the
dead code paths. /tokenrefresh itself is a bit of a thornier subject, since
there might be apps out there using it, but we can at least not generate
refresh tokens on new logins.

Also make it an inclusive not exclusive filter, as the spec demands.

 * add tests for filter api errors

 * add tests

Signed-off-by: Alexander Maznev <alexander.maznev@gmail.com>

Signed-off-by: Patrik Oldsberg <patrik.oldsberg@ericsson.com>