I've removed every reference I could find so far and I still get

[validator]could not find templates for lang: php

. So I must have a reference somewhere still. It does appear that I may be close to stripping the lib from the proto files.

I might need to connect with the maintainer of

envoyproxy/protoc-gen-validate

and see if validation can be skipped if a template isn't found. That would might be a slightly better solution.

we have a ruby library and node library, neither of which have support from

protoc-gen-validate

, maybe check how they are solving this problem

Ok, I'll check that out. Thanks for the advice

Hi, i have a question on zed debugging; We have a schema that we've been using fine for the last 4 months, but sometime in the last day or so it stopped being accepted for import. The schema passes the

zed validate

command, but any attempts to import result in an

InvalidArgument

error with no description. What can I do to further diagnose the issue? Here is the complete output of

zed import --log-level trace

, with keys redacted and zed usage trailing text removed:

9:58AM DBG set log level new level=trace
9:58AM TRC token={"APIToken":"**REDACTED**","Endpoint":"grpc.authzed.com:443","Insecure":null,"Name":"advocat_chetan"}
9:58AM TRC requesting schema read request={}
9:58AM DBG error reading server version response header; it may be disabled on the server
9:58AM TRC parsed trailers trailers={}
9:58AM DBG error reading dispatched operations trailer error="key `io.spicedb.respmeta.dispatchedoperationscount` not found in trailer"
9:58AM DBG error reading cached operations trailer error="key `io.spicedb.respmeta.cachedoperationscount` not found in trailer"
9:58AM DBG extracted response dispatch metadata cached=0 dispatch=0
9:58AM DBG found schema definition prefix prefix=advocat_chetan
9:58AM INF importing schema
9:58AM TRC writing schema request=**REDACTED**
9:58AM TRC parsed trailers trailers={}
9:58AM DBG error reading dispatched operations trailer error="key `io.spicedb.respmeta.dispatchedoperationscount` not found in trailer"
9:58AM DBG error reading cached operations trailer error="key `io.spicedb.respmeta.cachedoperationscount` not found in trailer"
9:58AM DBG extracted response dispatch metadata cached=0 dispatch=0
Error: rpc error: code = InvalidArgument desc =

you probably have duplicate definitions in it

we just started to tighten that

and I just fixed the error to make it visible in the next prod push we do

either that, or you're pushing the same schema without any changes

which we're also fixing

part of our CI/CD process is to re-import the schema on every deployment; is pushing the same schema without any changes now a bug on our end?

no, its a bug on our end that got introduced while fixing another bug

it should be a no-op

we're working on a fix for it now

ah, got it. for now i'll just bypass that step; is there a GitHub issue that I can track so that I can re-enable?

its an internal one since it only affects our hosted service

ok. thanks!

but I'll ping in here once its fixed

Hey @here! Our community just shipped some massive features in SpiceDB v1.12.0! 💥 - 👩‍💻 LookupSubjects API for querying all subjects with access to a given resource - 📦 Debug containers based on Chainguard's distroless - 🪳 Even more resiliency for CockroachDB datastore users https://github.com/authzed/spicedb/releases/tag/v1.12.0

I wonder if this is possible to model with SpiceDB: 1. A user can be either a regular employee or an admin. 2. Only admin with tenure >= 3 years can view documents of type "secured".

yes, either by writing a relationship for that case or to use the upcoming caveats feature

You mean to model the "tenure" attribute of a user as a relationship to the user?

yep

Ok. I haven't seen much examples of modeling ABAC using ReBAC. Also what is the upcoming caveats feature?

Hope this comes sooner than later!

its under active development

the first PR went in last week and we're working towards it now

follow that issue to be updated