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

[turborepo] No tasks ran #5384

Closed
WhitigolProd opened this issue Jun 26, 2023 · 6 comments
Closed

[turborepo] No tasks ran #5384

WhitigolProd opened this issue Jun 26, 2023 · 6 comments
Labels
area: windows Issues specifically reproducing on Windows kind: bug Something isn't working needs: reproduction

Comments

@WhitigolProd
Copy link

What version of Turborepo are you using?

1.10.6

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

Yarn v1

What operating system are you using?

Windows

Describe the Bug

When trying to run any tasks in any turborepo on my system except for those which were created a long time ago, no tasks run whatsoever. Even with a newly generated repo

Expected Behavior

When running yarn turbo run dev for example, I would expect turborepo to run the tasks in each of the apps/packages

To Reproduce

  1. Generate a new Turborepo with yarn create turbo
  2. Run yarn turbo run dev
  3. See the issue

I'm aware that this is very likely an issue just on my end, but I would like some pointers as to what causes this.

Reproduction Repo

No response

@WhitigolProd WhitigolProd added area: turborepo kind: bug Something isn't working needs: triage New issues get this label. Remove it after triage labels Jun 26, 2023
@WhitigolProd
Copy link
Author

Bump. Really really need this resolved. Big fork in my workflow.

@juandl
Copy link

juandl commented Jul 23, 2023

"turbo": "1.10.1" -> this version works well, but the latest version is not working, and not task detected.

@1997roylee
Copy link

same

@tknickman tknickman added the area: windows Issues specifically reproducing on Windows label Aug 22, 2023
@tknickman
Copy link
Member

Hey, this is likely an issue specific to Windows, I'm not able to reproduce on macOS.

Here's my attempt to verify in case anything jumps out that you're doing differently:

$ npx create-turbo@latest basic-turborepo yarn

>>> TURBOREPO

>>> Welcome to Turborepo! Let's get you set up with a new codebase.


Downloading files. This might take a moment.

>>> Created a new Turborepo with the following:

apps
 - apps/docs
 - apps/web
packages
 - packages/eslint-config-custom
 - packages/tsconfig
 - packages/ui

Installing packages. This might take a couple of minutes.

>>> Success! Created a new Turborepo at "basic-turborepo".
Inside that directory, you can run several commands:

  yarn run build
     Build all apps and packages

  yarn run dev
     Develop all apps and packages

  yarn run lint
     Lint all apps and packages

Turborepo will cache locally by default. For an additional
speed boost, enable Remote Caching with Vercel by
entering the following command:

  npx turbo login

We suggest that you begin by typing:

  cd basic-turborepo
  npx turbo login

$ cd basic-turborepo/
$ yarn --version
1.22.19
$ turbo --version
1.10.12
$ yarn turbo run dev
yarn run v1.22.19
$ /Users/knickman/Developer/vercel/tmp/turbo-5384/basic-turborepo/node_modules/.bin/turbo run dev
• Packages in scope: docs, eslint-config-custom, tsconfig, ui, web
• Running dev in 5 packages
• Remote caching disabled
web:dev: cache bypass, force executing 4c92f5cb8e8eef61
docs:dev: cache bypass, force executing 8c22dbf5f148788b
web:dev: $ next dev
docs:dev: $ next dev --port 3001
docs:dev: - ready started server on [::]:3001, url: http://localhost:3001
web:dev: - ready started server on [::]:3000, url: http://localhost:3000
docs:dev: - event compiled client and server successfully in 103 ms (20 modules)
web:dev: - event compiled client and server successfully in 107 ms (20 modules)
docs:dev: - wait compiling...
web:dev: - wait compiling...
web:dev: - event compiled client and server successfully in 101 ms (20 modules)
docs:dev: - event compiled client and server successfully in 118 ms (20 modules)

@mehulkar
Copy link
Contributor

Are you able to provide a reproduction that can perhaps show the issue in Github Actions windows runner? We have e2e tests that run on Windows that show that basic functionality is working.

@mehulkar mehulkar added needs: reproduction owned-by: turborepo and removed needs: triage New issues get this label. Remove it after triage labels Oct 20, 2023
@anthonyshew
Copy link
Contributor

Closing due to inactivity.

If anyone here has a reproduction on the most recent canary regarding this issue, please open a new issue and include it. Thank you!

@vercel vercel locked and limited conversation to collaborators Apr 2, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area: windows Issues specifically reproducing on Windows kind: bug Something isn't working needs: reproduction
Projects
None yet
Development

No branches or pull requests

6 participants