Opened 3 years ago

Closed 3 years ago

Last modified 3 years ago

#33266 closed Bug (needsinfo)

Auto-reload not detecting changes in Django 3.2 — at Version 3

Reported by: Brian Salcedo Owned by: nobody
Component: Core (Other) Version: 3.2
Severity: Normal Keywords:
Cc: Tom Forbes Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description (last modified by Abdul Rehman)

I have tried using both StatReloader and WatchmanReloader, and runserver will not detect changes and reload. Other Django projects 3.1.x or below on the same machine reload, but not reloading in Django 3.2.

For reproduction:
Python version: 3.9.7
Django version: 3.2.9
Also Getting The Same Issue on django: 3.2.8
Arch: x86_64
OS: Arch Linux
Kernel: 5.14.16-hardened1-1-hardened (package: linux-hardened)
Filesystem: /dev/mapper/vg0-root on / type btrfs (rw,relatime,compress=zstd:3,ssd,space_cache,subvolid=5,subvol=/)

Change History (3)

comment:1 by Brian Salcedo, 3 years ago

Description: modified (diff)

comment:2 by Mariusz Felisiak, 3 years ago

Cc: Tom Forbes added
Resolution: → needsinfo
Status: new → closed

Hi, I don't think you've explained the issue in enough detail to confirm a bug in Django. Please reopen the ticket if you can debug your issue and provide details about why and where Django is at fault. A sample project would be helpful.

comment:3 by Abdul Rehman, 3 years ago

Description: modified (diff)
Note: See TracTickets for help on using tickets.
Back to Top