#30323: Django 2.2 autoreloader is failing intermittently (not using watchman)
---------------------------------+--------------------------------------
Reporter: Mark Chackerian | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 2.2
Severity: Normal | Resolution:
Keywords: autoreloader | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+--------------------------------------
Comment (by Tom Forbes):
Ok, this isn't good! Thanks for CCing me Carlton.
I added a fair bit of logging to the autoreloader, if anyone in this
thread could enable the `django.utils.autoreload` logger and set it's
verbosity to DEBUG and paste any logs here then that would be very, very
helpful. It smells like this might be a timestamp resolution issue of some
kind however it's really hard to tell.
Regarding your comment Sammie, are you sure you are using Watchman?
Without Watchman the file modification timestamps are polled, with
Watchman then something more efficient should be used and in theory the
timestamps are not required.
--
Ticket URL: <https://code.djangoproject.com/ticket/30323#comment:4>
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/069.6ba4ddb35bd232c139a9fa9b831520a5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
