studio/tuwunel
2
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

Fix sliding-sync again by resetting after interrupted requests. (fixes #190)

Browse Source 
This solution is not elegant but appears to be correct for fixing the issue. A
a more efficient solution might be possible without resetting the connection
which should be further investigated.

Signed-off-by: Jason Volk <jason@zemos.net>
This commit is contained in:
Jason Volk
2025-10-15 21:59:01 +00:00
parent d5b39aa995
commit 4e0249cd2f
1 changed files with 5 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
src/api/client/sync/v5.rs
View File

@@ -23,7 +23,7 @@ use ruma::{
}; };
use tokio::time::{Instant, timeout_at}; use tokio::time::{Instant, timeout_at};
use tuwunel_core::{ use tuwunel_core::{
Result, apply, at, Err, Result, apply, at,
debug::INFO_SPAN_LEVEL, debug::INFO_SPAN_LEVEL,
err, err,
error::inspect_log, error::inspect_log,
@@ -119,6 +119,10 @@ pub(crate) async fn sync_events_v5_route(
let (mut conn, _) = join(conn, ping_presence).await; let (mut conn, _) = join(conn, ping_presence).await;
if conn.next_batch != since {
return Err!(Request(UnknownPos("Requesting unknown or duplicate 'pos' parameter.")));
}
conn.update_cache(request); conn.update_cache(request);
conn.globalsince = since; conn.globalsince = since;
conn.next_batch = since; conn.next_batch = since;