Growing Memory on Demand for WebAssembly #647
Unanswered
christophwille
asked this question in
OPA and Rego
Replies: 1 comment 1 reply
-
Hi there! May be that there’s some delay before someone can look into this :) Just to help us understand here, is this something you had working pre-1.0 and now it doesn’t work anymore, or just that you tried it now for the first time and it doesn’t work as you expected? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
christophwille/dotnet-opa-wasm#58
I basically did the same as the npm version - check if memory size is sufficient, grow if necessary. All of the other stuff remained exactly the same, however, in my case it then fails inside opa_eval (enlarging the memory works, writing the string works, but then opa_eval does the same as in the "too little memory case" which is strange).
Any ideas where to start looking? (note my C# is rego_v1 whereas npm isn't yet)
Beta Was this translation helpful? Give feedback.
All reactions