![github-actions[bot]](https://web.archive.org/web/20220525144330im_/https://avatars.githubusercontent.com/in/15368?v=4){kind=avatar}
Saw this rule in the clj-kondo linter, and I think it would be a good addition to our strict mode. Having duplicate elements in sets is probably always a mistake in a production policy, and while it's "harmless", the intent is likely to provide another element rather than the duplicate, leading to an unexpected
With oso 0.11.1 and Rust client code.
When tracking down policy logic failures using the POLAR_LOG=1 environment variable I will see the logging of the execution of all of my inline queries. The problem is that I have lots of these, but usually I'm not interested in the ones in my core policy files which are fairly static and unchanging, but rather I'm interested in those policy sources that
I've read the docs, and it seems you can pass through knex instances, but I didn't see if it supports SQLite3 - could you clarify please?
Add a description, image, and links to the authorization topic page so that developers can more easily learn about it.
To associate your repository with the authorization topic, visit your repo's landing page and select "manage topics."
The upstream issues got closed. It is referenced in:
This issue was created by the ORY Closed Reference Notifier GitHub action.