#25840: cache.get_or_set() works incorrectly with DummyCache backend
-------------------------------------+-------------------------------------
Reporter: oleksiyivanenko | Owner: nobody
Type: Bug | Status: closed
Component: Core (Cache system) | Version: 1.9
Severity: Normal | Resolution: fixed
Keywords: get_or_set | Triage Stage: Accepted
dummycache |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"8e838d9c869083597dc9e161ae2fe37acaa90de9" 8e838d9]:
{{{
#!CommitTicketReference repository=""
revision="8e838d9c869083597dc9e161ae2fe37acaa90de9"
Fixed #25840 -- Fixed BaseCache.get_or_set() on the DummyCache backend.
This also fixes a possible data eviction race condition between
setting and getting a key. Another thread could remove the key
before get_and_set() accesses it again. In this case, now the
default value will be returned instead of None.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/25840#comment:6>
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/073.090d56b88da9a6ca630f4e2dea816938%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
