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

Deleting a compute graph can produce weird behaviors if the executor is not restarted #998

Open
seriousben opened this issue Nov 1, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@seriousben
Copy link
Member

seriousben commented Nov 1, 2024

When deleting a graph and then recreating the same one, some executor state issue seems to create side effects that only go away when restarting the executor.

The following example if from https://github.com/tensorlakeai/indexify/blob/9fcb176bfce8990e35ef28e572dc3096dddb50b2/python-sdk/tests/test_graph_update.py where the equality assertion fails in a surprising way when adding deletion on cleanup.

Traceback (most recent call last):
  File "/Users/seriousben/src/github.com/tensorlakeai/indexify/python-sdk/tests/test_graph_update.py", line 44, in test_graph_update
    self.assertEqual(output[0], Object(x="ab"))
AssertionError: Object(x='ab') != Object(x='ab')

After doing a model_dump and other prints, I still can't quite understand the difference between the objects.

@seriousben seriousben added the bug Something isn't working label Nov 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant