-
Notifications
You must be signed in to change notification settings - Fork 9
fix(benchmarks): remove hidden Farkas evidence cap #1333
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
morluto
merged 1 commit into
morluto:main
from
kaoru0822-kitauji:agent/harbor-integrity-pilot
Aug 13, 2026
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
2 changes: 1 addition & 1 deletion
2
benchmarks/datasets/mathematical-benchmarks-v1/exact-farkas-ldl-slice/tests/Dockerfile
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When a schema-valid evidence object contains large legal whitespace between tokens (rather than only at the beginning or end covered by the new test), this loop retains the entire prefix and reruns
raw_decodeover it after every 64 KiB read. Runtime therefore grows quadratically: a 64 MiB string/prefix already takes about 30 seconds locally, so a roughly 128 MiB artifact within the task's 4 GiB storage allowance can exceed the 120-second verifier timeout and produce no deterministic reward. Parse the bounded evidence schema incrementally, including discarding whitespace at token boundaries, so removing the unpublished byte cap does not replace it with a practical timeout cap.AGENTS.md reference: AGENTS.md:L180-L183
Useful? React with 👍 / 👎.