-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
discovery failed: bad grpc status code: The operation was cancelled #8491
Comments
I also get this error sometimes:
But after runing |
Same version, same issue:
Apparently it's not reliably reproducible, as I'm currently running watch mode without issue. I have no idea what changed. |
Interesting. Could you run watch mode with debug verbosity, i.e. add |
I see the same thing in my repo. Some notes:
Hope this helps. Thanks for your hard work |
Also with many -v's:
|
I tried with the Kodix repo from the OP and it worked on the same drive as /var and failed on my dev drive. Thats your repro I think. |
I have the very same issue with
|
I'll add that even with
And then, if I manually clean
Fwiw, non-watch commands succeed
|
Okay! Progress: It looks like So, if I add extra jobs of the form
I get the expected behaviour! (except that I get ticks for every item in the watch view) |
I believe I may have now worked around the issue by installing the Turborepo LSP extension for Visual Studio Code. I can't say for sure that's why |
I have a similar issue, but it always happens after the first run of watch command. I'm unable to reproduce that on second run, for example. |
Gotcha. I'll try to reproduce and fix these issues. I will note that If I have it correct, there's a few issues at hand here:
Is that an accurate summary? |
For mine, I am running on MacOS. When I said my "dev" drive I meant my literal other drive/partition that is mounted at |
I've run in to this fairly reliably (not consistent enough for repro though) when i leave the
My command is Which does the following in my monorepo:
If I try to run my The
Hopefully this helps a little bit |
@Cypher1 And execute |
Just experienced this; running |
@uncvrd, how long are you letting your computer sleep? We do have an inactivity timeout for the daemon, so if you're leaving watch mode open for multiple hours, it's expected that the daemon should stop. |
@NicholasLYang it would be overnight. In V1 versions of I've updated to the latest version of turbo v2.0.6 and this morning I keep randomly getting The logs from the corresponding file change show
Not sure if helpful though. really wish I could understand what triggers it but it has happened twice in the last few hours. Normally my changes are hot reloaded when updating a file but other times i get this This is the turbo
Which runs this npm script:
Okay hypothesis that might help...maybe? Since my turbo task is defined as |
So the way Nonetheless, there does seem to be an issue with the daemon either crashing or ending up in an invalid state. Continuing to investigate that... |
Hey @NicholasLYang thanks for the response! I have a previous comment above that mentions that I use No worries though let me know if there's anything i can test on my end to help |
Ah gotcha, sorry for missing that. I'm investigating the watch issues right now. Do you happen to have an open source repository that I can use to test? |
All good! Since I haven't been able to repro consistently, nothing to provide unfortunately. Sorry :/ If I can lock it down then yes, would be happy to provide a repro |
+1 for this happening intermittently as well. Hard to get a true repro since it is pretty random 😭 |
+1 from me as well. I don’t know how to reproduce it either :/ For now, I might just add the state when it happens:
|
+1 from us also. Sadly unable to find a way to reliably reproduce, but it is causing significant disruptions in our development workflow. Similar constraints that @dobrac mentioned above. If there's anything else we find out I'll add here, but for now we aren't sure what to do other than just deal with it. |
Any updates on this? |
man this is just boring |
It's so freaking annoying, let's do sth with this, pls. |
We are seeing this issue 100% of the time we run This only happens for us on a Mac case-sensitive volume. If the repo is copied to a non case-sensitive volume, this error does not occur. Looking forward to a patch for this. |
My issue is a Mac on a case sensitive volume as well |
I Have it on Windows 11 |
+1 on Mac on case-sensitive volume; works fine when copied to the system drive. |
1 similar comment
+1 on Mac on case-sensitive volume; works fine when copied to the system drive. |
+1 Having same result on Windows with WSL, and on Linux (Linux Mint 22). Using the same project in both OS. Edit: I managed to fix it. I'm using a docker compose file to spin up a db locally. I was saving the data on ./data in the same folder as the monorepo. After running docker compose up, everything broke. Running |
Next month with that error, hymm |
Hi, I am also seeing this issue in my monorepo project, if I run the turbo watch inside node:20 docker container.
Not sure why is this happening. |
Yet another +1 on MacOS case-sensitive volume. I move it to another location and works just fine. |
Verify canary release
Link to code that reproduces this issue
https://github.com/dBianchii/kodix-turbo
What package manager are you using / does the bug impact?
pnpm
What operating system are you using?
Linux
Which canary version will you have in your reproduction?
turbo 2.0.3
Describe the Bug
When trying to run
turbo watch dev -F @kdx/kdx...
for my project, I get this error:Expected Behavior
Should run the project in watch mode without any problems
To Reproduce
Clone https://github.com/dBianchii/kodix-turbo and run
pnpm dev:kdx
after runningpnpm i
Additional context
I tested it on 2.0.4-canary.4
The text was updated successfully, but these errors were encountered: