Skip to content

[dotnet watch] Fix target framework selector being stuck #53675

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Merged
jonathanpeppers merged 1 commit into from
Apr 2, 2026
Merged

[dotnet watch] Fix target framework selector being stuck #53675

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 4 additions & 9 deletions src/Dotnet.Watch/dotnet-watch/UI/SpectreBuildParametersSelectionPrompt.cs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -74,15 +74,10 @@ internal static string FormatDevice(DeviceInfo device)

private static IAnsiConsole CreateConsole(IConsole watchConsole)
{
if (!Console.IsInputRedirected)
{
return AnsiConsole.Console;
}

// When stdin is redirected (e.g. in integration tests), Spectre.Console detects
// non-interactive mode and refuses to prompt. Create a console with forced
// interactivity that reads keys from IConsole.KeyPressed (fed by
// PhysicalConsole.ListenToStandardInputAsync).
// Always read keys from IConsole.KeyPressed (fed by PhysicalConsole) instead of
// letting Spectre.Console call Console.ReadKey() directly. PhysicalConsole already
// owns the Console.ReadKey() loop, so a second reader would race with it and never
// receive any key presses, making the selection prompt appear stuck.
var ansiConsole = AnsiConsole.Create(new AnsiConsoleSettings
{
Ansi = AnsiSupport.Yes,
Expand Down
Loading