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
The --ignore
parameter does not take effect
#654
Comments
Try |
I've tried everything. It doesn't work. |
Also, on Win11, it doesn't work at all, typing watchexec produces nothing. |
well, i'm gonna need a log file for that |
Fairly sure I'm having the same issue. Exclude file:
Log: {"timestamp":"2023-11-16T10:28:34.439960Z","level":"INFO","fields":{"message":"action constructed","action":"Action { events: [Event { tags: [Source(Filesystem), FileEventKind(Modify(Any)), Path { path: \"C:\\\\devel\\\\laravel-demo\\\\node_modules\\\\caniuse-lite\\\\data\\\\features\\\\mdn-text-decoration-shorthand.js\", file_type: Some(File) }], metadata: {} }], outcome: OnceCell(Uninit) }"},"target":"watchexec::action::worker"}
{"timestamp":"2023-11-16T10:28:34.440936Z","level":"INFO","fields":{"message":"outcome resolved","outcome":"Both(Wait, Start)"},"target":"watchexec::action::worker"}
{"timestamp":"2023-11-16T10:28:35.445059Z","level":"INFO","fields":{"message":"action constructed","action":"Action { events: [Event { tags: [Source(Filesystem), FileEventKind(Modify(Any)), Path { path: \"C:\\\\devel\\\\laravel-demo\\\\node_modules\\\\effect\\\\dist\\\\cjs\\\\Exit.js\", file_type: Some(File) }], metadata: {} }], outcome: OnceCell(Uninit) }"},"target":"watchexec::action::worker"}
{"timestamp":"2023-11-16T10:28:35.446084Z","level":"INFO","fields":{"message":"outcome resolved","outcome":"Both(Wait, Start)"},"target":"watchexec::action::worker"} Technically these files shouldn't trigger in the first place, because they do not change, but I'm going to blame that part on Windows. In any case the ignore file should have caught these. |
cool, still need a logfile (at debug or trace level) |
Sure. This time I had to provoke it via changing an ignored file as whatever is triggering it doesn't want to do it today (further suggesting that part is Windows' fault). |
Hmm. I wonder if something changed out from under me and isn't respecting windows paths anymore. Does it change if you do e.g. |
No, unfortunately it does not. |
watchexec -i "target/**" make test
Invalid filtering, still monitors files in the target directory for changes.
The text was updated successfully, but these errors were encountered: