#31895: Process crash after upgrade to 3.1: Incorrect padding
-------------------------------------+-------------------------------------
Reporter: Matt Hegarty | Owner: nobody
Type: Uncategorized | Status: closed
Component: Core (Other) | Version: 3.1
Severity: Normal | Resolution: needsinfo
Keywords: incorrect padding, | Triage Stage:
badsignature | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Matt Hegarty):
Thanks for the response. It does look similar to the other issues you
posted. I don't have a reproducible instance at present. The only way I
can think to reproduce would be to start up a 3.0 site, login, wait for
the session to expire, then upgrade to 3.1. These are the steps that
would have happened on the environment where I encountered the issue.
--
Ticket URL: <https://code.djangoproject.com/ticket/31895#comment:4>
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/072.fc42b1626f2a4f61360d29aca919ff88%40djangoproject.com.
