learningequality / learningequality/studio
InvalidMove: A node may not be made a sibling of itself.
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 191
- Forks
- 307
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 10
Description
Sentry Issue: STUDIO-E31
InvalidMove: A node may not be made a sibling of itself.
(3 additional frame(s) were not displayed)
...
File "contentcuration/db/models/manager.py", line 210, in move_node
self._move_node(node, target, position=position)
File "mptt/managers.py", line 71, in wrapped
return method(self, *args, **kwargs)
File "mptt/managers.py", line 592, in _move_node
self._move_child_node(node, target, position)
File "mptt/managers.py", line 1070, in _move_child_node
self._move_child_within_tree(node, target, position)
File "mptt/managers.py", line 1149, in _move_child_within_tree
raise InvalidMove(_('A node may not be made a sibling of itself.'))
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with contentcuration/db/models/manager.py at move_node, then follow the _move_node call into the mptt manager methods named in the traceback. Look for the operation that passes the same node as both node and target. The issue does not provide reproduction steps or expected behavior, so confirm those before defining done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100