Anyone experiencing dependsOn to cause their script to fail?

[kasir-barati]

I have a fairly simple setup, scriptA depends on scriptB and scriptC. And scriptB, and scriptC on their own runs just fine but when I add them as dep for scriptA it fails with this error msg:

nx prisma-seed todo-backend --verbose

 NX   Running target prisma-seed for project todo-backend and 2 tasks it depends on:

—————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————

> nx run todo-backend:prisma-push


> nx run todo-backend:prisma-generate

                                     Error: Operation not permitted (os error 1)
                                                                                    at PseudoTerminal.fork (/home/kasir/projects/graphql/.nx/installation/node_modules/nx/src/tasks-runner/pseudo-terminal.js:42:73)
                                                                                          at ForkedProcessTaskRunner.forkProcessWithPseudoTerminal (/home/kasir/projects/graphql/.nx/installation/node_modules/nx/src/tasks-runner/forked-process-task-runner.js:140:45)
                at ForkedProcessTaskRunner.forkProcess (/home/kasir/projects/graphql/.nx/installation/node_modules/nx/src/tasks-runner/forked-process-task-runner.js:126:25)
                                                  at TaskOrchestrator.runTaskInForkedProcess (/home/kasir/projects/graphql/.nx/installation/node_modules/nx/src/tasks-runner/task-orchestrator.js:304:54)
                                                                               at TaskOrchestrator.applyFromCacheOrRunTask (/home/kasir/projects/graphql/.nx/installation/node_modules/nx/src/tasks-runner/task-orchestrator.js:287:61)
                                                                                                             at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
                                                                at async TaskOrchestrator.executeNextBatchOfTasksUsingTaskSchedule (/home/kasir/projects/graphql/.nx/installation/node_modules/nx/src/tasks-runner/task-orchestrator.js:85:13)
                                                                                                                    at async Promise.all (index 1)
                        at async TaskOrchestrator.run (/home/kasir/projects/graphql/.nx/installation/node_modules/nx/src/tasks-runner/task-orchestrator.js:61:9)
                                      at async defaultTasksRunner (/home/kasir/projects/graphql/.nx/installation/node_modules/nx/src/tasks-runner/default-tasks-runner.js:51:16) {
                                                      code: 'GenericFailure'
                                                                            }

>  Pushing Database 

[command]/home/kasir/.local/share/pnpm/pnpm exec prisma db push --schema=/home/kasir/projects/graphql/apps/todo-backend/prisma/schema.prisma
Prisma schema loaded from apps/todo-backend/prisma/schema.prisma
Datasource "db": PostgreSQL database "todo", schema "public" at "localhost:5432"

The database is already in sync with the Prisma schema.

✔ Generated Prisma Client (v5.19.0) to ./node_modules/.pnpm/@[email protected].
[email protected]/node_modules/@prisma/client in 109ms


—————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————

 NX   Running target prisma-seed for project todo-backend and 2 tasks it depends on failed

Failed tasks:

- todo-backend:prisma-generate

Hint: run the command with --verbose for more details.

And when I do as it hints (run nx prisma-generate todo-backend --verbose) I get the following logs which in my book indicates it did generated the types for me successfully and in reality it is:

> nx run todo-backend:prisma-generate


>  Generating Client 

[command]/home/kasir/.local/share/pnpm/pnpm exec prisma generate --schema=/home/kasir/projects/graphql/apps/todo-backend/prisma/schema.prisma
Prisma schema loaded from apps/todo-backend/prisma/schema.prisma

✔ Generated Prisma Client (v5.19.0) to ./node_modules/.pnpm/@[email protected][email protected]/node_modules/@prisma/client in 103ms

Start by importing your Prisma Client (See: http://pris.ly/d/importing-client)

Tip: Want real-time updates to your database without manual polling? Discover how with Pulse: https://pris.ly/tip-0-pulse


—————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————

 NX   Successfully ran target prisma-generate for project todo-backend



 NX   Nx detected a flaky task

  todo-backend:prisma-generate

Flaky tasks can disrupt your CI pipeline. Automatically retry them with Nx Cloud. Learn more at https://nx.dev/ci/features/flaky-tasks

And the other script:

> nx run todo-backend:prisma-push


>  Pushing Database 

[command]/home/kasir/.local/share/pnpm/pnpm exec prisma db push --schema=/home/kasir/projects/graphql/apps/todo-backend/prisma/schema.prisma
Prisma schema loaded from apps/todo-backend/prisma/schema.prisma
Datasource "db": PostgreSQL database "todo", schema "public" at "localhost:5432"

The database is already in sync with the Prisma schema.

✔ Generated Prisma Client (v5.19.0) to ./node_modules/.pnpm/@[email protected].
[email protected]/node_modules/@prisma/client in 116ms


—————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————

 NX   Successfully ran target prisma-push for project todo-backend

Any idea?