continuwuation/continuwuity
continuwuation/continuwuity
13
79
Fork 85
Code Issues 117 Pull requests 44 Releases 27 Packages 3 Activity Actions 9

WIP: feat: Add method to flush senders when a server becomes active #1463

Closed
nex wants to merge 2 commits from nex/fix/stale-destination-cache into main
pull from: nex/fix/stale-destination-cache
merge into: continuwuation:main
Conversation 0 Commits 2 Files changed 3 +68 -4
nex commented 2026-02-26 16:18:14 +00:00
Owner
Copy link

Currently continuwuity does not track whether a server is online or "offline" since this isn't really a concept the spec has. This means that if a server is unreachable, it may resolve to servername:8448 incorrectly, which then gets saved into the destination cache, and requires manual eviction (or waiting 24 hours). In a similar deficiency vein, the sender service does not try to immediately re-try sending new transactions while it's in exponential backoff, which can happen if it tries to send to the wrong destination.

This PR fixes this by tracking the connectivity of remote servers in-memory. If a server makes a request to us, it is marked as online. If it was previously offline, the destination cache for that server is cleared (triggering a re-resolution), and a flush is sent to the sender for that server, which should cause it to immediately re-try sending transactions. If a transaction fails to send, the server is marked as offline, which currently has no special meaning (apart from the "reconnection" logic mentioned prior), but may be used in the future to determine whether requests like profile lookups and E2EE requests should be aborted early.

Pull request checklist:

  • This pull request targets the main branch, and the branch is named something other than
    main.
  • I have written an appropriate pull request title and my description is clear.
  • I understand I am responsible for the contents of this pull request.
  • I have followed the contributing guidelines:
Currently continuwuity does not track whether a server is online or "offline" since this isn't really a concept the spec has. This means that if a server is unreachable, it may resolve to `servername:8448` incorrectly, which then gets saved into the destination cache, and requires manual eviction (or waiting 24 hours). In a similar deficiency vein, the sender service does not try to immediately re-try sending new transactions while it's in exponential backoff, which can happen if it tries to send to the wrong destination. This PR fixes this by tracking the connectivity of remote servers in-memory. If a server makes a request to us, it is marked as online. If it was previously offline, the destination cache for that server is cleared (triggering a re-resolution), and a flush is sent to the sender for that server, which should cause it to immediately re-try sending transactions. If a transaction fails to send, the server is marked as offline, which currently has no special meaning (apart from the "reconnection" logic mentioned prior), but may be used in the future to determine whether requests like profile lookups and E2EE requests should be aborted early. <!-- Example: This pull request allows us to warp through time and space ten times faster than before by double-inverting the warp drive with hyperheated jump fluid, both making the drive faster and more efficient. This resolves the common issue where we have to wait more than 10 milliseconds to engage, use, and disengage the warp drive when travelling between galaxies. --> <!-- Closes: #... --> <!-- Fixes: #... --> <!-- Uncomment the above line(s) if your pull request fixes an issue or closes another pull request by superseding it. Replace `#...` with the issue/pr number, such as `#123`. --> **Pull request checklist:** <!-- You need to complete these before your PR can be considered. If you aren't sure about some, feel free to ask for clarification in #dev:continuwuity.org. --> - [x] This pull request targets the `main` branch, and the branch is named something other than `main`. - [x] I have written an appropriate pull request title and my description is clear. - [x] I understand I am responsible for the contents of this pull request. - I have followed the [contributing guidelines][c1]: - [x] My contribution follows the [code style][c2], if applicable. - [x] I ran [pre-commit checks][c1pc] before opening/drafting this pull request. - [ ] I have [tested my contribution][c1t] (or proof-read it for documentation-only changes) myself, if applicable. This includes ensuring code compiles. - [x] My commit messages follow the [commit message format][c1cm] and are descriptive. - [ ] I have written a [news fragment][n1] for this PR, if applicable<!--(can be done after hitting open!)-->. <!-- Notes on these requirements: - While not required, we encourage you to sign your commits with GPG or SSH to attest the authenticity of your changes. - While we allow LLM-assisted contributions, we do not appreciate contributions that are low quality, which is typical of machine-generated contributions that have not had a lot of love and care from a human. Please do not open a PR if all you have done is asked ChatGPT to tidy up the codebase with a +-100,000 diff. - In the case of code style violations, reviewers may leave review comments/change requests indicating what the ideal change would look like. For example, a reviewer may suggest you lower a log level, or use `match` instead of `if/else` etc. - In the case of code style violations, pre-commit check failures, minor things like typos/spelling errors, and in some cases commit format violations, reviewers may modify your branch directly, typically by making changes and adding a commit. Particularly in the latter case, a reviewer may rebase your commits to squash "spammy" ones (like "fix", "fix", "actually fix"), and reword commit messages that don't satisfy the format. - Pull requests MUST pass the `Checks` CI workflows to be capable of being merged. This can only be bypassed in exceptional circumstances. If your CI flakes, let us know in matrix:r/dev:continuwuity.org. - Pull requests have to be based on the latest `main` commit before being merged. If the main branch changes while you're making your changes, you should make sure you rebase on main before opening a PR. Your branch will be rebased on main before it is merged if it has fallen behind. - We typically only do fast-forward merges, so your entire commit log will be included. Once in main, it's difficult to get out cleanly, so put on your best dress, smile for the cameras! --> [c1]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md [c2]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/docs/development/code_style.mdx [c1pc]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md#pre-commit-checks [c1t]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md#running-tests-locally [c1cm]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md#commit-messages [n1]: https://towncrier.readthedocs.io/en/stable/tutorial.html#creating-news-fragments
nex added this to the next milestone 2026-02-26 16:18:14 +00:00
feat: Add method to flush senders when a server becomes active
All checks were successful
Update flake hashes / update-flake-hashes (pull_request) Successful in 23s
Details
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m27s
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 3m5s
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 23m6s
Details
5e3174493d
fix: Actually flush destinations before selecting new events
All checks were successful
Update flake hashes / update-flake-hashes (pull_request) Successful in 28s
Details
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m22s
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 4m41s
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 19m51s
Details
82bd0c8e15
nex requested review from Owners 2026-02-27 11:20:50 +00:00
nex changed title from feat: Add method to flush senders when a server becomes active to WIP: feat: Add method to flush senders when a server becomes active 2026-02-27 12:05:04 +00:00
nex closed this pull request 2026-02-27 13:14:44 +00:00
All checks were successful
Update flake hashes / update-flake-hashes (pull_request) Successful in 28s
Details
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m22s
Details
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 4m41s
Required
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 19m51s
Required
Details

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No reviewers
continuwuation/Owners
Labels
Clear labels   
Blocked

