Can't enable sliding sync with Conduit

[lnicola]

Steps to reproduce

1. log in to a Conduit HS
2. try to enable sliding sync

Outcome

What did you expect?

It works.

What happened instead?

• the server responds after 30 seconds, but Element times out after 5 seconds (okay, maybe this is on the server)
• if it didn't time out in the previous step, Element still seems to try to validate the proxy address even if empty by requesting /client/server.json, which Conduit doesn't know about

Operating system

Linux

Browser information

Firefox

URL for webapp

1.11.47

Application version

No response

Homeserver

Conduit 0.7.0-alpha

Will you send logs?

No

[weeman1337]

@lnicola Thank you for opening an issue. Unfortunately there is not enough information there for me to be able to reproduce it.

Can you send logs? Does it work with the Element X mobile clients?

[lnicola]

Yes, it works with Element X and I can send the logs, but I think a screen recording would be more clear. Anyway, I'll try to patch Conduit to work around the timeout first.

[lnicola]

Buggy form validation:

Logs uploaded.

[t3chguy]

It is expecting the server.json file from the proxy, right now it only supports the proxy https://github.com/matrix-org/sliding-sync/blob/a8fb52626110b8084e0cc6026a894ce3093eaefb/v3.go#L178

[lnicola]

I managed to enable it, it's currently making a lot of requests (reloading the history?).

The client/server.json request goes to the Element URL, so there's no need to modify the server, dropping a file in there is enough.

[lnicola]

Update: it's making a bajillion requests to _matrix/client/unstable/org.matrix.msc3575/sync?pos=XXXXXX&timeout=20000, where pos is increasing each time by 1 (it's around 385000 at the moment) and the server replies with pretty much the same thing to each of those.

I suspect it's indeed not working very well.

[t3chguy]

If the pos is increasing then the server is sending it incremental data, the way both sync APIs work is long-polling, the server shouldn't respond if it has nothing to send until the timeout is reached. The issue you are hitting is therefore on the server side.

[girlbossceo]

The other issue is most likely due to matrix-org/sliding-sync@e3b110e which I reported https://gitlab.com/famedly/conduit/-/issues/404