Fix some looping_call calls which were broken in #3604
It turns out that looping_call does check the deferred returned by its callback, and (at least in the case of client_ips), we were relying on this, and I broke it in #3604. Update run_as_background_process to return the deferred, and make sure we return it to clock.looping_call.
Showing
- changelog.d/3610.feature 1 addition, 0 deletionschangelog.d/3610.feature
- synapse/app/homeserver.py 2 additions, 2 deletionssynapse/app/homeserver.py
- synapse/groups/attestations.py 1 addition, 1 deletionsynapse/groups/attestations.py
- synapse/handlers/profile.py 1 addition, 1 deletionsynapse/handlers/profile.py
- synapse/metrics/background_process_metrics.py 8 additions, 2 deletionssynapse/metrics/background_process_metrics.py
- synapse/rest/media/v1/media_repository.py 1 addition, 1 deletionsynapse/rest/media/v1/media_repository.py
- synapse/rest/media/v1/preview_url_resource.py 1 addition, 1 deletionsynapse/rest/media/v1/preview_url_resource.py
- synapse/storage/client_ips.py 1 addition, 1 deletionsynapse/storage/client_ips.py
- synapse/storage/devices.py 1 addition, 1 deletionsynapse/storage/devices.py
- synapse/storage/event_federation.py 1 addition, 1 deletionsynapse/storage/event_federation.py
- synapse/storage/event_push_actions.py 2 additions, 2 deletionssynapse/storage/event_push_actions.py
- synapse/storage/transactions.py 3 additions, 1 deletionsynapse/storage/transactions.py
- synapse/util/caches/expiringcache.py 1 addition, 1 deletionsynapse/util/caches/expiringcache.py
Loading
Please register or sign in to comment