#24523: django.apps.registry.populate() does not handle failures in
app_config.ready()
-------------------------------+--------------------------------------
Reporter: kalium99 | Owner: nobody
Type: Bug | Status: new
Component: Uncategorized | Version: 1.7
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 kalium99):
Just to clarify this pont:
it only really becomes annoying when you have a multiprocess model, and
flaky infrastructure. Where you will randomly get 500's when using your
app (depending on whether the process that your request is given to does
or does not have this problem).
Of course, if your infrastructure is going up and down all the time you
can expect your app to behave it all sorts of strange ways. What I
specifically meant though, is that even if your DB fails for just a moment
and quickly recovers you could have potentially have any number of wsgi
processes being in a persistent erroneous state due to them being started
up in that window where the DB was down.
--
Ticket URL: <https://code.djangoproject.com/ticket/24523#comment:5>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.32ed362cc6b9b329f5798984b089be2c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
