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

Exporting a branch fails with CheckViolation for unexpectedly present lifecycle #11644

Closed
jacobtylerwalls opened this issue Nov 21, 2024 · 0 comments · Fixed by #11669
Closed
Assignees
Labels

Comments

@jacobtylerwalls
Copy link
Member

dev/8.0.x

  1. Create a model
  2. Create a string node under the top node
  3. Create new publication, click ok
  4. Make changes without publishing
  5. Click the string node in the sidebar
  6. Click the -> export button on the string node (➡️)
[20/Nov/2024 18:53:08] "GET /graph/85d63196-4748-4304-9d3c-1f7e8bc91285/get_related_nodes/d6f5f3d6-a7a2-11ef-9b5f-1ea1ac52128f HTTP/1.1" 200 2
Internal Server Error: /graph/85d63196-4748-4304-9d3c-1f7e8bc91285/export_branch
Traceback (most recent call last):
  File "/Users/jwalls/release/lib/python3.12/site-packages/django/db/backends/utils.py", line 105, in _execute
    return self.cursor.execute(sql, params)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
psycopg2.errors.CheckViolation: new row for relation "graphs" violates check constraint "resource_instance_lifecycle_conditional_null"
DETAIL:  Failing row contains (0e1a1626-a7a3-11ef-9b5f-1ea1ac52128f, {"en": "New Node"}, {"en": ""}, null, , null, , f, , {"en": ""}, null, null, null, {}, 50000000-0000-0000-0000-000000000001, null, null, null, f, f, f, 7e3cce56-fbfb-4a4b-8e83-59b9f9e7cb75).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant