I submitted a bug report and am working on a patch:
https://code.djangoproject.com/ticket/30361
Also, it appears that some fixes to the StatReloader may be coming in 2.2.1
(or 2.3?) which could also help
On Thursday, April 11, 2019 at 3:34:27 PM UTC-7, ja...@workflowy.com wrote:
>
> After more
After more research, I noticed that Django is using the default timeout of
1sec for the pywatchman client. When I try running the watch with a higher
timeout, I am able to start it successfully.
I would suggest that Django makes the timeout configurable, or chooses a
higher default value.
On W
We have noticed the same thing. StatReloader is very unreliable (over
docker) and Watchman timed out. I'm gonna try tweaking the Watchman config
settings but it was the first time I have upgraded Django and had anything
less than a perfectly smooth experience
On Wednesday, April 10, 2019 at 5:0
Since the introduction to Watchman, with the failover to StatReloader, the
file changes aren't picked up.
We're running our Django development environment in Docker/Docker-compose,
and 2.1.7 everything is still fine. But updating to 2.2.0, the file changes
aren't picked up (or rarely).
We have
4 matches
Mail list logo
