#Depth Error - Cyclic Checks

1 messages · Page 1 of 1 (latest)

rose knot
#

Hi @cosmic gyro, I will look at it

cosmic gyro
#

thanks! here is my production config if that helps at all:

app:
server:
rate_limit: 10000

service:
circuit_breaker: false
watch:
enabled: false
schema:
cache:
number_of_counters: 1_000
max_cost: 8MiB
permission:
concurrency_limit: 1000
cache:
number_of_counters: 10_000
max_cost: 16MiB

database:
engine: postgres
auto_migrate: true
max_open_connections: 20
max_idle_connections: 1
max_connection_lifetime: 300s
max_connection_idle_time: 60s
garbage_collection:
enabled: true
interval: 200h
window: 200h
timeout: 5m

plucky drift
#

I'm getting the same error in my schema, is there any solution?

#

@rose knot

rose knot
#

@raw bramble

cosmic gyro
#

I tried this other schema in production today, which seems much cleaner than my previous example, and I had the same issue. I had to rollback because it was producing the services that rely on Permify to go down.

`entity user {}

entity member {
relation user @user

attribute is_active boolean

permission active = user and is_active

}

entity team {
relation member @member
// TODO - Remove once migration is done
relation legacy_member @user
// TODO - Once migration is done replace with: action belongs_to = member.user
action belongs_to = member.user or legacy_member
}`

#

@rose knot @raw bramble

cosmic gyro
#

Hey folks @rose knot @raw bramble ! Do you have any updates on this?

cosmic gyro
#

Sorry ping you again @rose knot , but this is a blocking issue for us.

raw bramble
#

Hello @cosmic gyro, We have reproduced the error and we are investigating now.
We will get back to you soon.

rose knot
#

hi @cosmic gyro, i figured the issue. it was related to how we count the depth. i have opened a PR with the fix, and it should be included in the new release this Sunday.

#

thank you for pointing this out!