#31373: Django 3.x / uwsgi is leaking connections
-------------------------------------+-------------------------------------
Reporter: Marcin Nowak | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 3.0
(models, ORM) |
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Simon Charette):
* status: closed => new
* severity: Normal => Release blocker
* cc: Andrew Godwin (added)
* type: Uncategorized => Bug
* component: Uncategorized => Database layer (models, ORM)
* resolution: needsinfo =>
* stage: Unreviewed => Accepted
Comment:
Thanks for the sample project.
I managed to bisect the regression at
a415ce70bef6d91036b00dd2c8544aed7aeeaaed which introduced async support in
Django.
I didn't investigate why connections kept piling up but I suspect
[https://github.com/django/django/commit/a415ce70bef6d91036b00dd2c8544aed7aeeaaed
#diff-c50ed26e574fb41592a832e0b37c5713R143-R148 these lines] are to blame.
--
Ticket URL: <https://code.djangoproject.com/ticket/31373#comment:14>
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.8e0b47e4105f1030430619cc719e0b38%40djangoproject.com.