I found "•" is not supported in resource id's like resource ID = ABC.XYZ any specific reason why,

It just be alphanumeric

Must*

We are currently evaluating Authzed, is there an option, that you have a EU based datacenter, as authorization storage is for our company only allowed in EU.

👋🏻yup! Our "SpiceDB Dedicated" offering gives you the possibility spin up SpiceDB clusters in any region supported by the cloud provider for your choice. Drop @Jake a DM if you need more details!

Has Authzed SOC2 or ISO27001 certificate?

Also @dsieczko should be able to help here

Thanks @vroldanbet!

We're currently undergoing our SOC2 audit

Hi larsilus! Can you DM me on Discord? I'm at dsieczko#3371 or email me at damian@authzed.com if you prefer

Hey there! I got a weird error during a stress test of SpiceDB, 1 user, 1 thread, so no concurrent requests. ~10k requests no issues, then suddenly SpiceDB stopes answering and I see errors on the SpiceDB side

{
  "level": "error",
  "module": "pgx",
  "args": [],
  "err": "FATAL: query_wait_timeout (SQLSTATE 08P01)",
  "pid": 868501332,
  "sql": "begin isolation level repeatable read read only",
  "time": "2022-11-16T16:11:05Z",
  "message": "Exec"
}

I have 3 instances of SpiceDB running in Kubernetes. Have somebody ever seen this error?

what version of SpiceDB and what datastore engine?

I use SpiceDB

v1.14.1

and @authzed/authzed-node

v0.7.0

I can highlight one more error I see in nodejs app logs a lot

2 UNKNOWN: unable to compute optimized revision: unable to find revision: FATAL: query_wait_timeout (SQLSTATE 08P01)

what datastore engine are you using?

Postgres

how many rows are in your transactions table, if you can check?

Let me check

relation_tuple_transaction

has just one row

timestamp          |  xid  |   snapshot   
----------------------------+-------+--------------
 2022-11-15 17:44:36.838627 | 10000 | 10000:10000:

strange

relation_tuple

has

36752

that should be fine

how, exactly, are you running this test?

I call an endpoint of my Nodejs app which is calling SpiceDB

checkPermissions

endpoint.

one by one?

Yes, now we try to isolate the issue

sounds like your Postgres started having issues

if there is a single row in the transactions table

then queries should not be timing out finding it

Any good examples for how to handle editing user information (i.e. a user should be able to edit themself, but we may have some hierarchy allowing admins to edit their users, etc). Since there isn't self, would we just add relations directly to our

user {}

type, or would it be better to create a separate entity, like

user_setting { relation self: user; relation ...}

?