#31728: cache.backends.db._cull sometimes fails with 'NoneType' object is not
subscriptable
-------------------------------------+------------------------------------
Reporter: Guillermo Bonvehí | Owner: nobody
Type: Bug | Status: closed
Component: Core (Cache system) | Version: master
Severity: Normal | Resolution: fixed
Keywords: cache db | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+------------------------------------
Comment (by Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"b2e2489d807de360068f5a34c57d5345e526caf3" b2e2489]:
{{{
#!CommitTicketReference repository=""
revision="b2e2489d807de360068f5a34c57d5345e526caf3"
[3.1.x] Fixed #31728 -- Fixed cache culling when no key is found for
deletion.
DatabaseCache._cull implementation could fail if no key was found to
perform a deletion in the table. This prevented the new cache key/value
from being correctly added.
Backport of f386454d1302b66d0eb331ed0ae9e4811e2f3a15 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/31728#comment:7>
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.6fc6314102c111e5422bd158513941f2%40djangoproject.com.
