DJANGO_CELERY_BEAT_TZ_AWARE conflicts with setting beat_cron_starting_deadline of celery

[cy9747]

Summary:

beat_cron_starting_deadline is a celery configuration variable.

beat_cron_starting_deadline is used in the is_due function of the crontab class, which celery beat's class TzAwareCrontab inherits from, but overwrites is_due so that this setting does not work.

• Celery Version: 5.4.0
• Celery-Beat Version: 2.7.0

Exact steps to reproduce the issue:

1. set beat_cron_starting_deadline = 300
2. set DJANGO_CELERY_BEAT_TZ_AWARE = True
3. beat_cron_starting_deadline not work

[cy9747]

Is it a good idea to use super?

before

def is_due(self, last_run_at):
        last_run_at = last_run_at.astimezone(self.tz)

        rem_delta = self.remaining_estimate(last_run_at)
        rem = max(rem_delta.total_seconds(), 0)
        due = rem == 0
        if due:
            rem_delta = self.remaining_estimate(self.now())
            rem = max(rem_delta.total_seconds(), 0)
        return schedstate(due, rem)

after

def is_due(self, last_run_at):
    last_run_at = last_run_at.astimezone(self.tz)

    return super().is_due(last_run_at)