archive/blender-cloud
0
1
Fork 1
Code Issues 24 Pull Requests Packages Projects Releases Wiki Activity

422 on project edit due to header_node field #53729

New Issue
Open
opened 2018-01-08 15:42:45 +01:00 by Francesco Siddi · 3 comments
Francesco Siddi commented 2018-01-08 15:42:45 +01:00
Copy Link

When editing the project "Hero", for example updating some node_type props I get:

[Mon Jan 08 14:28:53.250706 2018] [wsgi:error] [pid 13036:tid 140624720283392] pillarsdk.exceptions.ResourceInvalid: Failed. Response status: 422. Error message: b'{"_issues": {"header_node": "value \\'5a1c2b838ac31b30f7f17cf0\\' must exist in resource \\'nodes\\', field \\'_id\\'."}, "_status": "ERR"}'

It looks like it's due to the header_node missing?

When editing the project "Hero", for example updating some `node_type` props I get: ``` [Mon Jan 08 14:28:53.250706 2018] [wsgi:error] [pid 13036:tid 140624720283392] pillarsdk.exceptions.ResourceInvalid: Failed. Response status: 422. Error message: b'{"_issues": {"header_node": "value \\'5a1c2b838ac31b30f7f17cf0\\' must exist in resource \\'nodes\\', field \\'_id\\'."}, "_status": "ERR"}' ``` It looks like it's due to the `header_node` missing?
Sybren A. Stüvel was assigned by Francesco Siddi 2018-01-08 15:42:45 +01:00
Francesco Siddi commented 2018-01-08 15:42:45 +01:00
Author
Copy Link

Added subscriber: @fsiddi

Added subscriber: @fsiddi
Francesco Siddi commented 2018-01-18 12:43:40 +01:00
Author
Copy Link

By actually using the brain and reading the error, it turns out that that the node referenced in header_node should exist (not be deleted). As a solution, we should make sure that when deleting a node in a project, we also check if it's used in the the project header_node property.

By actually using the brain and reading the error, it turns out that that the node referenced in `header_node` should exist (not be deleted). As a solution, we should make sure that when deleting a node in a project, we also check if it's used in the the project `header_node` property.
Sybren A. Stüvel was unassigned by Dalai Felinto 2019-12-23 16:36:22 +01:00
Dalai Felinto commented 2019-12-23 16:36:22 +01:00
Copy Link

Added subscriber: @dr.sybren

Added subscriber: @dr.sybren
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Priority::High
Priority::Low
Priority::Normal
Status::Archived
Status::Confirmed
Status::Duplicate
Status::Needs Triage
Status::Resolved
Type::Bug
Type::Design
Type::Report
Type::To Do
legacy module
Modeling
legacy project
Blender Cloud
legacy project
Documentation
legacy project
Infrastructure: Websites
legacy project
Infrastructure: blender.org
legacy project
Modeling
legacy project
Pillar
legacy project
Pillar Framework
No Label
Priority::Normal
Status::Confirmed
Type::Report
legacy project
Blender Cloud
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
blender-admin
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: archive/blender-cloud#53729
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?