Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Changes to source files are not reflected in the browser from v0.55.6 on #6308
Please see this thread https://discourse.gohugo.io/t/live-reload-broken/20584 for all relevant details, in particular this section https://discourse.gohugo.io/t/live-reload-broken/20584/6
I assume it's this commit: 95ce2a4 ...
I can see how the above commit would block (wait) for the previous build to fail and make it "feel" like the live reload isn't working. I think I've experienced something similar myself.
The thing is:
In fast render mode the above should not be something that should happen very often.
@christophlieck can you somehow confirm my theory above. I.e. try to:
Before 95ce2a4 we would just trigger these rebuilds in parallell, which made them feel snappier to the end user, but you had some weird and undefined side effects.
I think we need to do 2 things:
Apologies, but I'm afraid I've to update this issue again: After having returned to productive work with 0.55.5 it turned out that it is also unstable once updating the browser once not.
To fix this I rolled back to the last version before the commit quoted above, e. g. v0.54.0-B1A82C61 darwin/amd64 BuildDate: 2019-02-01T09:40:48Z which seems to work fine so far.
I therefore now second you suspecting commit 95ce2a4.