or your own local spicedb?

authzed.com

how many resources are in your result set?

this user has access to "all" the resources. so "a lot"

Wondering if there is any future though of exposing the exact preconditions that fail in a easily parseable/understandable way?

that's a good idea; can you file an issue for it?

400K

is there a workaround for

recv error rpc error: code = Unavailable desc = upstream request timeout

?

no, it means the request is too large to be handled

now why that is, is the interesting question

thank you. this is amazing

@Lanny if you can DM myself or @Jake, we can try to debug why exactly its timing out with you (we need some info about your permission system to do so, hence the DM)

Will do. I need to head out for a little bit. thank you!

its a URI the logical database name

I'm getting the same error when trying to delete relationships

rpc error: code = Unavailable desc = upstream request timeout

are you trying to delete very large amounts of relationships?

yeah. i wanted to start "over" and implement jake's suggestions

ah

well, for now, I recommend using a new permission system and we can clear out the existing one tomorrow if you like

trying to delete (what I assume) is hundreds of thousands of rels at once is going to time out

were you calling

DeleteRelationships

with a namespace as the filter?

yeah

so my guess is the timeout just simply due to the size of that

Hello! I was evaluating SpiceDB for an internal product in our organisation and found it a brilliant fit. I just had a question regarding LookupStream. Imagining it returns a million records using Go's SpiceDB client which follow no particular order as per my findings, is there a way to paginate the responses in an ordered way with the current released version into a REST response?

no. LookupResources is explicitly not designed to be ordered; the solution for ordered lookup will be to use the LookupWatch or Tiger cache once it is in

Any URL guiding towards the solution? I wasn't able to find an RPC call for LookupWatch in v1

as stated, its not written yet

Ah alright! Thanks for the prompt response @Joey! 😄