Back-pagination spinner gets stuck after using Purge History API in synapse

[4nd3r]

not sure if synapse or vector-web bug.

[richvdh]

It's trying to back-paginate. Is this in a federated room, or one that only exists on your server?

[4nd3r]

only in my server

[richvdh]

sounds like a synapse bug then. Do you get the same behaviour after reloading riot?

[4nd3r]

yes

[richvdh]

Yup, repeated here; synapse is returning 500 errors. Raised matrix-org/synapse#1623.

[4nd3r]

thanks

[richvdh]

Let's keep this open to track it from the application side.

[babolivier]

We realised today that matrix-org/synapse#1623 had been fixed (just hadn't been closed at the time), should we also close this issue?

[turt2live]

I think this is now waiting on matrix-org/matrix-spec-proposals#2251 to be fixed so we can fix the infinite spinner problem.

[babolivier]

@turt2live Right, but is that infinite spinner problem really still a thing though? I've just tried to reproduce it by creating a room on my local HS (unfederated), sending multiple messages in it, purging the history from one of these messages, and hitting "Clear cache and reload" in Riot. Once the room was loaded by Riot, it apparently tried to back-paginate events before the oldest event not purged, and when /messages returned with an empty chunk ([]) it stopped hitting that endpoint and showing a spinner.

[turt2live]

Hmm, indeed. Closing this as fixed.