-
Notifications
You must be signed in to change notification settings - Fork 956
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"zola serve" doesn't detect any change #2551
Comments
We've fixed it for Linux but for Windows I'd need someone with a Windows machine to check what's happening. See #2542 for the linux PR |
I'm seeing this in Mac as well (no changes result in a reload, even to templates or pages or anything), but maybe the linux fix will also fix that. |
Have you tried 0.19.1? It has always worked for me on Mac |
Tried According to devtools the websocket is being established ( Most recent release with working live reload on my system seems to be |
I was already on 0.19.1, but it started working with no changes, so idek. I've historically seen mac's do weird things with reloading dev server file detection before, so probably not anything on your end. Just following up to confirm I am not seeing this behavior on Mac, so ignore my earlier comment I guess. Maybe a permissioning hiccup or something on one of my installs. |
I also ran into this issue, I just installed it yesterday. Not that I'm 100% sure if it's related but it's showing the path and I'm curious if it's maybe related to the issue. I'm using 0.19.1
For me it's not catching any changes, templates, content anything. My path: But it's listing the path as: The full output:
Edit: Nevermind, I checked |
I'm also seeing this with Zola 0.19.1 currently. |
Can you try #2575 ? |
@Keats That seems to work for me. Version shows me using 0.19.1 PS D:\Workspace\Rust\snowdrama_dot_net_zola> zola.exe -V
zola 0.19.1 And this does correctly reload when an update is made PS D:\Workspace\Rust\SnowdramaDotNetZola> zola.exe serve
Building site...
Checking all internal links with anchors.
> Successfully checked 16 internal link(s) with anchors.
-> Creating 8 pages (1 orphan) and 12 sections
Done in 3.0s.
Web server is available at http://127.0.0.1:1111 (bound to 127.0.0.1:1111)
Listening for changes in \\?\D:\Workspace\Rust\snowdrama_dot_net_zola\{config.toml,content,sass,static,templates,themes}
Press Ctrl+C to stop
Change detected @ 2024-07-18 12:22:07
-> Content changed \\?\D:\Workspace\Rust\snowdrama_dot_net_zola\content\devlog\2024\07\test.md
Checking all internal links with anchors.
> Successfully checked 16 internal link(s) with anchors.
-> Creating 8 pages (1 orphan) and 12 sections
Done in 329ms. |
Nice, now let's see if it works for @chipotle as well. Which editor are you using? |
I'm using zola 0.19.1 on macOS 14.1.1, |
@opeik , I can reproduce that on macOS. Did your workflow used to work for you using zola 0.18? I took a look at the |
@iamorphen I don't think it's ever worked. |
@opeik , thanks for confirming. I couldn't find any special mention of symlinks in the older version of notify-rs (4.x) we used, either. I just confirmed that your use case works on Linux, so this behavior seems to be a quirk between macOS's FSEvents and the notify/debouncer crate. |
@Keats I've tested that PR and it fixes it when I save files in VS Code on Windows 10. I hope that can be merged and released ASAP. Thanks. |
Confirming that As mentioned in the #2575, while |
Can you open another issue for that? I haven't seen it on Mac so it would helpful to have someone on Windows debug it |
Bug Report
Environment
Zola version: 0.19.1, 0.19.0
Windows 11 22H2, Build version: 22621.3737
Expected Behavior
Using "zola serve" command, it should detect changes to a website and reflect it.
Current Behavior
In both 0.19.0 and 0.19.1 it can't detect any changes anymore, so I have to rerun "zola serve" every time I make any changes in my website code. In the terminal it's always at the initial "Listening for changes".
Step to reproduce
Note
I tried it in Windows Terminal, Powershell and the old command prompt. I tried running as admin too.
The text was updated successfully, but these errors were encountered: