#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
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* component: Uncategorized => Database layer (models, ORM)
* resolution: => invalid
* status: new => closed
* type: Uncategorized => Bug
Comment:
Django 4.2 is in extended support and no longer receives bugfixes (except
security patches). Moreover, it was fixed in Django 5.1
(bcccea3ef31c777b73cba41a6255cd866bf87237).
--
Ticket URL: <https://code.djangoproject.com/ticket/35577#comment:2>
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/010701908272b4ad-7dc8a6c1-bac5-4d33-bf4f-bac79f867989-000000%40eu-central-1.amazonses.com.
