Windows + TUI has tasks exit with code 3221225786

[chris-olszewski]

Verify canary release

• [X] I verified that the issue exists in the latest Turborepo canary release.

Link to code that reproduces this issue

Need reproduction

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

pnpm

What operating system are you using?

Windows

Which canary version will you have in your reproduction?

2.2.3

Describe the Bug

Dev tasks are exiting prematurely with exit code 3221225786 with turbo 2.2.1 and above when using the TUI

Expected Behavior

Dev tasks should not exit prematurely when using TUI

To Reproduce

See https://github.com/vercel/turborepo/issues/9304#issuecomment-2436218562

Additional context

I have version 2.2.3 of Windows 10, Powershell

https://github.com/vercel/turborepo/issues/9304#issuecomment-2432156979

[chris-olszewski]

@techwithanirudh Can you list out the following:

• OS (If using Windows, please indicate if WSL or not)
• Terminal program
• Shell
• Have you made sure your console isn't in legacy mode? (Make sure to restart your computer after changing this option to make sure the Console server gets restarted)

If anyone could provide a repository that reproduces this behavior on their machine, I would be very thankful.

[techwithanirudh]

• Operating System: Debian 12 in DevContainer
• Terminal Program: VSCode integrated terminal
• Shell: zsh
• Turbo Version: 2.2.3
• Legacy Console Mode Check: Not applicable (Debian environment)

Issue:
Running turbo dev works fine, but running turbo watch dev --continue gives the following response:

[chris-olszewski]

@techwithanirudh Do the ANSI codes only appear along when there's a failed to connect to daemon error?

[chris-olszewski]

@techwithanirudh If you could test out 2.2.4-canary.9, I believe turbo watch should do a better job of cleaning up the terminal regardless of why it exits.

[techwithanirudh]

@techwithanirudh Do the ANSI codes only appear along when there's a failed to connect to daemon error?

I think so, i'm gonna try testing the 2.2.4

Edit: Also happens with discovery failed: bad grpc status code: similar to #8491

[techwithanirudh]

@techwithanirudh If you could test out 2.2.4-canary.9, I believe turbo watch should do a better job of cleaning up the terminal regardless of why it exits.

@chris-olszewski Yeah, it did a pretty good job of cleaning up the ANSI codes.

[chris-olszewski]

Thank you for testing it out! I'll try to find what's producing that final ANSI escape sequence

[kodermax]

@chris-olszewski Is there any progress in resolving this issue, or perhaps some settings in Windows could help? However, in version 2.1.3, there was no such issue.

[chris-olszewski]

@kodermax I have still been unable to repro anything like this on my Windows machine. Searching online yields this link so that is the only guidance that I can give at the moment.