LookupSubjects

seems to be returning duplicate results, this is just running tests against the

memory

datastore so not sure if it's datastore-specific. Is this known and/or expected in

1.29.2

?

❯ zed relationship create auth/organisation:123 admin auth/staff:abc#user
11:51AM WRN the version of SpiceDB being called is out of date. See: https://github.com/authzed/spicedb/releases/tag/v1.30.1 latest-released-version=v1.30.1 this-version=v1.29.2
GhUKEzE3MTI3OTMwNzM3NTUzNjg3MDY=

❯ zed permission lookup-subjects auth/organisation:123 admin auth/staff#user
auth/staff:abc
auth/staff:abc

❯ zed relationship read auth/organisation:123 admin auth/staff:abc#user
auth/organisation:123 admin auth/staff:abc#user

LS does not filter duplicates

But how is there a duplicate? It's a fresh datastore with only that relation in it. Not a big deal as I can use

ReadRelationships

for my test, just trying to wrap my head around why this happens

If there are two schema paths to the same subject, it can show twice

I still don't follow how there could be multiple schema paths to the subject in this case

❯ zed schema read
definition auth/organisation {
    relation admin: auth/staff#user
}

definition auth/staff {
    relation user: auth/user
}

definition auth/user {}

❯ zed relationship create auth/organisation:123 admin auth/staff:abc#user
GhUKEzE3MTI3OTkwMzk2MDIzMjA3MTg=

❯ zed permission lookup-subjects auth/organisation:123 admin auth/staff#user
auth/staff:abc
auth/staff:abc

Because it’s dispatching to itself

Ahhh

You just hit a corner case

It's probably not something I'd ever use in reality, it doesn't manifest the same if I add a

user

relation to

staff:123

and lookup the

user

subjects instead. I was specifically trying to test for the relation being created without caring about whatever else existed - in hindsight

ReadRelationships

is a better choice for this anyway