feat: Support processing concurrent background transactions #1428
2026-02-23
chore: Refactor
transaction_ids -> transactions
Some checks failed
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m32s
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 2m24s
Documentation / Build and Deploy Documentation (push) Successful in 3m58s
Checks / Prek / Pre-commit & Formatting (push) Successful in 6m38s
Release Docker Image / Build linux-amd64 (release) (push) Has been cancelled
Release Docker Image / Build linux-arm64 (release) (push) Has been cancelled
Checks / Prek / Clippy and Cargo Tests (push) Has been cancelled
Release Docker Image / Create Multi-arch Release Manifest (push) Has been cancelled
Release Docker Image / Build linux-amd64 (max-perf) (push) Has been cancelled
Release Docker Image / Build linux-arm64 (max-perf) (push) Has been cancelled
Release Docker Image / Create Max-Perf Manifest (push) Has been cancelled
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 41m27s
chore: Fix incorrect capitalisation
I didn't realise I agreed to take an English class with @ginger while working on this server lol
refactor: Make federation transaction handle errors correctly
We have a dedicated error type that's then matched. Event sorting is now infallible. Could probably be cleaned up in a bit.
fix: Clean up cache, prevent several race conditions
We use one map which is only ever held for a short time.
feat(federation): Restructure transaction_ids service
Adds two new in-memory maps to the service in to prepare for better handlers