turbo icon indicating copy to clipboard operation
turbo copied to clipboard

[turborepo] Error: `timed out waiting for cookie`

Open thany opened this issue 2 years ago • 5 comments

What version of Turborepo are you using?

1.7.4

What package manager are you using / does the bug impact?

npm

What operating system are you using?

Windows

Describe the Bug

First of all, the starter guide instructs to execute turbo build but the command turbo doesn't exist. And no amount of saying so in the starter guide will make it come into existence 😘

I you want people to have the turbo command available, instruct to install it globally, or change the documentation to not require it, please.

Other than that, when I carry on by executing npm run build instead, it outputs what feels like a problem.

docs:build: Failed to mark outputs as cached for docs#build: rpc error: code = Unknown desc = timed out waiting for cookie
web:build: Failed to mark outputs as cached for web#build: rpc error: code = Unknown desc = timed out waiting for cookie

Probably has to do with remote caching, but we're not using that yet. So why is it waiting for a cookie that it isn't supposed to receive in the first place??

Expected Behavior

No error. Don't do anything remote if remote cache hasn't been set up at all.

To Reproduce

Follow the starter guide. Possibly needs a clean environment. Please choose npm as the package manager.

Reproduction Repo

No response

thany avatar Feb 14 '23 13:02 thany

Experiencing the same – no remote cache set up (yet), still getting the message. 1.8.1 on macOS arm64.

I can add to the discussion that the rpc thing is happening both on start: Failed to check if we can skip restoring outputs for <repo>#<job>: rpc error: code = Unknown desc = timed out waiting for cookie. Proceeding to check cache and on end of a run: Failed to mark outputs as cached for <repo>#<job>: rpc error: code = Unknown desc = timed out waiting for cookie

Related: https://github.com/vercel/turbo/issues/2790 https://github.com/vercel/turbo/issues/2034#issuecomment-1377525355

tom2strobl avatar Feb 21 '23 09:02 tom2strobl

Error logs give the following after running turbo daemon start

timed out waiting for initial fsevents cookie: code
timed out waiting for initial fsevents cookie: filewatching failed to start

I'm on MBP M1, Ventura 13.2

chandlervdw avatar Feb 21 '23 16:02 chandlervdw

I'm building but with this bizarre notice. Turbo version 1.8.2 on a Mac. pnpm 7.26.3.

• Packages in scope: @fieldzoo/kysely-repo
• Running build in 1 packages
• Remote caching disabled
@fieldzoo/kysely-repo:build: Failed to check if we can skip restoring outputs for 
  @fieldzoo/kysely-repo#build: rpc error: code = Unknown desc = timed out waiting
  for cookie. Proceeding to check cache

 Tasks:    1 successful, 1 total
Cached:    0 cached, 1 total
  Time:    1.73s 

(I added some line breaks to make it more readable.)

If I delete all .turbo and node_modules directories, pnpm install again, then it builds without trouble.

This is happening repeatedly. I get about 5 builds in before it starts up. I'm not sure what starts it.

UPDATE: npm upgrade -g turbo eliminated the notice, despite leaving me at version 1.8.2. Don't yet know if it'll be back again.

jtlapp avatar Feb 27 '23 03:02 jtlapp

Duplicate of #2790?

steveluscher avatar May 28 '23 04:05 steveluscher

If you landed here because you started seeing WARNING messages in your turbo foo output but don't use the Daemon and scoff at the idea of polluting your package manifest with --no-daemon flags you may find your solution here:

npx turbo daemon clean

vhscom avatar Jan 30 '24 21:01 vhscom