summary refs log tree commit diff
path: root/scripts-dev/gen_config_documentation.py
diff options
context:
space:
mode:
authorWill Hunt <will@half-shot.uk>2025-06-06 12:59:38 +0100
committerGitHub <noreply@github.com>2025-06-06 11:59:38 +0000
commitd285d76185216914baab6ad0bef63b5c95a87e5f (patch)
tree03276dc145ef5674446be2c1f09ff10eaff0c9c2 /scripts-dev/gen_config_documentation.py
parentRemove destinations from sending if not whitelisted (#18484) (diff)
downloadsynapse-d285d76185216914baab6ad0bef63b5c95a87e5f.tar.xz
Recover an appservice if a successful ping occurs. (#18521)
Fixes https://github.com/element-hq/synapse/issues/14240

This scratches an itch that i've had for years. We regularly run into
the issue where (especially in development) appservices can go down for
a period and them come back up. The ping endpoint was introduced some
time ago which means Synapse can determine if an AS is up more or less
immediately, so we might as well use that to schedule transaction
redelivery.

I believe transaction scheduling logic is largely implementation
specific, so we should be in the clear to do this without any spec
changes.
Diffstat (limited to 'scripts-dev/gen_config_documentation.py')
0 files changed, 0 insertions, 0 deletions