#31373: Django 3.x / uwsgi is leaking connections.
     Reporter:  Marcin Nowak         |                    Owner:  nobody
         Type:  Bug                  |                   Status:  closed
    Component:  Database layer       |                  Version:  3.0
  (models, ORM)                      |
     Severity:  Release blocker      |               Resolution:  invalid
     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 felixxm):

 * status:  new => closed
 * resolution:   => invalid


 We confirmed that it was an issue in `asgiref` that was fixed in
 `asgiref==3.2.7` (Thanks Andrew!).

 With `asgiref==3.2.5`:
 Time taken for tests:   47.321 seconds
 Complete requests:      500
 Failed requests:        400

 With `asgiref==3.2.7`:
 Time taken for tests:   4.413 seconds
 Complete requests:      500
 Failed requests:        0

 Note: `asgiref==3.2.6` introduced a regression and shouldn't be used.

Ticket URL: <https://code.djangoproject.com/ticket/31373#comment:22>
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 

Reply via email to