#35618: response.close() in a TestCase prematurely closes PostgreSQL connection
and
leads to psycopg2.InterfaceError
-------------------------------------+-------------------------------------
Reporter: Anders Kaseorg | Owner: (none)
Type: Uncategorized | Status: new
Component: Database layer | Version: 5.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
-------------------------------------+-------------------------------------
Changes (by Carlton Gibson):
* cc: Carlton Gibson, Jon Janzen (added)
Comment:
We had a similar issue in Channels, which we've addressed by (similarly)
disabling the close_old_connections handler during tests.
[https://github.com/django/channels/pull/2101 You can see the PR here].
We have this down as related to #30448.
--
Ticket URL: <https://code.djangoproject.com/ticket/35618#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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070190ca00cec1-f6d70d2d-8ee4-4cb9-a158-2968c86a5ac6-000000%40eu-central-1.amazonses.com.
