the ideal would be if it knows the read replica has the zedtoken, it could still use it

I'm liking SpiceDB so far, I've been toying in the playground, but it would be nice to have some kind of VSCode integration, do you guys accept community contributions ?

absolutely!

we actually have plans for a VSCode integration, so if you'd like to work on that with us, we'd more than welcome the contribution

in fact, the first part of the work for supporting it is here: https://github.com/authzed/spicedb/pull/663

allows for the full development system to work via WebAssembly, instead of calling an external API

Nice, I'll have a look !

I was able to build and run the wasm example. I'll try setting up a basic vscode extension over the weekend.

awesome

don't hesitate to ping me if you have any questions

Will do, thanks

we also have the grammar for coloring the schema in Monaco format already, if you need it

Yep, that would help, is it readily available on GitHub ?

not yet; the plan was to OSS it when we started on VSCode stuff

if you get the foundations of an extension setup, we can just contribute it into that

sounds good

Hello everyone! I was wondering if there are plans for create an elixir sdk for spicedb? I see a old discussion here: https://discord.com/channels/844600078504951838/844600078948630559/880848276314812497 but I’m not sure if this has been picked up. If it hasn’t, I would love to try and implement it! 😄

No plans but we’d love the contribution

Great, I’ll get started on it then! 😄

Hello everyone! Happy to announce that we have the first version of an elixir client for SpiceDB: https://github.com/goodhamgupta/authzed_ex 😄 . There are a few rough edges for now, but hopefully we can resolve it in the upcoming releases.

What's the best approach to deleting a bunch of permissions if we've granted a higher permission? E.g. if we have a hierarchy of organization -> team and a user has team level permissions, if we upgrade them to org level permissions how would we handle cleaning up all their team level permissions?

How are relationship graphs are maintained in memory? What is recommended size of memory , any guidelines?

hello, I did more investigation on our problem with spice (version 1.9.0, but it was the same on 1.8.0) memory usage on Lookup. I created a synthetic dataset with a simple schema: User member of Customer, Resource owned by User. Resource can be shared with other Users and Customers. Backend is PostgreSQL. Spice is single node. 0. spice initial memory usage: <30MB. 1. create 8k Resources, owned by User u1: memory usage still very low 2. query lookup non-concurrently, repeatedly (every 2s), for user u1: memory spikes to >200MB for a few seconds, then down to <100MB 3. while querying, I create thousands more relations on other users and customers: memory spikes as soon as I run the creation script, then it tops to >500MB 4. I stop the concurrent relation creation (it's still doing Lookup), memory usage 300MB 5. stop Lookup and wait a few minutes: memory usage 240MB, I'd expect it to be <100MB 6. restart spice: <30MB If I do the relation creation (point 3) non-concurrently, before running the repeated lookup script (point 2), memory never exceeds 120MB.

Note that it's the 4th of July, big holiday in the US, Authzed people probably won't be around today!

some of us are around, but took the opportunity to get some extra sleep 😄

you don't have to delete their team level permissions; they'll just be granted access through two paths. If you do want to delete them from the teams, you can use the DeleteRelationships call to delete all entries for that user in the

member

relation for the team(s), or its equivalent

graphs are not stored in memory, unless the memory-datastore is used, which is not recommended for production

I think i'd rather delete their team level perms if we promote them to org level perms, as if we revoke their org level perms i wouldn't want them demoted to team level. I'd think they'd just be removed, and need team level explicitly adding back

@vad8615 can you try turning off caching and see if the memory still spikes? The system will be caching those lists of lookup results, which could grow large if you have a very large dataset

then yeah, DeleteRelationships is what you want, to remove their access from the teams