Skip to content

Fix Windows device paths and UTF-16 NUL detection - #2672

Merged
Widthdom merged 3 commits into
mainfrom
fix-issue2043-1829
May 25, 2026
Merged

Fix Windows device paths and UTF-16 NUL detection#2672
Widthdom merged 3 commits into
mainfrom
fix-issue2043-1829

Conversation

@Widthdom

Copy link
Copy Markdown
Owner

Summary

  • Skip Windows reserved device paths and names before probing or reading file contents.
  • Detect BOM-less UTF-16 LE/BE text patterns so NUL bytes from encoding do not cause binary skips or validation noise.
  • Add focused FileIndexer coverage and bilingual changelog fragments.

Validation

  • dotnet test tests/CodeIndex.Tests/CodeIndex.Tests.csproj --filter "FullyQualifiedName~FileIndexerTests" -p:UseSharedCompilation=false
  • dotnet build CodeIndex.sln -c Release -p:UseSharedCompilation=false
  • dotnet test CodeIndex.sln -c Release -p:UseSharedCompilation=false
  • dotnet ./src/CodeIndex/bin/Debug/net8.0/cdidx.dll status --check --json
  • Adversarial review: No blocking/actionable issues found.

Documentation / Changelog

  • changelog.d/unreleased/2043.fixed.md
  • changelog.d/unreleased/1829.fixed.md

Follow-up Candidates

  • None.

Fixes #2043
Fixes #1829

@Widthdom
Widthdom marked this pull request as ready for review May 25, 2026 00:34
@Widthdom
Widthdom merged commit 0edb3b2 into main May 25, 2026
10 checks passed
@Widthdom
Widthdom deleted the fix-issue2043-1829 branch May 25, 2026 00:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

1 participant