[turborepo] Cannot start turbo build on macos m1

[polRk]

What version of Turborepo are you using?

1.7.0-canary.7

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

npm, pnpm

What operating system are you using?

Mac

Describe the Bug

RUST_BACKTRACE=1 turbo build
thread 'main' panicked at 'Failed to execute turbo.: Os { code: 2, kind: NotFound, message: "No such file or directory" }', crates/turborepo/src/main.rs:21:10
stack backtrace:
   0: _rust_begin_unwind
   1: core::panicking::panic_fmt
   2: core::result::unwrap_failed
   3: turbo::main
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

Expected Behavior

Works fine.

To Reproduce

pnpm install turbo --global
turbo build

Reproduction Repo

No response

[tknickman]

Hey @polRk! Thanks for helping us test out the canaries!

We have a stable 1.7.0 out now that I would recommend switching to that should fix this issue.

You can grab it with:

pnpm install turbo@latest --global

If you'd like to stay on the bleeding edge, we have a 1.7.1 canary out that should fix this and also be pretty stable. Try that one out with:

pnpm install turbo@canary --global

[vinassefranche]

Hi @tknickman !

I have the same issue with the 1.7.1 while I did not have it with the 1.7.0. Should we stick to the 1.7.0 for a while or is there something we can do to fix it?

Thanks in advance for your answer!

[tknickman]

Hey, got it thanks @vinassefranche. So installing globally isn't working with turbo@canary, but it is working with turbo@latest?

[vinassefranche]

It's installed with yarn in a project.

With "turbo": "^1.7.0", in our package.json, it works fine but I have the same error message as mentioned in this issue if I set it to "turbo": "^1.7.1",

[vinassefranche]

I just tested with yarn add -D turbo@latest and yarn add -D turbo@canary and it does not work in both case. It only works if I set the version to be 1.7.0

[vinassefranche]

Sorry, I'm completely wrong on the versions 😞
It works fine with 1.6.3 but not with any 1.7.X version

[vinassefranche]

I've tried to reproduce the issue on small repo and it seems like the issue is linked to our use of yarn's plug and play. With version 1.7.0:

• If I set nodeLinker: node-modules in my yarn config file, I don't have the issue.
• If I set nodeLinker: pnp in my yarn config file, I have the issue.

[mehulkar]

I've tried to reproduce the issue on small repo

Could you push this up somewhere so someone from the team can try to repro?

[vinassefranche]

Here it is: https://github.com/vinassefranche/turbo-issue-with-pnp/tree/main
The steps to reproduce are in the repository's readme

[tknickman]

Hey @vinassefranche thanks for the repro! Unfortunately we don't officially support the pnp linker, we only support node-modules as of now.

That being said, we have another issue tracking this, so I'm going to close this one only to consolidate reports.

Duplicate of #3280

[vinassefranche]

Hi @tknickman,
Thanks for looking at this! I'll subscribe to the other issue then.