Tasks getting skipped with no explanation #9277
Comments
jakeleventhal
added
kind: bug
|
Hi, thanks for the issue. What directory is |
Here is {
"name": "@riptech/app1",
"private": true,
"scripts": {
"admin": "pnpm --dir=./admin run start",
"api": "pnpm --dir=./api run start",
"client": "pnpm --dir=./client run start",
"landing": "pnpm --dir=./landing run start",
"onboard-demo": "rm -rf $(pwd)/localDBData/demoData && pnpm --dir=./api run onboard-demo",
"start": "concurrently --raw \"pnpm run start-database\" \"pnpm run client\"",
"start-admin": "concurrently --raw \"pnpm run start-database\" \"pnpm run admin\"",
"start-database": "docker-compose up --build",
"stop": "docker-compose down && killall -9 node"
}
} |
|
Thanks, just to confirm, Judging by your layout, this is likely an issue with nested workspaces. Turborepo doesn't support nested workspaces, i.e. having |
|
The directory is I don't mean for packages:
- 'apps/*'
- 'apps/*/*'
- 'packages/*/*'
- 'tools/*'If I remove even though |
|
Interesting. The behavior you described of running all packages downstream is what should happen. I'll look into that. And possibly improve the error message to show which package json it's trying to pull from |
|
Is this repository public? Or is it possible to get access to a smaller version of it without any code? |
|
My repo is private, and very large. If you're willing, I can invite you to the repo temporarily. |
|
That would be great, thanks! |
|
@NicholasLYang added you as a collaborator. We can continue discussion in this thread. |
Verify canary release
Link to code that reproduces this issue
See output
What package manager are you using / does the bug impact?
pnpm
What operating system are you using?
Mac
Which canary version will you have in your reproduction?
turbo@2.1.3
Describe the Bug
For some reason, I am getting tasks that seem to skip with no explanation. In a directory of my application
apps/app1/api, I runturbo tscand expect 15 total tasks to be ran. It seems that turbo randomly only does a subset of tasks. If I runturbo tscseveral times in a row, I randomly will get correct output:and randomly get incorrect output that does not download cached outputs:
Notably, see how it says:
I don't even have a tsc task for
@riptech/app1Expected Behavior
In all cases, I would expect all 15 tasks to run (cached).
To Reproduce
See above
Additional context
Here is my turbo.json
{ "$schema": "https://turbo.build/schema.json", "tasks": { "//#coverage": { "dependsOn": ["//#package-deps", "@riptech/lcov-merger#tsc"], "inputs": ["!**/node_modules/**", "**/coverage/lcov.info"], "outputLogs": "new-only", "outputs": ["coverage/_coverage_report.dat"] }, "//#package-deps": { "inputs": [ "!**/.next/**", "!**/dist/**", "!**/out/**", "!**/node_modules/**", ".nvmrc", "**/package.json", "pnpm-lock.yaml", "pnpm-workspace.yaml" ], "outputLogs": "new-only", "outputs": ["pnpm-lock.yaml"] }, "format": { "dependsOn": ["//#package-deps", "eslint-config-riptech#tsc"], "outputLogs": "new-only" }, "image": { "dependsOn": ["//#package-deps", "^tsc", "@riptech/docker#tsc"], "inputs": [".env*", "dist/**"], "outputLogs": "new-only" }, "image-production": { "cache": false, "dependsOn": ["//#package-deps", "^tsc", "@riptech/docker#tsc"] }, "image-staging": { "cache": false, "dependsOn": ["//#package-deps", "^tsc", "@riptech/docker#tsc"] }, "lint": { "dependsOn": ["//#package-deps", "eslint-config-riptech#tsc"], "outputLogs": "new-only" }, "pull-vercel": { "cache": false }, "test": { "dependsOn": ["//#package-deps", "@riptech/jest-config#tsc"], "outputLogs": "new-only", "outputs": ["coverage/lcov.info"] }, "tsc": { "dependsOn": ["//#package-deps", "^tsc"], "outputLogs": "new-only", "outputs": ["dist/**"] } } }The text was updated successfully, but these errors were encountered: