Closed steveluscher closed 8 months ago
Hey @steveluscher, thanks for reporting this. Can you tell me more about your OS (version, arch etc.)?
Also, please try passing --no-daemon
to turbo build
Sure thing, @tknickman!
$ uname -a
Linux HOSTNAME 5.4.0-81-generic #91-Ubuntu SMP Thu Jul 15 19:09:17 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
Adding --no-daemon
had no effect. :(
I also have this issue and am receiving the same error message along with:
"Failed to check if we can skip restoring outputs for cms#build: rpc error: code = Unknown desc = timed out waiting for cookie."
"Failed to mark outputs as cached for frontend#build: rpc error: code = Unknown desc = timed out waiting for cookie"
This is making one of the major benefits of TurboRepo invalid.
I also tried --no-daemon and it made no difference
I also see this issue - just sprung up out of nowhere in the middle of a session. It had been working for hours before.
I'm on Windows:
bash ❯ uname -a
MINGW64_NT-10.0-19045 devbox 3.3.6-341.x86_64 2022-09-05 20:28 UTC x86_64 Msys
bash ❯ pnpm exec turbo --version
1.7.0
Turbo seems to be working just fine but I get the same errors, or rather - messages.
Turbo 1.8.8 Windows 11
Windows 10 here. Same messages but it works for running tests and tsc. Using --no-daemon made the error messages go away.
I have turbo installed globally and locally in my project
I first started running dev tasks for nextjs and vite/react and got a error about not being able to connect to the process. The message told me to run turbo daemon clean so I had to install turbo globally and then because it was open/locked by the local turbo, I had to manually delete the turbo .pid file.
Everything runs a lot faster with --no-daemon . So I guess it's all a timing issue with my OS?
Hey, folks! I'm seeing that this issue has been inactive for quite some time. If you're still seeing this, please give us a comment here and we can re-open it. Thank you!
What version of Turborepo are you using?
1.6.3
What package manager are you using / does the bug impact?
pnpm
What operating system are you using?
Linux
Describe the Bug
Outputs don't get saved in my team's remote cache.
Expected Behavior
turbo a b c
rm -rf node_modules/.cache/turbo
turbo a b c
againExpected remote artifacts to be downloaded and full turbo mode to be achieved.
To Reproduce
turbo -vvv --remote-only a b c
Observe ‘timed out waiting for cookie’ failure to cache in logs:
Reproduction Repo
https://github.com/solana-labs/solana