Skip to content

Handle binary harness judge targets#58

Closed
fazpu wants to merge 1 commit into
mainfrom
fix/harness-binary-target-metadata
Closed

Handle binary harness judge targets#58
fazpu wants to merge 1 commit into
mainfrom
fix/harness-binary-target-metadata

Conversation

@fazpu

@fazpu fazpu commented May 11, 2026

Copy link
Copy Markdown
Member

Summary

  • Render binary harness_judge target files as deterministic metadata instead of prompt content
  • Keep text target rendering and truncation behavior unchanged
  • Add a regression test proving NUL-containing targets do not place embedded NUL bytes in subprocess argv

Checks

  • uv run ruff check src tests
  • uv run pyright
  • uv run pytest tests/test_harness_judge.py tests/test_harness_judge_binary_targets.py -q
  • uv run pytest -q

Note: the local working tree also contains pre-existing unstaged gpt-5.5 model-update edits. They were preserved and are not included in this PR commit.

@fazpu fazpu force-pushed the fix/harness-binary-target-metadata branch from e5c0b39 to baf509e Compare May 11, 2026 02:56
@fazpu fazpu closed this May 11, 2026
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