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
v1.25.1 MacOS Issue: No such file or directory (os error 2) #765
Comments
I'm hitting this as well (OS X), previously worked fine. |
@schultz-is could you run with -vvvv to see if there's more of a hint as to what's up? @hlship can you describe your situation? as it seems quite specific to a single file here, I'm curious as to the commonality |
Sure thing, here you go!
|
Here's mine:
|
My workaround: added |
In my case, I'm running inside one git workspace, but some of my watched directories are in a neighboring git workspace. |
Hmm. I'll see if I can replicate that on my old macbook air as I don't really see what's happening still and need to debug in place. @schultz-is does @hlship's workaround work for you? |
Yep, it does! Thanks for that @hlship. Please let me know if I can help more in any way with debugging or repoducing, @passcod. |
I'm on ubuntu 23.10 watchexec version 1.25.1 i have a monorepo with
Runs successfully
Errors. On another computer the same directory structure and files don't give this error (ubuntu 22.04, watchexec 1.24.2) By the way it would be helpful if the error |
We don't have that kind of precise fault attribution knowledge (code-wise) but I do agree it should show which path there is no such file at. In any case your issue, and hopefully the others', seems to be a combination of the explicit watches being resolved from the project origin rather than the current directory, which I believe isn't the intent. |
I thought I'd add some context in terms of how this issue is affecting us, in case it's helpful: We use watchexec (which we love btw!) within a monorepo, where
Absolutely correct. It would be good to confirm that this is definitely not the intent! The manpage currently says the following, which suggests that paths are relative to the current path (since that's the default), but this could certainly be made more explicit.
|
Why: * This was not working correctly, possibly due to this [bug](watchexec/watchexec#765) How: * Adding an extra flag to `watchexec` so it correctly starts the process
Why: * This was not working correctly, possibly due to this [bug](watchexec/watchexec#765) How: * Adding an extra flag to `watchexec` so it correctly starts the process
I'm seeing issues running all invocations of watchexec in a certain directory with version 1.25.1, where the same invocations succeeded with version 1.25.0 and before. I'm also unable to reproduce these errors outside of the directory in question. Even simplifying the watch file list to a single extant file, replacing the command with something simple, and removing all other flags fails (e.g.
watchexec -w Makefile -- echo hello
).Watchexec version: v1.25.1 via Homebrew
OS: MacOS Sonoma 14.2.1
Error:
Error: × No such file or directory (os error 2)
Example Invocation:
watchexec --no-vcs-ignore -w cmd -w pkg -w go.mod -w go.sum -w ../../lib -- make server
Resulting Log (with
-vvv
):The text was updated successfully, but these errors were encountered: