| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Recover an appservice if a successful ping occurs. (#18521) | Will Hunt | 2025-06-06 | 1 | -1/+6 |
| | | | | | | | | | | | | | | | 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. | ||||
| * | Correctly mention previous copyright (#16820) | Erik Johnston | 2024-01-23 | 1 | -0/+1 |
| | | | | | | During the migration the automated script to update the copyright headers accidentally got rid of some of the existing copyright lines. Reinstate them. | ||||
| * | Update license headers | Patrick Cloke | 2023-11-21 | 1 | -10/+16 |
| | | |||||
| * | Stabilize MSC2659 support for AS ping endpoint. (#15528) | Tulir Asokan | 2023-05-09 | 1 | -6/+4 |
| | | |||||
| * | Implement MSC2659: application service ping endpoint (#15249) | Tulir Asokan | 2023-03-16 | 1 | -0/+115 |
| Signed-off-by: Tulir Asokan <tulir@maunium.net> | |||||
 |
index : matrix/thirdparty/synapse.git | |
| Unnamed repository; edit this file 'description' to name the repository. |
| summary refs log tree commit diff |