Closed ChainGangEvents closed 2 years ago
These issues are the most annoying as I didn't do anything to cause them ;) There appears to be a compatibility issue between python 10 and Django. This probably requires setting the versions in the docker container. I will take a look.
On Wed, Oct 27, 2021 at 6:16 AM ChainGangEvents @.***> wrote:
LogFile.txt https://github.com/esitarski/RaceDB/files/7425235/LogFile.txt
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/esitarski/RaceDB/issues/40#issuecomment-952765357, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABGXKJG3HDXE2HYPN6VBNLUI7GRFANCNFSM5GZ6LFUA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
--
Edward Sitarski
AS Python 3.10 was only released on Oct 4, 2021, I would suggest locking the container to a base image of 3.9.x. There really isn't a need to be on a bleeding edge. I suggest changing the Dockerfile to use Python:3.9-buster as a base container and avoid the newer Debian and Python versions.
Changed the base of the container to python:3.9-buster in the dev branch, and checked in the change. @ChainGangEvents try the "beta" version when you get a chance (and after it builds on GitHub). You may have to remove the old container image using docker - do this is nothing changes. If you still run into issues, please get a bash prompt into the container and verify the python version with "python --version".
If this all works, Ed can promote this to a release.
Thanks Mark. Agree there is no reason to run bleeding-edge python as it just creates problems when the other modules aren't updated for it yet (eg. Django).
On Wed, Oct 27, 2021 at 8:54 AM Mark Buckaway @.***> wrote:
Changed the base of the container to python:3.9-buster in the dev branch, and checked in the change. @ChainGangEvents https://github.com/ChainGangEvents try the "beta" version when you get a chance (and after it builds on GitHub). You may have to remove the old container image using docker - do this is nothing changes. If you still run into issues, please get a bash prompt into the container and verify the python version with "python --version".
If this all works, Ed can promote this to a release.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/esitarski/RaceDB/issues/40#issuecomment-952897176, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABGXKNVROWBZVZBBIW7TCDUI7ZBTANCNFSM5GZ6LFUA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
--
Edward Sitarski
On another note, I am running python 3.9 on my development machine, and I have no problems running RaceDB. As the python 3.10 happens in Django's code, I am confident that fixing the python version to 3.9 will fix the problem.
On Wed, Oct 27, 2021 at 9:27 AM Edward Sitarski @.***> wrote:
Thanks Mark. Agree there is no reason to run bleeding-edge python as it just creates problems when the other modules aren't updated for it yet (eg. Django).
On Wed, Oct 27, 2021 at 8:54 AM Mark Buckaway @.***> wrote:
Changed the base of the container to python:3.9-buster in the dev branch, and checked in the change. @ChainGangEvents https://github.com/ChainGangEvents try the "beta" version when you get a chance (and after it builds on GitHub). You may have to remove the old container image using docker - do this is nothing changes. If you still run into issues, please get a bash prompt into the container and verify the python version with "python --version".
If this all works, Ed can promote this to a release.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/esitarski/RaceDB/issues/40#issuecomment-952897176, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABGXKNVROWBZVZBBIW7TCDUI7ZBTANCNFSM5GZ6LFUA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
--
Edward Sitarski
--
Edward Sitarski
@esitarski Still recommended @ChainGangEvents confirm this solves the problem for him before promoting it to a "production" release. We've seen what your idea "working code" sometimes does :)
@mbuckaway, I can report back that the roll back to Python 3.9 works. @esitarski I've also tested Release v3.0.72-20211027095547 and it works perfect.
Glad to hear that it works. Thanks for your help.
On Wed, Oct 27, 2021 at 10:26 AM ChainGangEvents @.***> wrote:
@mbuckaway https://github.com/mbuckaway, I can report back that the roll back to Python 3.9 works. @esitarski https://github.com/esitarski I've also tested Release v3.0.72-20211027095547 and it works perfect.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/esitarski/RaceDB/issues/40#issuecomment-952985035, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABGXKPNS7OHLEZUG23OCD3UJADXTANCNFSM5GZ6LFUA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
--
Edward Sitarski
My part was easy :) .Thank you. I will close this issue now.
Updated via container. Restarted Docker and RaceDB do not want start. I will add log file below