You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Public contentnode tree returns no children for an uppercase node id #6417
Confirm that you’ve read the guidelines in your comment.
Overview
The public contentnode tree endpoint accepts its node id in any form Python's UUID() parses, including uppercase hex, but then matches children by comparing each child's parent with the id exactly as sent. For an uppercase id the comparison never matches, so the response has the parent node with no children.
Reproduced: GET /api/public/v2/contentnode_tree/<id in uppercase>/ returns 200 with no children key, and the same id in lowercase returns the children.
The Change
The endpoint should normalise the id it accepts to lowercase hex before using it.
Acceptance Criteria
General
GET /api/public/v2/contentnode_tree/<id>/ with the id in uppercase returns the same response as with the id in lowercase.
Testing
The criterion has a regression test.
AI usage
I scoped the audit. Claude Code found and reproduced this failure and drafted this issue.
Activity
learning-equality-bot commentedon Nov 15, 2026
Hi! 👋
This issue is available for contribution and supports self-assignment. Here's how to get started:
/assignto assign yourself to this issue📖 Read the Contributing guidelines before starting.
Are you preparing for Google Summer of Code? See our GSoC guidelines.
ManyaJain111 commentedon Nov 16, 2026
/assign
learning-equality-bot commentedon Nov 16, 2026
Hi! 👋
You've been assigned to this issue. Here's what to do next:
Good luck! 😊
Are you preparing for Google Summer of Code? See our GSoC guidelines.