#35577: runserver leaves a database connection infinitely unclosed as a result
of
its migration check
-------------------------------------+-------------------------------------
Reporter: Klaas van Schelven | Owner: (none)
Type: Bug | Status: closed
Component: Database layer | Version: 4.2
(models, ORM) |
Severity: Normal | Resolution: invalid
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 Klaas van Schelven):
> it was fixed in Django 5.1
I'm glad it was, this is indeed the fix.
I still can't find any other bug report leading up to the fix so perhaps
the present ticket can lead others to the fix.
--
Ticket URL: <https://code.djangoproject.com/ticket/35577#comment:3>
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
https://groups.google.com/d/msgid/django-updates/0107019082977c1c-b7eafef3-ac11-4918-9d1c-137a5f756464-000000%40eu-central-1.amazonses.com.
