Change detected, rebuilding site. Issue

support
1

Continuing the discussion from Anybody else getting a lot of unnecessary "Change detected, rebuilding site."?:

Hi there,

This is the most annoying issue with Hugo. I’ve been dealing with it for months, but always simply let it rebuild. However, since the latest upgrade it has gone mad. It is rebuilding so quickly that I am unable to properly scroll down a page.

I have deactivated all extensions in VSC. I am using the latest Hugo version: v0.99.1+extended darwin/amd64 and the latest go version: go version go1.18.2 darwin/amd64

This problem does not affect all Hugo projects, but only a few; there are no node modules, only Hugo modules. Please offer a solution to this problem. It was once uncommon, but today it’s out of hand.

I can confirm it is not happening on all computers not happening for all projects even with the exact same copy. But hugo is not able to provide an error or notification to what is going on and why it is rebuilding so quickly and what are those changes hugo is detecting while i am not toucing any files at all.

Thanks

Environment: "development"
Serving pages from memory
Running in Fast Render Mode. For full rebuilds on change: hugo server --disableFastRender
Web Server is available at http://localhost:1313/ (bind address 127.0.0.1)
Press Ctrl+C to stop

Change detected, rebuilding site.
2022-05-20 14:20:49.027 +0300
Rebuilt in 1623 ms

Change detected, rebuilding site.
2022-05-20 14:20:54.527 +0300
Rebuilt in 1502 ms

Change detected, rebuilding site.
2022-05-20 14:20:59.529 +0300
Rebuilt in 1433 ms

Change detected, rebuilding site.
2022-05-20 14:21:05.028 +0300
Rebuilt in 1326 ms

Change detected, rebuilding site.
2022-05-20 14:21:10.028 +0300
Rebuilt in 963 ms

Change detected, rebuilding site.
2022-05-20 14:21:15.528 +0300
Rebuilt in 1161 ms

Change detected, rebuilding site.
2022-05-20 14:21:20.528 +0300
Rebuilt in 1378 ms

Change detected, rebuilding site.
2022-05-20 14:21:26.028 +0300
Rebuilt in 1248 ms

Change detected, rebuilding site.
2022-05-20 14:21:31.528 +0300
Rebuilt in 1244 ms

Change detected, rebuilding site.
2022-05-20 14:21:36.528 +0300
Rebuilt in 1458 ms

Change detected, rebuilding site.
2022-05-20 14:21:42.029 +0300
Rebuilt in 93382 ms

Change detected, rebuilding site.
2022-05-20 14:23:17.415 +0300
Rebuilt in 1837 ms

Change detected, rebuilding site.
2022-05-20 14:23:35.032 +0300
Rebuilt in 2172 ms

Change detected, rebuilding site.
2022-05-20 14:23:40.535 +0300
Rebuilt in 1941 ms

Change detected, rebuilding site.
2022-05-20 14:30:09.545 +0300
hugo: collected modules in 1516 ms
Rebuilt in 3390 ms

Change detected, rebuilding site.
2022-05-20 14:30:17.544 +0300
Rebuilt in 1793 ms

Change detected, rebuilding site.
2022-05-20 14:30:22.544 +0300
Rebuilt in 1914 ms

Change detected, rebuilding site.
2022-05-20 14:30:28.045 +0300
Rebuilt in 1997 ms

Change detected, rebuilding site.
2022-05-20 14:30:33.044 +0300
Rebuilt in 1841 ms

Change detected, rebuilding site.
2022-05-20 14:30:38.545 +0300
Rebuilt in 1734 ms

Change detected, rebuilding site.
2022-05-20 14:30:43.545 +0300
Rebuilt in 1793 ms

Change detected, rebuilding site.
2022-05-20 14:30:49.045 +0300
2

I found this thread via Google and to save time for other people;

What worked was for me was the StackOverflow work-around, that is, to disable git.autorefresh in vscode settings.

Downside is that you need to press the refresh button to see the unstaged changes in the git view of vscode.

I didn’t have this problem on another computer with git.autorefresh enabled. Just my new MBP.