Repository navigation
core: fail an any_of with a stray path instead of stopping the report - #156
Merged
Merged
Conversation
jbpros
added
bug
jbpros
force-pushed
the
core/any-of-stray-path
branch
from
October 7, 2026 17:01
b6d0408 to
674c83f
Compare
jbpros
added this pull request to stack #157
October 7, 2026 17:08
jbpros
marked this pull request as ready for review
October 7, 2026 17:08
An any_of with a path field it doesn't use, like a leftover from an equals it replaced, gave two different inputs for the same row, so OPA stopped the whole evaluation with eval_conflict_error and there was no report at all. The check is now written wrong, as the docs already say. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
jbpros
force-pushed
the
core/any-of-stray-path
branch
from
October 7, 2026 17:10
674c83f to
39a41e5
Compare
jbpros
added a commit
that referenced
this pull request
Oct 7, 2026
Extracts the cases again after #155, #156 and #158, leaving out policies that aren't objects, since their reports use numbers as keys. The Rust port now writes every number in its plain form, as #158 does, and its runner compares number text exactly to check it. generate.sh lets OPA write each file's text, because jq rewrote numbers like 0.000000123 as 1.23E-7. Co-Authored-By: Claude Opus 5.5 <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.
An
any_ofwith apathfield it doesn't use, like one left over from anequalsit replaced, gave two different inputs for the same row. OPA then stopped the whole evaluation witheval_conflict_error, so there was no report at all:{"op": "any_of", "path": ["y"], "options": {"o": [{"op": "equals", "path": ["x"], "value": 1}]}}The check is now written wrong and fails as
ill_formed, which is whatREFERENCE.mdalready says about a field an op doesn't use.What I ran: every check in
AGENTS.md, plus Wasm, OPA 1.20.2 and the JS runtime, 878/878. The new test errors without the fix.AGENTS.mdpassREFERENCE.mdandREADME.mdare updated if behaviour changedChanges the report:🤖 Generated with Claude Code