Joey
12/29/2022, 8:22 PMSingha1
12/29/2022, 8:34 PMderekperkins
01/02/2023, 11:41 PM/nozzle.billing.v1.PlansService/ListPlans
, but it appears that isn't supported. I found this recommendation from 8 months ago to base64 encode it. Is that still the recommendation? Is there a better approach?
https://discord.com/channels/844600078504951838/844600078948630559/972191542435532860kameshraj
01/03/2023, 4:40 PMpquerna
01/03/2023, 5:48 PMtim-dcdbl
01/04/2023, 12:53 AM$ zed version
client: zed 0.7.5
4:46PM WRN the version of SpiceDB being called is out of date. See: https://github.com/authzed/spicedb/releases/tag/v1.15.0 latest-released-version=v1.15.0 this-version=v1.11.0
service: v1.11.0
I would expect a brand new SpiceDB instance from a brand new install of the k8s operator would be up to date, but instead it is 4 minor versions behind. Anybody know what's up? What should I do instead?
Yes I need features that don't work with this version but did work when I installed via brew install authzed/tap/spicedb
and ran from the command line.
I need to convince folks at my company (including myself) that SpiceDB is the way to go, and have been impressed so far. It'd be a real big help if the recommended install method was up to date. Or else am I missing something?
Thank you!ecordell
01/04/2023, 1:01 AMtim-dcdbl
01/04/2023, 1:05 AMspec:
config:
image: authzed/spicedb:v1.15.0
Joey
01/04/2023, 1:23 AMtim-dcdbl
01/04/2023, 1:25 AMSPICEDB_DISPATCH_UPSTREAM_ADDR
). I see the fix was merged 2022-12-01. I'll be using postrges store so I expect operator to work out of the box (unaffected by this issue). Again, sure appreciate your help!tim-dcdbl
01/04/2023, 9:12 PMdatastoreEngine: postgres
with the k8s operator, but the initial migrate job the operator attempts fails with error message:
unable to migrate to `head` revision: error executing migration `add-xid-columns`: ERROR: type "xid8" does not exist (SQLSTATE 42704)
on postgres 12.4. Any ideas? Thanks!tim-dcdbl
01/04/2023, 9:21 PMJoey
01/04/2023, 9:34 PMJoey
01/04/2023, 9:34 PMsmithp4ntz
01/04/2023, 10:37 PMvroldanbet
01/05/2023, 9:32 AMShyam
01/05/2023, 11:07 AMvroldanbet
01/05/2023, 12:58 PMfmascarenhas
01/05/2023, 1:58 PM│ spicedb-5bc6d7f6d5-9g8p7 {"level":"warn","error":"timeout: context deadline exceeded","time":"2023-01-05T13:53:24Z","message":"error attempting to perform garbage collection"} │
│ spicedb-5bc6d7f6d5-dx8sb {"level":"error","module":"pgx","args":[4124334],"err":"timeout: context deadline exceeded","pid":25001,"sql":"WITH rows AS (SELECT namespace, object_id, relation, userset_namespace, │
│ userset_object_id, userset_relation, created_xid, deleted_xid FROM relation_tuple WHERE deleted_xid < $1 LIMIT 1000)\n\t\t DELETE FROM relation_tuple\n\t\t WHERE (namespace, object_id, relation, userset_n │
│ amespace, userset_object_id, userset_relation, created_xid, deleted_xid) IN (SELECT namespace, object_id, relation, userset_namespace, userset_object_id, userset_relation, created_xid, deleted_xid FROM rows) │
│ ;\n\t","time":59989.653851,"time":"2023-01-05T13:53:24Z","message":"Exec"}
There is probably a lot of garbage because I was using TOUCH instead of CREATE consistently, and unaware of https://github.com/authzed/spicedb/issues/901. This has been fixed, but I would like to clean the existing garbage. Is it possible to increase this deadline through an environment variable? For context, the datastore is Postgres, in a rather beefy RDS instance of Postgres 14 (4 vCPU).vroldanbet
01/05/2023, 2:13 PMRobertM
01/06/2023, 5:39 AMJoey
01/06/2023, 5:40 AMJoey
01/06/2023, 5:40 AMJoey
01/06/2023, 5:41 AM--datastore-bootstrap-files strings bootstrap data yaml files to load
--datastore-bootstrap-overwrite overwrite any existing data with bootstrap data
Joey
01/06/2023, 5:41 AMJoey
01/06/2023, 5:42 AMRobertM
01/06/2023, 5:43 AMpoulpi
01/06/2023, 4:38 PM2 UNKNOWN: unable to find revision: ERROR: prepared statement \"lrupsc_89_0\" does not exist (SQLSTATE 26000)
poulpi
01/06/2023, 4:38 PMpoulpi
01/06/2023, 4:40 PM