Skip to content
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

[BUG] Failed to execute turbo #556

Closed
ck3d opened this issue Jul 16, 2023 · 12 comments
Closed

[BUG] Failed to execute turbo #556

ck3d opened this issue Jul 16, 2023 · 12 comments

Comments

@ck3d
Copy link

ck3d commented Jul 16, 2023

Describe the bug
I package your project in Nix and the execution of yarn build fails. This issue could be related to vercel/turborepo#3280 .
Updating turbo to version 1.8.8 could fix the issue.

To Reproduce
Execute turbo run build returns following error:

❯ turbo run --verbosity 10 build
2023-07-16T13:42:34.084+0200 [DEBUG] turborepo_lib::shim: Global turbo version: 1.7.4
2023-07-16T13:42:34.085+0200 [DEBUG] turborepo_lib::shim: Local turbo version: 1.7.4
2023-07-16T13:42:34.085+0200 [DEBUG] turborepo_lib::shim: Running local turbo binary in /home/chris/work/Flowise/node_modules/turbo/bin/turbo

2023-07-16T13:42:34.085+0200 [DEBUG] turborepo_lib::shim: supports_skip_infer_and_single_package true
thread 'main' panicked at 'Failed to execute turbo.: Os { code: 2, kind: NotFound, message: "No such file or directory" }', crates/turborepo/src/main.rs:50:10
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Expected behavior
yarn build should not fail.

Setup

  • Installation yarn build
  • Flowise Version 1.2.15
  • OS: Linux
@chungyau97
Copy link
Contributor

Hi @ck3d,

Before we proceed would like to ask you some questions

  1. What's your node version? >= 18.15.0
  2. Could you try sudo yarn build or sudo yarn build-force?

@ck3d
Copy link
Author

ck3d commented Jul 17, 2023

Sorry, here the missing information:

  1. yes, the used node version is 18.16.1
  2. sudo and build-force produces the same error

@chungyau97
Copy link
Contributor

Could you try these steps on a fresh Flowise without modifying anything:

  1. git clone https://github.com/FlowiseAI/Flowise.git
  2. yarn install or sudo yarn install
  3. yarn build or sudo yarn build
  4. yarn start or sudo yarn start

@ck3d
Copy link
Author

ck3d commented Jul 23, 2023

Based on git commit ffc8033 (after release 1.2.16) the same error occurs:#

❯ yarn build
yarn run v1.22.19
$ turbo run build
╭───────────────────────────────────────────────────────────────────────╮
│                                                                       │
│                   Update available v1.7.4 ≫ v1.10.9                   │
│    Changelog: https://github.com/vercel/turbo/releases/tag/v1.10.9    │
│                      Run "npm i turbo" to update                      │
│                                                                       │
│     Follow @turborepo for updates: https://twitter.com/turborepo      │
╰───────────────────────────────────────────────────────────────────────╯
thread 'main' panicked at 'Failed to execute turbo.: Os { code: 2, kind: NotFound, message: "No such file or directory" }', crates/turborepo/src/main.rs:50:10
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
error Command failed with exit code 101.

@trm217
Copy link

trm217 commented Aug 18, 2023

What's the current status of this?
A new initial setup of a turbo mono-repo with 'pnp' didn't work.

@chungyau97
Copy link
Contributor

Hi @trm217,

I'm not able to replicate the errors you guys are having.
image
image

cc @HenryHengZJ

@kenzik
Copy link

kenzik commented Aug 20, 2023

I had this same issue when attempting to use in OSX.

When I switched to Linux, I did not have the issue.

@chungyau97
Copy link
Contributor

Hey @kenzik,

Could you try this out?
#768 (comment)

@kenzik
Copy link

kenzik commented Aug 25, 2023

@chungyau97 - I will when I can and have some more free time.

I'm just using Linux now and have no real preference either way -- especially since it won't be deployed on a Mac.

@ck3d
Copy link
Author

ck3d commented Aug 25, 2023

Is updating of turbo not an option? It would fix this issue.

@chungyau97
Copy link
Contributor

Hey @ck3d,

We can update Turbo, but me and @HenryHengZJ don't own a Mac to test it.

You can try it on your forked repo. If it works, you can submit a PR along with some screenshots of different type of tested flow results.

@HenryHengZJ
Copy link
Contributor

should be resolved with moving to pnpm - #1272

JohnBQuinn pushed a commit to JohnBQuinn/Flowise that referenced this issue Jun 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants