Erik JohnstonandClaude Opus 5.5 aa2ffd95aa Let Rust code sleep on the virtual test clock ...

Tokio's timers run on real time, but trial drives a virtual reactor clock
that only moves when a test advances it. A Rust task that sleeps with
`tokio::time::sleep` under trial waits out real time while the test
believes none has passed.

`Clock::sleep` sleeps on the virtual clock while a test has pinned it:
`set_virtual_time_msec` wakes the sleepers that are due. Otherwise it is
`tokio::time::sleep`. Code that sleeps takes a `Sleeper`, so that its
Rust unit tests can use tokio's pausable clock instead, since the
virtual time is process-global and an earlier test may have pinned it.

The federation sender port needs this for its backoff and well-known
retry sleeps.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01R5b7Ruy4cgt27Mjq6Ptxbb

2026-10-15 14:54:15 +00:00

..

benches

Add push rules for MSC4075: MatrixRTC invites and notifications (#20227)

2026-09-25 10:40:24 +00:00

src

Let Rust code sleep on the virtual test clock

2026-10-15 14:54:15 +00:00

build.rs

resolves #19403 Report the rust compiler version used in the prometheus metrics (#19643)

2026-04-03 11:21:23 +02:00

Cargo.toml

Let Rust code sleep on the virtual test clock

2026-10-15 14:54:15 +00:00

clippy.toml

Move per-homeserver Rust state into a RustRuntime object on the HomeServer (#20011)

2026-09-21 18:48:37 +01:00