Alex Vandiver a5a5791794 management: Skip hourly crons during deploys. ... This is most important for `send_zulip_update_announcements`, which can race with the version run as a post-deploy hook. However, all of these crons can tolerate being slightly delayed, and there's little benefit to them taking CPU or possibly hitting odd borderline race conditions when the deploy is in progress. For safety, we only trust the deploy lockfile if it was created within the last hour -- deploys should not take more than an hour, and failing to ever run hourly crons is much worse than perhaps running them during a real very-long deploy.		2025-07-15 09:07:36 -07:00
..
__init__.py	Move management commands to the analytics app.	2013-11-06 16:51:08 -05:00
check_analytics_state.py	puppet: Factor out pattern of writing a nagios state file atomically.	2024-05-24 11:31:25 -07:00
clear_analytics_tables.py	management: Move commands to all use ZulipBaseCommand.	2024-05-24 10:30:16 -07:00
clear_single_stat.py	management: Move commands to all use ZulipBaseCommand.	2024-05-24 10:30:16 -07:00
populate_analytics_db.py	stream: Add subscriber_count field.	2025-05-13 17:36:53 -07:00
update_analytics_counts.py	management: Skip hourly crons during deploys.	2025-07-15 09:07:36 -07:00