You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Under the hood, OPA is rewriting the == operation as a unification operation without checking whether the result of the == operation is required. Unification fails (since 3 != 0) so the query ends up undefined. This is a bug. Thanks for reporting it--it should be a quick fix.
In a660d8f we added a rewriting stage that converts == to unification.
This simplifies evaluation and allows the rule index to be used,
however, the rewriting was incorrectly applied to == expressions that
are intended to yield a true/false value (and not undefined).
Fixesopen-policy-agent#995
Signed-off-by: Torin Sandall <torinsandall@gmail.com>
In a660d8f we added a rewriting stage that converts == to unification.
This simplifies evaluation and allows the rule index to be used,
however, the rewriting was incorrectly applied to == expressions that
are intended to yield a true/false value (and not undefined).
Fixes#995
Signed-off-by: Torin Sandall <torinsandall@gmail.com>
I am trying to return a document to the rest call. The document contains results of a match array, and a binary conclusion
This is correct, but let's add a conditional:
Why is the resulting doc empty? c is a bound variable, and I should be able to use it in an expression, the problem is when the expression is binary
The text was updated successfully, but these errors were encountered: