Upgrade to 1.3.6 stops the cluster from working

[michaelbartz]

We upgraded from 1.3.5 to 1.3.6 and our cluster and scheduled jobs quit working. The error logs are filled with this message:

ERROR localtime() cannot be applied to a naive datetime

[michaelbartz]

this is broken on multiple OS's, Linux, Mac, and Ubuntu. Running Python 3.9.0 to 3.9.5.

[Koed00]

My guess would be that you have timezone support disabled in Django. All the tests are being done with USE_TZ = True
We'll need to add some check for this before we call localtime, cause this has fixed a bunch of issues for other people.

Will try to make time for this, but any help is appreciated.

[michaelbartz]

That was our guess too. We reverted for now. We will try to look at this after our next software release. Thanks for responding. Michael From: Ilan Steemers ***@***.***> Date: Wednesday, May 26, 2021 at 9:01 AM To: Koed00/django-q ***@***.***> Cc: Michael Bartz ***@***.***>, Author ***@***.***> Subject: Re: [Koed00/django-q] Upgrade to 1.3.6 stops the cluster from working (#565) CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. My guess would be that you have timezone support disabled in Django. All the tests are being done with USE_TZ = True We'll need to add some check for this before we call localtime, cause this has fixed a bunch of issues for other people. Will try to make time for this, but any help is appreciated. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FKoed00%2Fdjango-q%2Fissues%2F565%23issuecomment-848795157&data=04%7C01%7Cmichael.bartz%40dunavant.com%7Ce60809c3a24b42d4971508d9204ec63f%7C9a72383b7f0246d7bb1ce03b029894df%7C0%7C0%7C637576344987789826%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=KDuD2kUsNkfCaTHtW9keNCp06ORj7yotnqqICQXqizA%3D&reserved=0>, or unsubscribe<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAST64AGUAZRXJWW36CWSZKTTPT5L5ANCNFSM45QEAJGA&data=04%7C01%7Cmichael.bartz%40dunavant.com%7Ce60809c3a24b42d4971508d9204ec63f%7C9a72383b7f0246d7bb1ce03b029894df%7C0%7C0%7C637576344987799825%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=jprPhiOZ6J3Fjb9z6nuECiSSoVdruhCiseP8shMx%2Fz4%3D&reserved=0>.

[Koed00]

@michaelbartz could you give the master branch a whirl? I think this should fix it.