This pull request or issue is currently blocked from being merged/closed

  
Bug

Something isn't working as intended

  
Cherry-picking

Commits picked from other conduit projects

  
Database

This requires or includes changes to the database

  
Dependencies

Something dependency related

  
Dependencies/Renovate

Automatic dependency upgrades by Renovate

  
Difficulty
Easy
Low difficulty to implement - touches few parts of the codebase, low complexity

  
Difficulty
Hard
High difficulty to implement - touches many parts of the codebase, high complexity

  
Difficulty
Medium
Medium difficulty to implement - touches more parts of the codebase, higher complexity

  
Documentation

Improvements or additions to documentation

  
Enhancement

New feature or request

  
Good first issue

Good for newcomers

  
Help wanted

Additional eyes and keyboards are required for this one

  
Inherited

Issues that have been inhereted from the project pre-fork

  
Matrix/Administration

Features pertaining to homeserver administration

  
Matrix/Appservices

Features pertaining to the appservice API

  
Matrix/Auth

Features pertaining to authentication

  
Matrix/Client

Features pertaining to client-to-server interactions

  
Matrix/Core

Issues relating to core matrix functionality, such as state resolution and PDU formats

  
Matrix/E2EE

   
Matrix/Federation

Features pertaining to server-to-server interactions

  
Matrix/Hydra

Issues related to room version 12 and related changes (temporary label)

  
Matrix/MSC

Features pertaining to unstable matrix features

  
Matrix/Media

Features pertaining to media interactions

  
Matrix/T&S

Changes or issues related to trust & safety tooling

  
Meta

Related to housekeeping, maintenance, or other repo-meta.

  
Meta/CI

Issues related to CI changes

  
Meta/Packaging

Packaging

  
Priority
Blocking
This issue is blocking the next release

  
Priority
High
This issue is very important

  
Priority
Low
This issue is of a rather low priority

  
Security

This item is related to general security

  
Status
Confirmed
This issue has enough information and is confirmed

  
Status
Duplicate
This issue or pull request already exists

  
Status
Invalid
This issue doesn't seem right

  
Status
Needs Investigation
This issue needs further investigation

  
Support

Questions or support requests

  
To-Merge

   
Wont fix

This will not be worked on

  
old/ci/cd

Ci/CD

Archived

  
old/rust

Pull requests that update Rust code

Archived

No labels
Blocked
Bug
Cherry-picking
Database
Dependencies
Dependencies/Renovate
Difficulty
Easy
Difficulty
Hard
Difficulty
Medium
Documentation
Enhancement
Good first issue
Help wanted
Inherited
Matrix/Administration
Matrix/Appservices
Matrix/Auth
Matrix/Client
Matrix/Core
Matrix/E2EE
Matrix/Federation
Matrix/Hydra
Matrix/MSC
Matrix/Media
Matrix/T&S
Meta
Meta/CI
Meta/Packaging
Priority
Blocking
Priority
High
Priority
Low
Security
Status
Confirmed
Status
Duplicate
Status
Invalid
Status
Needs Investigation
Support
To-Merge
Wont fix
old/ci/cd
old/rust
Milestone
Clear milestone
No items
No milestone
next
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
continuwuation/continuwuity!1463
No description provided.