introduce federation connection timeout setting #909
No reviewers
Labels
No labels
Bug
Cherry-picking
Database
Dependencies
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/Federation
Matrix/MSC
Matrix/Media
Meta
Meta/Packaging
Priority
Blocking
Priority
High
Priority
Low
Security
Status
Confirmed
Status
Duplicate
Status
Invalid
Status
Needs Investigation
Wont fix
old/ci/cd
old/rust
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: continuwuation/continuwuity#909
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "rooot/continuwuity:federation-conn-timeout"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
introduces a new setting to separate federation connection timeouts from the rest
fixes #906
@ -415,0 +415,4 @@
/// Federation client connection timeout (seconds). You should not set this
/// to high values, as dead homeservers can significantly slow down federation,
/// specifically key retrieval, which will take roughly the amount of time
/// you configure here given that a homeserver doesn't respond.
Might want to mention the client timeout issue
something like "This will cause any sane client to time out /keys/query, causing E2EE and device verification to fail"?
(Probably comes under https://continuwuity.org/development/code_style#inclusivity-and-diversity-guidelines)
im gonna be honest it didn't occur to me in the slightest that the term "sane clients" would be considered ableist language ^^
i guess "This will cause most clients to time out /keys/query, causing E2EE and device verification to fail" would be better?
oh i literally just realized that i came up with the exact same notice, i thought you were quoting, my bad lmao
1d5c3e1cf3
to811623adb8
(forgot to run cargo build before committing the docs change, wasn't worth adding another commit to the history for)
Ahh dammit the formatting was wrong
oops dangit
editing the branch protection rules to force push to main 😗🎶