Skip to content

Conversation

@codegeass2409
Copy link

updating all new changes , including database locking to stop two crons running at same time.

Sumit Chachra and others added 30 commits November 1, 2021 17:54
Removed link to fork of a different deprecated Tivix project
Remove misleading link from deprecation notice
ugettext_lazy is an alias.   In django 4.0 need to use gettext_lazy instead
fixes for django 4.0
Command for making cronjobs running in loop or running several times with the sleep time between.
change deprecated assertEquals to assertEqual
change deprecated ugettext_lazy to gettext_lazy
use super() without arguments
user __str__ method to make string represation of model objects

Co-authored-by: Jedrzej Maluszczak <[email protected]>
* run CronJob on days in month

* commit running CronJobs on days of month

* documentation
…e_and_class_name

name locks by module_name.class_name for higher distinction
* Locking backend with database

* documentation of database lock
This parameter (schedule.run_tolerance_seconds) allows to run the job slightly earlier.

For example, consider a job that runs every 5 minutes and last time it was run at 00:00:00. For example, runcrons command
gets called every five minutes starting from 00:00:00.

Without this parameter, the job will be run next time at 00:10:00.

If run_tolerance_seconds is set to non-zero value, the job will be run next time at 00:05:00. That makes job run period
more precise.

By default, run_tolerance_seconds is 0, so this does not affect existing jobs.
…-checking-if-cron-should-run

Issue/80 exclude future dates from checking if cron should run
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants