Anders Eknert

Awesome, @anivar 💯 Let us know if you need any help with that! The language aspect is valid for sure, and LLMs can likely be of great help in that...

Beautiful! It’s 5:13 am here and time to sleep 😄 Jet lag… But I’ll get back to re-review when I wake up.

Indeed, those users may notice a positive performance impact in some cases. I can add to the list for sure, but it’ll probably never be complete, as we find new...

Reproducing should be easy. Just put the example code from the description in a policy file (say `p.rego`) and then run: ``` opa eval -f pretty -d p.rego data.play.obj ```...

After clearing out my tmp-directory and changing to `/users/*`, I no longer get the "Txn is too big" errors. The bad news is that I now go straight to the...

``` $ opa run -c sconf.yaml -s bundle-opa-400.tar.gz error: initialization error: storage error: storage_invalid_patch_error: value cannot be partitioned ``` I tried changing `/users/*` to `/roles/*` thinking it might want me...

That did not make a difference :/ I checked and according to `jq` there are only two top-level attributes in the bundle — `users` and `roles`. ``` cat ~/Desktop/bundle-opa-400/data.json |...

Trying `/roles` and `/users` without the wildcard doesn't work either: ``` $ opa run -c sconf.yaml -s bundle-opa-400.tar.gz error: initialization error: storage error: Txn is too big to fit into...

Yes, https://github.com/open-policy-agent/opa/issues/5721#issuecomment-1453441223 **conf.yaml** ``` storage: disk: directory: "/tmp/storage" auto_create: true partitions: - "/roles/*" - "/users/*" ``` ``` $ opa run --log-level debug -c conf.yaml -s bundle-opa-400.tar.gz {"level":"info","msg":"badger: All 0 tables...

Yep, that seems to be it — the arrays present in the data seem to be the cause, as JSON unmarshalling into a map unsurprisingly fails. ![Screenshot 2023-03-03 at 13...