Skip to content
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

Infinite watch loop on Windows #133

Closed
torhovland opened this issue Feb 23, 2021 · 1 comment · Fixed by #134
Closed

Infinite watch loop on Windows #133

torhovland opened this issue Feb 23, 2021 · 1 comment · Fixed by #134

Comments

@torhovland
Copy link

I'm getting the infinite watch loop decribed in #84 and #99. My setup is:

Windows 10 Build 19042.804.

rustup-init using the following defaults:

default host triple: x86_64-pc-windows-msvc
default toolchain: stable (default)
profile: default
modify PATH variable: yes

Visual Studio 2019 - 16.8.6, with the C++ desktop development workload.

rustup target add wasm32-unknown-unknown
cargo install --locked trunk
cargo install wasm-bindgen-cli

At this point I have:

rustup 1.23.1 (3df2264a9 2020-11-30)
rustc 1.50.0 (cb75ad5db 2021-02-10)
cargo 1.50.0 (f04e7fab7 2021-02-04)
wasm-bindgen 0.2.70
trunk 0.8.2

Running trunk watch on either trunk/examples/seed or trunk/examples/yew yields the infinite watch loop.

@torhovland
Copy link
Author

I did some debug logging in here:

        if ev_path
            .ancestors()
            .any(|path| self.ignored_paths.iter().any(|ignored_path| { 
                if ignored_path == path {
                    self.progress.println(format!("Ignored {:?}", path));
                } else {
                    self.progress.println(format!("{:?} !== {:?}", ignored_path, path));
                }
                ignored_path == path }))
        {
            return; // Don't emit a notification if path is ignored.
        }

I found this:

Handling Write("\\\\?\\C:\\Projects\\trunk\\examples\\seed\\target\\wasm-bindgen\\debug\\index-88a2d670d6306bab_bg.wasm")
"\\\\?\\C:\\Projects\\trunk\\examples\\seed\\dist" !== "\\\\?\\C:\\Projects\\trunk\\examples\\seed\\target\\wasm-bindgen\\debug\\index-88a2d670d6306bab_bg.wasm"
"C:\\Projects\\trunk\\examples\\seed\\target" !== "\\\\?\\C:\\Projects\\trunk\\examples\\seed\\target\\wasm-bindgen\\debug\\index-88a2d670d6306bab_bg.wasm"
"\\\\?\\C:\\Projects\\trunk\\examples\\seed\\dist" !== "\\\\?\\C:\\Projects\\trunk\\examples\\seed\\target\\wasm-bindgen\\debug"
"C:\\Projects\\trunk\\examples\\seed\\target" !== "\\\\?\\C:\\Projects\\trunk\\examples\\seed\\target\\wasm-bindgen\\debug"
"\\\\?\\C:\\Projects\\trunk\\examples\\seed\\dist" !== "\\\\?\\C:\\Projects\\trunk\\examples\\seed\\target\\wasm-bindgen"
"C:\\Projects\\trunk\\examples\\seed\\target" !== "\\\\?\\C:\\Projects\\trunk\\examples\\seed\\target\\wasm-bindgen"
"\\\\?\\C:\\Projects\\trunk\\examples\\seed\\dist" !== "\\\\?\\C:\\Projects\\trunk\\examples\\seed\\target"
"C:\\Projects\\trunk\\examples\\seed\\target" !== "\\\\?\\C:\\Projects\\trunk\\examples\\seed\\target"
"\\\\?\\C:\\Projects\\trunk\\examples\\seed\\dist" !== "\\\\?\\C:\\Projects\\trunk\\examples\\seed"
"C:\\Projects\\trunk\\examples\\seed\\target" !== "\\\\?\\C:\\Projects\\trunk\\examples\\seed"
"\\\\?\\C:\\Projects\\trunk\\examples\\seed\\dist" !== "\\\\?\\C:\\Projects\\trunk\\examples"
"C:\\Projects\\trunk\\examples\\seed\\target" !== "\\\\?\\C:\\Projects\\trunk\\examples"
"\\\\?\\C:\\Projects\\trunk\\examples\\seed\\dist" !== "\\\\?\\C:\\Projects\\trunk"
"C:\\Projects\\trunk\\examples\\seed\\target" !== "\\\\?\\C:\\Projects\\trunk"
"\\\\?\\C:\\Projects\\trunk\\examples\\seed\\dist" !== "\\\\?\\C:\\Projects"
"C:\\Projects\\trunk\\examples\\seed\\target" !== "\\\\?\\C:\\Projects"
"\\\\?\\C:\\Projects\\trunk\\examples\\seed\\dist" !== "\\\\?\\C:\\"
"C:\\Projects\\trunk\\examples\\seed\\target" !== "\\\\?\\C:\\"
Not ignored.

So the problem seems to be this inequality:

"C:\\Projects\\trunk\\examples\\seed\\target" !== "\\\\?\\C:\\Projects\\trunk\\examples\\seed\\target"

torhovland pushed a commit to torhovland/trunk that referenced this issue Feb 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant