#32403: When run test with off postgres database got `RuntimeError: generator
didn't yield` instead of connection error
-------------------------------------+-------------------------------------
Reporter: Kazantcev Andrey | Owner: Mariusz
| Felisiak
Type: Bug | Status: closed
Component: Database layer | Version: 3.1
(models, ORM) |
Severity: Release blocker | Resolution: fixed
Keywords: postgres db | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by GitHub <noreply@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"f131841c601b9d4884adcdb284b4213c2ad89231" f131841c]:
{{{
#!CommitTicketReference repository=""
revision="f131841c601b9d4884adcdb284b4213c2ad89231"
Fixed #32403 -- Fixed re-raising DatabaseErrors when using only 'postgres'
database.
Thanks Kazantcev Andrey for the report.
Regression in f48f671223a20b161ca819cf7d6298e43b8ba5fe.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/32403#comment:9>
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/064.a37b510a26a5356a6582c65f450225e6%40djangoproject.com.