Erik JohnstonandClaude Opus 5.5 eec1906e75 Answer conflict-free Rust state resolutions synchronously ...

When the state sets agree there is nothing to read or resolve. The
handler now separates the state under the GIL and, without conflicts,
returns an already-fired deferred instead of checking out a connection
and hopping through the tokio runtime.

This also keeps the common path synchronous, as the Python one is:
test_failed_partial_join_is_clean checks the partial-state flag right
after the join fails, and the resync that clears it resolves zero state
groups.

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

2026-10-13 11:37:42 +00:00

..

benches

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

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

src

Answer conflict-free Rust state resolutions synchronously

2026-10-13 11:37:42 +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

Add a connection-checkout timeout to the native Rust Postgres pool

2026-10-12 18:31:24 +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