HI I am facing issue with client.
# spicedb
m
HI I am facing issue with client.bulkCheckPermission(request) this line and error is Error: 12 UNIMPLEMENTED: CheckBulkPermissions is not yet supported in SpiceDB Serverless
v
bulk check is not supported in Authzed Serverless
m
The code is working properly earlier but due to version mismatch now it is stopped working. can you suggest which versions of @authzed/authezed-node and @grpc/grpc-js need to use.
"@authzed/authzed-node": "0.18.0" "@grpc/grpc-js": "1.6.9" these are the current versions
v
This could have not possibly worked earlier, because BulkCheck was never implemented in Authzed Serverless.
m
can you give some heads up what is serverless spicedb means. Because we have this working code but due to package changes now it stopped working.
permission.map(each => { permissionChecks.push( v1.BulkCheckPermissionRequestItem.create({ resource: createObject(each.resource), permission: each.permission, subject: createSubject(each.subject) })) }) const request = v1.BulkCheckPermissionRequest.create({ consistency:createConsistency(), items: permissionChecks }) return client.bulkCheckPermission(request)
we have deployed spicedb server. But where we need to check why it is pointing to serverless
v
Authzed Serverless is a managed SpiceDB served in authzed.com. It feels like somehow your client started calling
grpc.authed.com
instead of your own SpiceDB deployment.
are you providing the
endpoint
parameter to
NewClient
? It will default to Authzed Serverless unless provided: https://github.com/authzed/authzed-node/blob/948263a9649c829cd6aa3a790c980d8eb34f8d65/src/v1.ts#L291
m
yes we are providing end point to newclient
v
@yetitwo can you think of anything that may have changed recently that would have caused the authzed-node to start defaulting to serverless?
y
it always defaults to the serverless endpoint: https://github.com/authzed/authzed-node/blob/main/src/v1.ts#L291
oh, which you just linked above
no, nothing i can think of changed about this
what happens if you upgrade to the most recent version of the client? and does your usage match what's in the tests as far as client construction goes?
i'd also sanity check that the value you're passing as the endpoint is actually defined
6 Views