#31654: Memcached key validation raises InvalidCacheKey with clunky message.
-------------------------------------+------------------------------------
Reporter: Tim McCormack | Owner: felixxm
Type: Bug | Status: assigned
Component: Core (Cache system) | Version: 2.2
Severity: Release blocker | Resolution:
Keywords: memcached | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+------------------------------------
Comment (by Tim McCormack):
I don't understand it either! I'll take a little more time to poke at it
today. (For anyone who wants to reproduce this strange test error in
place: Python 3.5 virtualenv, `make requirements`, `pytest -s
common/djangoapps/xblock_django/tests/test_api.py::XBlockSupportTestCase::test_authorable_blocks`
-- on commit 9f53525c.) The farthest I've gotten is that it's definitely
coming from inside `warnings.warn(...)`:
{{{
(Pdb) warnings.warn(("hi", str), RuntimeWarning)
*** TypeError: 'type' object cannot be interpreted as an integer
}}}
Why it doesn't happen on a fresh REPL with all dependencies loaded, I'm
not sure. My best guess is that it has something to do with warning
filtering, since that's configurable and appears to be what's inspecting
the warning message. Probably not specifically relevant to Django or the
edX code, though.
--
Ticket URL: <https://code.djangoproject.com/ticket/31654#comment:5>
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/067.42697ecdc4d8727bf89163c19551f04b%40djangoproject.com.
