#31515: Django tries to reuse MySQL connections that have gone away with ASGI.
-------------------------------------+-------------------------------------
Reporter: Braunson | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 3.0
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Braunson):
Replying to [comment:14 Andrew Godwin]:
> Well, the current `master` has a whole swathe of different async fixes
due to the work done around the async views work - I would not be
surprised if this is what fixed it if you are comparing to 3.0. The signal
handling, especially, was fixed, and not running the start/end request
signals properly is one of the main causes of this kind of bug.
Awesome. Glad to hear it's supposedly been fixed then. Is there a
roadmap/schedule I can look at for when the master changes will make it
into a release?
--
Ticket URL: <https://code.djangoproject.com/ticket/31515#comment:15>
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.a6c2433ddcd420b22bb9b01d78e4df5a%40djangoproject.com.
