This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
Remove get_destination_retry_timings cache #3914
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Currently we rely on the master to invalidate this cache promptly. However, after having moved most federation endpoints off of master this no longer happens, causing outbound fedeariont to get blackholed. Fixes #3798
erikjohnston
force-pushed
the
erikj/remove_retry_cache
branch
from
3680710 to
83ee559
Compare
richvdh
approved these changes
Sep 19, 2018
changelog.d/3914.bugfix
Outdated
| @@ -0,0 +1 @@ | |||
| Fix bug where outboud federation would stop talking to some servers when using workers | |||
NOES, not the fearsome FEDEARIONT! |
|
I wonder if there exists a tool to monitor all outbound network traffic from my computer and run it through a spell checker... |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently we rely on the master to invalidate this cache promptly.
However, after having moved most federation endpoints off of master this
no longer happens, causing outbound fedeariont to get blackholed.
Fixes #3798