forked from Tivix/django-cron
-
Notifications
You must be signed in to change notification settings - Fork 2
updating_cron_to_latest_changes #1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
codegeass2409
wants to merge
41
commits into
Trendlyne-technologies:codegeass2409-patch-1
Choose a base branch
from
Tivix:master
base: codegeass2409-patch-1
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
updating_cron_to_latest_changes #1
codegeass2409
wants to merge
41
commits into
Trendlyne-technologies:codegeass2409-patch-1
from
Tivix:master
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
Remove succeed cron job logs
…-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
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
updating all new changes , including database locking to stop two crons running at same time.