Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tooling to help debug cyclic data issues #2056

Open
zxlin opened this issue Sep 5, 2024 · 2 comments
Open

Tooling to help debug cyclic data issues #2056

zxlin opened this issue Sep 5, 2024 · 2 comments
Labels
kind/proposal Something fundamentally needs to change

Comments

@zxlin
Copy link

zxlin commented Sep 5, 2024

Problem Statement

Sometimes there may be cyclic data accidentally stored into SpiceDB and right now it's kind of hard to identify where in the data there is a cycle. It's only really realized with calls like lookup-resources as that will do a full traversal and not short circuit like with check permission.

Solution Brainstorm

It may be useful to include in the --explain feature some kind of highlighting if a particular node in the graph was traversed more than once (or however many time it was traversed), so that the user can more quickly identify a cyclic data problem in their DB.

@zxlin zxlin added the kind/proposal Something fundamentally needs to change label Sep 5, 2024
@josephschorr
Copy link
Member

@corkrean
Copy link

@josephschorr, sure, but that doesn't solve the problem statement. If a lookup-resources request results in a cycle, it can be challenging to identify where in the data the cycle is occurring. There is no equivalent of --explain for lookup-resources.

@corkrean corkrean reopened this Sep 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/proposal Something fundamentally needs to change
Projects
None yet
Development

No branches or pull requests

3 participants