Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Bump black from 23.10.1 to 24.2.0 (#16936) | dependabot[bot] | 2024-03-13 | 1 | -3/+3 |
| | |||||
* | 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 |
| | |||||
* | Fix rare bug that broke looping calls (#16210) | Erik Johnston | 2023-08-30 | 1 | -14/+22 |
| | | | | | | | | | | * Fix rare bug that broke looping calls We can't interact with the reactor from the main thread via looping call. Introduced in v1.90.0 / #15791. * Newsfile | ||||
* | Fix database performance of read/write worker locks (#16061) | Erik Johnston | 2023-08-17 | 1 | -52/+35 |
| | | | | | | | We were seeing serialization errors when taking out multiple read locks. The transactions were retried, so isn't causing any failures. Introduced in #15782. | ||||
* | Add ability to wait for locks and add locks to purge history / room deletion ↵ | Erik Johnston | 2023-07-31 | 1 | -66/+124 |
| | | | | | (#15791) c.f. #13476 | ||||
* | Add basic read/write lock (#15782) | Erik Johnston | 2023-07-05 | 1 | -56/+168 |
| | |||||
* | Require SQLite >= 3.27.0 (#13760) | David Robertson | 2022-09-09 | 1 | -82/+39 |
| | |||||
* | LockStore: fix acquiring a lock via `LockStore.try_acquire_lock` (#12832) | Sumner Evans | 2022-05-30 | 1 | -1/+18 |
| | | | Signed-off-by: Sumner Evans <sumner@beeper.com> | ||||
* | Type hint the constructors of the data store classes (#11555) | Sean Quah | 2021-12-13 | 1 | -3/+11 |
| | |||||
* | Add type hints to some storage classes (#11307) | Patrick Cloke | 2021-11-11 | 1 | -2/+4 |
| | |||||
* | Handle federation inbound instances being killed more gracefully (#11262) | Erik Johnston | 2021-11-08 | 1 | -10/+21 |
| | | | | | | | | | | | | | | | | | * Make lock better handle process being killed If the process gets killed and restarted (so that it didn't have a chance to drop its locks gracefully) then there may still be locks in the DB that are for the same instance that haven't yet timed out but are safe to delete. We handle this case by a) checking if the current instance already has taken out the lock, and b) if not then ignoring locks that are for the same instance. * Periodically check for old staged events This is to protect against other instances dying and their locks timing out. | ||||
* | Fix dropping locks on shut down (#10433) | Erik Johnston | 2021-07-20 | 1 | -1/+5 |
| | |||||
* | Ensure we always drop the federation inbound lock (#10336) | Erik Johnston | 2021-07-09 | 1 | -2/+13 |
| | |||||
* | Add a distributed lock (#10269) | Erik Johnston | 2021-06-29 | 1 | -0/+334 |
This adds a simple best effort locking mechanism that works cross workers. |