Erik JohnstonandClaude Opus 5 9b5697d378 Move per-homeserver Rust state into a RustRuntime object on the HomeServer (#20011) ...

Previously the tokio runtime was stashed in a hidden attribute on the
reactor object, installed lazily by whichever Rust code first needed it,
and started via `callWhenRunning`.

Instead, we create a `RustRuntime` (accessible via
`HomeServer.get_rust_runtime()`) that holds any per-reactor Rust state,
such as the tokio runtime. It is constructed lazily on use. Rust
consumers (`HttpClient`, `VersionsHandler`, the Python DB pool wrapper)
now receive the runtime or reactor handle explicitly, and the
`reactor.run()` / manual-startup workarounds in tests are no longer
needed.

We also add helper wrappers in Rust for `Reactor` and `HomeServer` that
exposes the needed functionality.

The aim is to allow us to have a Rust-side clock (mainly to get the
current time), that respects the unit test per-reactor time management.

---------

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>

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

..

__init__.py

Write some tests for the email pusher (#4095)

2018-10-30 23:55:43 +11:00

test_bulk_push_rule_evaluator.py

Write union types as X | Y where possible (#19111)

2025-11-06 14:02:33 -06:00

test_email.py

Add tests to ensure that email notification links are sanitized (#19741)

2026-06-03 17:36:58 -05:00

test_http.py

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

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

test_presentable_names.py

Fix up event-construction in tests ahead of the Rust event port (#19781)

2026-05-15 10:12:42 +01:00

test_push_rule_evaluator.py

Fix up event-construction in tests ahead of the Rust event port (#19781)

2026-05-15 10:12:42 +01:00