In reply to@emma:rory.gay
Tbh my main issue with lack of filtered sync is payload size

In reply to@emma:rory.gay
Yknow, 12mbps connection and all

In reply to@emma:rory.gay
My synapse init syncs kn seconds, but thats all void when it takes me a minute to download

In reply to @olivia:envs.net
it's good to know that synapse initial sync is much faster, so it's not fundamental

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   160  100   160    0     0      1      0  0:02:40  0:02:00  0:00:40    45
curl 'https://matrix.rory.gay/_matrix/client/v3/sync?timeout=0' -H  -H  -H  -  0.05s user 0.09s system 0% cpu 2:00.54 total

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 48.3M    0 48.3M    0     0  2920k      0 --:--:--  0:00:16 --:--:-- 8034k
curl 'https://matrix.rory.gay/_matrix/client/v3/sync?timeout=0' -H  -H  -H  -  0.29s user 0.31s system 3% cpu 16.975 total

there it is

I came here from the synapse developer docs, I believe that this room is matrix dev in general, not synapse dev specifically, so forgive me if this question is in the wrong place.

I'm trying to run complement tests against my synapse fork in github actions. When I do so, a bunch of tests fail remotely that don't fail locally using the complement.sh script in the synapse repo. Most of the tests fail on Bad JSON value: float. For anyone who has worked with complement tests before - is there any obvious reason why this might be happening?