⬆️ django 4.2

[nikolas]

No description provided.

[nikolas]

There seems to be a bug with running spatialite 5 and django 4.2, that I'm seeing in my dev environment. Details here:

• https://stackoverflow.com/q/75656184/173630
• https://code.djangoproject.com/ticket/32935

[nikolas]

I've reached out in a few places to get some guidance on this:

• https://stackoverflow.com/q/78342638/173630
• https://forum.djangoproject.com/t/errors-with-django-4-2-and-spatialite-5/30277

[nikolas]

It sounds like updating to Spatialite 5.1 would fix the issue: https://stackoverflow.com/a/78343541/173630

Now we just have to figure out how to set that up and build it on github actions and jenkins.

Also, this upstream patch fixes the issue for spatialite 5.0.1: django/django#18083

[nikolas]

@ndittren this should be good to deploy as long as we avoid the spatialite versions 5.0 / 5.0.1. Production is currently on ubuntu 20, which uses spatialite 4.3. In my dev environment I do have spatialite 5.0.1, and I'm working around this bug by manually applying this patch in django's code in my venv: django/django#18083

Moving forward, Ubuntu 24 is about to be released, and comes with Spatialite 5.1, and this bug is apparently fixed there.

[ndittren]

@nikolas Okay looks good to me. Footprints prod currently has an unhealthygroup alarm on cloudwatch. Should we wait for that to clear up?

[nikolas]

I think this can go through now that the alarm is green and footprints is fixed.