#35757: memcached.PyMemcacheCache reentrancy problem with ASGI-based runserver
-------------------------------------+-------------------------------------
Reporter: Harm Verhagen | Owner: (none)
Type: Bug | Status: new
Component: Core (Cache system) | Version: 5.1
Severity: Normal | Resolution:
Keywords: asgi, async | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Carlton Gibson):
Removing `daphne` (or `channels` in older versions) restores use of
Django’s own `runserver` command, so at that point you’re no longer
running ASGI.
I would say the comment about the race condition looks most likely, but
I’m confused by the last remark that it doesn’t occur in production.
(Daphe’s `runserver` command does very little except run `daphne`)
My memcached chops are not what they could be. (I haven’t used it in
production since before 2010 IIRC so… 🤷) Short of a clear diagnosis, it’s
hard to know what to suggest.
--
Ticket URL: <https://code.djangoproject.com/ticket/35757#comment:19>
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/0107019251503ff2-ec9a6209-0b8e-4c80-8a61-0cc33095e75e-000000%40eu-central-1.amazonses.com.
