Skip to content
This repository was archived by the owner on Apr 26, 2024. It is now read-only.

Add a note to the config documentation that the 'delete_stale_devices_after' job always runs on the main process #15452

Merged
anoadragon453 merged 2 commits into from
Apr 18, 2023
Merged

Add a note to the config documentation that the 'delete_stale_devices_after' job always runs on the main process #15452

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7fef1b1
note 'delete_stale_devices_after' job always runs on main process
anoadragon453 Apr 17, 2023
fa8570b
changelog
anoadragon453 Apr 17, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions changelog.d/15452.doc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
Note that the `delete_stale_devices_after` background job always runs on the main process.
4 changes: 4 additions & 0 deletions docs/usage/configuration/config_documentation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -577,6 +577,10 @@ delete any device that hasn't been accessed for more than the specified amount o

Defaults to no duration, which means devices are never pruned.

**Note:** This task will always run on the main process, regardless of the value of
`run_background_tasks_on`. This is due to workers currently not having the ability to
delete devices.

Example configuration:
```yaml
delete_stale_devices_after: 1y
Expand Down