hrm, could that be it? I didn't specify any. Does it not default to full?

No it defaults to minimize latency

ah!

But you don’t even have to execute that check

Once the schema write is accepted just start writing your data and using the zookies you get back

Zedtokens *

That will synchronize everything up nicely

got it. I was building a small spicedb test framework for my application, and the first dumb test I created was simply "Check" with unexistent data

I didn't specify the consistency level, hence the error I was getting

Hey all! I'm trying to follow the 'First App' guide (https://docs.authzed.com/guides/first-app) with Java. It seems it is pretty outdated for Java, can I find an up-to-date version somewhere?

We can work on getting an update out today. In order to help the team: which specific parts are out of date?

1st section: https://docs.authzed.com/guides/first-app#defining-and-applying-a-schema

2nd section: https://docs.authzed.com/guides/first-app#storing-relationships

I see, yep should be easy enough to get those fixed up for v1

and also the third 🙂

that would be great, we're looking to integrate it into a Java stack, so it's quite crucial to us that it's reliable and up to date 🙂

In the meantime, this example already appears to be up to date for v1: https://github.com/authzed/authzed-java/blob/main/examples/v1/App.java

thanks for the hint, I'll have a look

I suspect that the version of

zed

available via Homebrew needs to be bumped. I'm trying to do a

zed import

of a playground file that has wildcard relationships and I'm seeing parse errors.

scaling

thanks @User , we'll get that updated asap

@User I tried with a fresh build from

main

and am still getting a parse error, so while the version does need a bump, that might not be the root cause.

The error I'm seeing is:

Error: failed to parse github/memex:public_user_memex1#public@github/user:* as relationship

After a slight hiccup in our release automation, zed 0.3.0 is published now if you'd like to give it a try From the error message I expect the spicedb bump to fix the issue (zed uses the string->object parsing from spicedb to convert the playground relationships to api calls), but we can keep looking if there's another issue as well

the issue has cleared with the fresh build. Getting some warnings that seem non-critical

❯ zed import file:///Users/cjs/github/authzd-acl/config/spicedb/playground.yaml --insecure
9:24AM INF importing schema
9:24AM WRN error reading dispatched operations trailer error="key `io.spicedb.respmeta.dispatchedoperationscount` not found in trailer"
9:24AM WRN error reading cached operations trailer error="key `io.spicedb.respmeta.cachedoperationscount` not found in trailer"
9:24AM INF importing relationships count=204
9:24AM WRN error reading dispatched operations trailer error="key `io.spicedb.respmeta.dispatchedoperationscount` not found in trailer"
9:24AM WRN error reading cached operations trailer error="key `io.spicedb.respmeta.cachedoperationscount` not found in trailer"

those errors are indeed not critical