#36439: Auth hashing blocks event loop if using asyncio
-------------------------------------+-------------------------------------
Reporter: Robert Aistleitner | Owner: Roelzkie
Type: | Status: closed
Cleanup/optimization |
Component: contrib.auth | Version: 5.2
Severity: Normal | Resolution: fixed
Keywords: async, auth, | Triage Stage: Ready for
asyncio, performance | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Jacob Walls <jacobtylerwalls@…>):
In [changeset:"7f66c3b41f0fb0fb938d7b96e20a28dccdaa2ecd" 7f66c3b4]:
{{{#!CommitTicketReference repository=""
revision="7f66c3b41f0fb0fb938d7b96e20a28dccdaa2ecd"
Refs #36439 -- Added sync_to_async() to dummy password hasher path.
Since the existing user path eventually calls sync_to_async() in
acheck_password,
aim for parity with the nonexistent/inactive user branch by adding
sync_to_async().
Follow-up to 748ca0a146175c4868ece87f5e845a75416c30e3.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36439#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 [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019dfe04fe44-6aa3de00-ae28-42fb-ae8d-4064fca34935-000000%40eu-central-1.amazonses.com.
