#30323: Django 2.2 autoreloader is failing intermittently (not using watchman)
---------------------------------+------------------------------------
Reporter: Mark Chackerian | Owner: nobody
Type: Bug | Status: new
Component: Utilities | Version: 2.2
Severity: Release blocker | Resolution:
Keywords: autoreloader | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+------------------------------------
Comment (by Tom Forbes):
I will try and fix this tomorrow, but for prosperity's sake the issue as I
can see it is this: In the StatReloader.loop_files, on Windows, seems to
have a condition where all files are treated as new and for some reason
files with changed modification times are not treated as actually changed:
I have a clear debug log from a very helpful chap on IRC that clearly
shows the mtime of a file changing but not triggering as the file being
changed, which can only happen in a particularly weird set of
circumstances. I've attached the full log to the ticket.
I feel the solution is to more faithfully copy the previous stat reloader
as that seemed to work correctly, which means removing some (seemingly
premature) optimizations I tried to add.
--
Ticket URL: <https://code.djangoproject.com/ticket/30323#comment:10>
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/069.91d3b224af3bc435752b695ace8f5748%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
