Martin Vogel 4dd099679d fix(windows): pin the search_code PowerShell pipe to UTF-8 ...

PowerShell 5.1 encodes stdout for a native-process pipe in the console
OEM codepage, so raw search content containing characters the inherited
CP cannot carry (Cyrillic under CP437/850, ...) reached
collect_grep_matches as '?' — and whether it degraded depended entirely
on which console the server happened to inherit. That surfaced as the
intermittent test_mcp raw-Русский mojibake on the windows CI leg and
means real Windows users in a default console get '?' for all
non-ASCII search_code raw content.

Every generated command now pins [Console]::OutputEncoding to UTF-8, so
the pipe is codepage-independent by construction. The read side needs
no pin: Select-String decodes BOM-less UTF-8 via .NET StreamReader
defaults. A Windows-side builder test asserts all five command variants
carry the prelude.

Signed-off-by: Martin Vogel <martin.vogel.tech@gmail.com>

2026-08-18 09:31:59 +02:00

..

compact_out.c

fix(mcp): guarantee valid UTF-8 in tree-format output

2026-07-27 01:05:12 +02:00

compact_out.h

feat(mcp): complete the tree-format migration — TOON pruned, json = stringified tree

2026-07-17 22:58:22 +02:00

index_supervisor.c

fix(index): make a crashed worker's log survive and name the run

2026-08-14 20:01:06 +02:00

index_supervisor.h

fix(index): make a crashed worker's log survive and name the run

2026-08-14 20:01:06 +02:00

mcp_internal.h

perf(mcp): prefilter simple suffix globs on Windows

2026-08-14 17:50:54 +03:00

mcp.c

fix(windows): pin the search_code PowerShell pipe to UTF-8

2026-08-18 09:31:59 +02:00

mcp.h

fix(mcp): keep ADR reads nonblocking

2026-07-31 11:02:01 +03:00