Hotfix v0.16.1 — KoSIT-Validator stdin auf Windows#102
Merged
Conversation
KoSIT 1.6.x prüft via FileInputStream.available() ob stdin gepiped ist. Auf Windows wirft available() für character devices (geerbtes Console-Handle, auch NUL via Stdio::null) eine IOException, die KoSIT nicht fängt — Validator bricht ab bevor ein Report geschrieben wird. Fix: stdin aus leerer regulärer Datei füttern. Disk-type-Handle ist pollbar, available() liefert 0, isPiped() wird false. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Der KoSIT-Validator wirft auf Windows
IOException: Unzulässige Funktionund bricht ab, bevor ein Report geschrieben wird. Folge: jede Validierung (Dev-Modus und Production-Build) scheitert mit „Kein Report gefunden".Ursache: KoSIT 1.6.x prüft via
FileInputStream.available()ob stdin gepiped ist (Validator.isPiped()inValidator.java:292). Auf Windows wirftavailable()für character devices — geerbtes Console-Handle und auchNULviaStdio::null()— eineIOException, die KoSIT nicht fängt.Fix: stdin aus einer leeren regulären Datei füttern. Disk-type-Handle ist pollbar,
available()liefert 0,isPiped()wird sauber false.Verifiziert mit direktem Sidecar-CLI-Aufruf gegen
01-standard-19.xml→Validation successful! Acceptable: 1.Test plan
cargo check→ clean🤖 Generated with Claude Code