• Jake

    Jake

    6 months ago
    should be fine, if you run into anything let us know and we'll get to work on fixing it!
  • Vilsol

    Vilsol

    6 months ago
    awesome, thanks! the only other question I might have is whether CRDB is fully supported or are there things I should look out for?
  • Jake

    Jake

    6 months ago
    we run CRDB in prod
  • Vilsol

    Vilsol

    6 months ago
    that answers that
  • Jake

    Jake

    6 months ago
    this is some interesting reading if you've got the time: https://authzed.com/blog/prevent-newenemy-cockroachdb/
  • Vilsol

    Vilsol

    6 months ago
    ah, I saw this issue mentioned in the docs, will have a read, thanks!
  • night

    night

    6 months ago
    qq: is spicedb’s cockroach support reliant on enterprise features or is standard cockroach ok?
  • Jake

    Jake

    6 months ago
    you'll probably want backups
  • Jake

    Jake

    6 months ago
    but we don't orchestrate that, and we don't use any other enterprise features, e.g. enterprise changefeeds
  • williamdclt

    williamdclt

    6 months ago
    I'm regularly getting some of these errors when calling the check endpoint:
    Could not check permissions from the SpiceDB service. Error: 2 UNKNOWN: error dispatching request: unable to read namespace config: context canceled
        at Object.callErrorFromStatus (/home/node/app/node_modules/@grpc/grpc-js/build/src/call.js:31:26)
        at Object.onReceiveStatus (/home/node/app/node_modules/@grpc/grpc-js/build/src/client.js:180:52)
        at Object.onReceiveStatus (/home/node/app/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:365:141)
        at Object.onReceiveStatus (/home/node/app/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:328:181)
        at /home/node/app/node_modules/@grpc/grpc-js/build/src/call-stream.js:182:78
        at processTicksAndRejections (internal/process/task_queues.js:77:11) {
      code: 2,
      details: 'error dispatching request: unable to read namespace config: context canceled',
      metadata: Metadata {
        internalRepr: Map(2) {
          'io.spicedb.respmeta.dispatchedoperationscount' => [Array],
          'io.spicedb.respmeta.cachedoperationscount' => [Array]
        },
        options: {}
      }
    }
    That seems like an internal error, either it's a bug or it should surface a more readable error for the developer? "namespace config" and "context canceled" aren't concepts I've encountered in the docs