wasm: String concat set ordering #2924
Comments
srenatus
added a commit
to srenatus/opa
that referenced
this issue
Dec 11, 2020
Since anything can happen, we now list the possibilities (3! = 6), and check that any of them was the result. Fixes open-policy-agent#2924. Signed-off-by: Stephan Renatus <stephan.renatus@gmail.com>
tsandall
pushed a commit
that referenced
this issue
Dec 14, 2020
Since anything can happen, we now list the possibilities (3! = 6), and check that any of them was the result. Fixes #2924. Signed-off-by: Stephan Renatus <stephan.renatus@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This test case test/cases/testdata/strings/test-strings-0883.yaml is failing when run with Wasm with the following result:
The policy is attempting to concatenate a set of strings, and it seems that the Wasm implementation does so in a different order. Since it was a set initially (non ordered) it doesn't appear to be an invalid result, but we need some way to better handle these test cases. The yaml specifies:
Which implies a string value with a specific order.
The text was updated successfully, but these errors were encountered: