FutureWarning for Cron Scheduled Jobs

[ross-spencer]

The current implementation is raising a FutureWarning for Cron jobs.

(venv) user:~/git/orcfax/collector-node$ python heartbeat.py 
Feeds to be removed by this heartbeat before being added: ADAUSD-ee4eed14-ffc2-11ed-9f67-67fb68ae3988
/home/user/git/orcfax/collector-node/venv/lib/python3.10/site-packages/rq_scheduler/utils.py:28: FutureWarning: Version 0.22.0+ of crontab will use datetime.utcnow() and
datetime.utcfromtimestamp() instead of datetime.now() and
datetime.fromtimestamp() as was previous. This had been a bug, which will be
remedied. If you would like to keep the *old* behavior:
`ct.next(..., default_utc=False)` . If you want to use the new behavior *now*:
`ct.next(..., default_utc=True)`. If you pass a datetime object with a tzinfo
attribute that is not None, timezones will *just work* to the best of their
ability. There are tests...
  next_time = cron.next(now=now, return_datetime=True)
Feeds queued: ADAUSD-ee4eed14-ffc2-11ed-9f67-67fb68ae3988

This seems to be the affected line:

rq-scheduler/rq_scheduler/utils.py

Line 28 in 0521e7f

next_time = cron.next(now=now, return_datetime=True)

This can be fixed using the default_utc argument above, or now = datetime.now(timezone.utc).