Skip to content

Fix native parser portability on Windows - #4

Draft
ajhcs wants to merge 1 commit into
mainfrom
codex/cse-windows-portability-20261018
Draft

ajhcs wants to merge 1 commit into
mainfrom
codex/cse-windows-portability-20261018

Conversation

@ajhcs

@ajhcs ajhcs commented Oct 18, 2026 •

Copy link
Copy Markdown
Owner

Native parser checks failed on Windows because the adapter imported POSIX-only locking, used a POSIX classpath, and assumed Java output was UTF-8. Use nonblocking Windows byte-range or POSIX file locks, the platform classpath separator, and explicit UTF-8 byte transport. Missing or malformed output now returns a structured parser error. Lock acquisition and Java execution retain one timeout budget.

Add contention, exception/timeout recovery, Unicode and malformed-transport coverage, plus required-native CI on Ubuntu and Windows with Python 3.10/3.12 and Java 21. Windows checkout link records remain intact; launcher tests use the real skill directories when links are unavailable. The existing alpha scope remains three drafting skills sharing the pinned parser; project discovery and global installation require separate qualification.

Validation: Linux required-native suite passed 247 tests across 18 suites with no skips. Actual Windows qualification passed the same 247 tests, 12 focused portability tests and five launcher tests on Python 3.13.6 / Temurin 21.0.11, including a space/Unicode path. Independent code reviews found no remaining actionable findings. Optional helper checks also passed without Java, with the two native tests skipped.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant