-
Notifications
You must be signed in to change notification settings - Fork 2k
Closed
Labels
kind: bugSomething isn't workingSomething isn't workingneeds: triageNew issues get this label. Remove it after triageNew issues get this label. Remove it after triage
Description
Verify canary release
- I verified that the issue exists in the latest Turborepo canary release.
Link to code that reproduces this issue
https://github.com/IanMitchell/summarize-colon-missing-logfile
Which canary version will you have in your reproduction?
turbo@2.4.1-canary.0
Enviroment information
CLI:
Version: 2.4.1-canary.0
Path to executable: /Users/ian/Developer/summarize-colon-missing-logfile/node_modules/turbo-darwin-arm64/bin/turbo
Daemon status: Running
Package manager: npm
Platform:
Architecture: aarch64
Operating system: macos
WSL: false
Available memory (MB): 13660
Available CPU cores: 14
Environment:
CI: None
Terminal (TERM): xterm-256color
Terminal program (TERM_PROGRAM): vscode
Terminal program version (TERM_PROGRAM_VERSION): 1.96.4
Shell (SHELL): /opt/homebrew/bin/fish
stdin: false
Expected behavior
The task log file packages/pkg-a/.turbo/turbo-colon$colon$command.log
should exist
Actual behavior
There is no .turbo
directory and no log file
To Reproduce
In the linked repro repository, run npm run colon:command
Additional context
While I am unsure if the $colon$
ultimately is responsible, other commands create the associated log files.
Metadata
Metadata
Assignees
Labels
kind: bugSomething isn't workingSomething isn't workingneeds: triageNew issues get this label. Remove it after triageNew issues get this label. Remove it after triage