We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The output of turbo info: turbo info turbo 2.3.3 CLI: Version: 2.3.3 Path to executable: ....\node_modules\turbo-windows-64\bin\turbo.exe Daemon status: Not running Package manager: berry Platform: Architecture: x86_64 Operating system: windows WSL: false Available memory (MB): 35060 Available CPU cores: 24 Environment: CI: None Terminal (TERM): unknown Terminal program (TERM_PROGRAM): unknown Terminal program version (TERM_PROGRAM_VERSION): unknown Shell (SHELL): unknown stdin: false Note that I'm running the command from a Windows Powershell terminal, but CMD has the same behavior too. The command being used to invoke turbo: turbo run preview How the signal is being sent to turbo: Ctrl+C on the terminal window If it helps, below is the process hierarchy, see the dangling processes: Hope it helps @chris-olszewski
turbo info turbo 2.3.3 CLI: Version: 2.3.3 Path to executable: ....\node_modules\turbo-windows-64\bin\turbo.exe Daemon status: Not running Package manager: berry Platform: Architecture: x86_64 Operating system: windows WSL: false Available memory (MB): 35060 Available CPU cores: 24 Environment: CI: None Terminal (TERM): unknown Terminal program (TERM_PROGRAM): unknown Terminal program version (TERM_PROGRAM_VERSION): unknown Shell (SHELL): unknown stdin: false
Note that I'm running the command from a Windows Powershell terminal, but CMD has the same behavior too.
turbo run preview
If it helps, below is the process hierarchy, see the dangling processes:
Hope it helps @chris-olszewski
Originally posted by @erhan-talarian in #9694
The text was updated successfully, but these errors were encountered:
SIGINT
turbo
@erhan-talarian I think I'm able to reproduce on my Windows machine. Just a few follow ups:
--ui=stream
yarn run preview
"preview": "turbo run preview"
Ctrl-C
Sorry, something went wrong.
Hey @chris-olszewski
tui
@erhan-talarian Could you show the process tree once turbo has exited via a Ctrl-C press?
I'm having the same issue. Here are my process trees:
Before:
On CTRL+C I managed to capture this (the PIDs are different than previous screenshot as it was a different run):
All that is left in the tree afterwards is pwsh.exe:
pwsh.exe
The other processes are now on their own without a parent:
Let me know if you need me to run/try something else, I've been having this issue for a while so I'm keen to get it resolved.
No branches or pull requests
Originally posted by @erhan-talarian in #9694
The text was updated successfully, but these errors were encountered: