#32643: CookieStorage for contrib.messages crashes after upgrade to django 3.2
-------------------------------------+-------------------------------------
Reporter: Jan Pieter | Owner: Florian
Waagmeester | Apolloner
Type: Bug | Status: closed
Component: contrib.messages | Version: 3.2
Severity: Release blocker | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Adam Hooper):
Could Django please release a patch release that fixes this bug?
Unless I'm misunderstanding, I've run into this:
1. Upgrade to Django 3.2.
2. Test. Everything passes.
3. Deploy to production.
4. Users experience 500 errors.
In my case, I _happened_ to catch this when I deployed to staging. Pure
luck.
But in general, this crash affect tons of existing sites and there is no
workaround until 3.2.1 is released, right?
--
Ticket URL: <https://code.djangoproject.com/ticket/32643#comment:13>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.912bbdbb26e918311b989d388355e696%40djangoproject.com.
