Code view returns HTTP 500 on the root of every public repo in one organization (EverMind-AI)

[LivXue]

🏷️ Discussion Type

Bug

Body

GitHub Community report - repo root code view returns 500 for every public repository in one organization

Category: Repositories (or "Other feature feedback / questions / ideas")
Title: Code view returns HTTP 500 on the root of every public repo in one organization (EverMind-AI)

---

Summary

Opening the repository root page of any public repository in the EverMind-AI organization
returns a page whose code-view region is a server-side rendered error:

Error loading page
An unexpected 500 error occurred. Try reloading the page.

The HTTP response itself is 200, but the embedded React payload carries the server error.
17 of the 18 public repositories in the organization are affected. The only exception,
EverMind-AI/.github, does not use the React code view at all.

Environment

• Organization: EverMind-AI (org id 229275294, GitHub Free plan)
• Default branch of the reporting repo: main
• Edge region reported by the response: southeastasia
• Viewed anonymously and while authenticated - identical result
• Reproduced from two independent network vantage points (see "Not the client" below)

Reproduction

1. Open https://github.com/EverMind-AI/Raven while signed out.
2. The page shell renders (repo name, tabs, issue/PR counts), but the content region shows
   "Error loading page / An unexpected 500 error occurred".
3. Repeat for any other public repo in the org - EverOS, EverMe, MSA, Plugins,
   SkillCorpus, HyperMem, EverAlgo, EverMemBench, EverOS-MCP, EverOS-Tools,
   EverOS-Convex, evermem-claude-code, evermem_got_demo, everos-cloud-sdk-python,
   raven-use-cases, EvoAgentBench. All fail the same way.

The server error, as returned in the page payload

curl -H "Accept: application/json" https://github.com/EverMind-AI/Raven returns:

"codeViewRepoRoute": {
  "path": "",
  "tree": { "items": [], "totalCount": 0, "readme": null },
  "fileTree": null,
  "fileTreeProcessingTime": null,
  "overview": { "overviewFiles": null },
  "error": { "httpStatus": 500, "type": "httpError" }
}

On a working repository the same route returns "path": "/", a populated tree.items,
and "error": null. The empty path looks like the root route is being built without its
path, after which the tree and README load fails.

Request IDs (all 2026-10-15 UTC, edge region southeastasia)

Affected:

Repo	Request ID	Time
EverMind-AI/Raven	3A49:F7865:D7985D:1413DDD:6AD07C38	07:09:44
EverMind-AI/EverOS	3981:353DC:D935E7:1430697:6AD07C3B	07:09:44
EverMind-AI/EverMe	2833:1A6C41:D84ADB:1424065:6AD07C3D	07:09:44
EverMind-AI/MSA	D5A8:156633:D7EBFE:1417469:6AD07C3F	07:09:44
EverMind-AI/Plugins	B8E2:6783E:D9E330:143C6BD:6AD07C41	07:09:44
EverMind-AI/SkillCorpus	AF32:9CA4C:D8E034:1425DF1:6AD07C44	07:09:44
EverMind-AI/Raven (earlier)	6153:2F1B40:C2EF1B:123A8F9:6AD0720D	06:26:22
EverMind-AI/Raven (earlier)	9321:2F1B40:D75215:1405F90:6AD07B71	07:06:25

Working control at the same time:

Repo	Request ID	Time
SpiralCloudOmega/Raven	B930:6A71E:D8378A:141CDBB:6AD07C46	07:09:57
nodejs/node	EEB7:124545:D94C5C:142E493:6AD07C48	07:09:57

What is NOT affected

Everything except the repository root code view continues to work normally:

• Subdirectory views: /EverMind-AI/Raven/tree/main/raven - renders correctly
• File views: /EverMind-AI/Raven/blob/main/README.md - 200
• /tags, /branches, /commits/main, /find/main, /community, /releases, /actions,
  /discussions, /issues, /pulls - all 200
• REST API: GET /repos/EverMind-AI/Raven/git/trees/main returns 51 entries;
  GET /repos/EverMind-AI/Raven/readme returns README.md, 27923 bytes;
  GET /repos/EverMind-AI/Raven/tree-commit-info/main returns ~476 KB
• raw.githubusercontent.com/EverMind-AI/Raven/main/README.md - 200, 27923 bytes
• git clone and the gh CLI work normally

This suggests the Git data and the API are healthy and that the failure is confined to the
code-view rendering path for the repository root.

What has been ruled out

• Not the client or the network. Reproduced from two independent vantage points, including
  a third-party renderer that never touches the reporter's network. Same error page, same
  message.
• Not auth. Anonymous and authenticated requests fail identically; a signed-out browser
  shows the same error.
• Not repository content. Forks of EverMind-AI/Raven under other owners
  (SpiralCloudOmega/Raven, amanajas/Raven, artzy/Raven, ForeverYoungPp/Raven), which
  contain byte-identical root content including both README files, render correctly -
  full file tree, 51 entries, no error. Only the copy under EverMind-AI fails.
• Not a global outage. 40+ unrelated repositories across many other owners and
  organizations render correctly, at the same times.
• Not symlinks in the tree root. Suggested by a related past report, but falsified here:
  EverMind-AI/MSA, Plugins and SkillCorpus contain no symlinks in their root and still fail.
• Not non-ASCII filenames. No affected repository has a non-ASCII name at its root.
• Not the community-health files. CODE_OF_CONDUCT.md is a regular file in the repos that
  have one, and several affected repos do not have one at all.
• Not repo metadata. Topics, discussions toggle, description, custom properties (the org's
  property schema is empty), and response-header differences were compared and show no
  correlation.
• Not .github inheritance. EverMind-AI/.github has no commits and no health files.

Notes

• The pattern is bound to the organization, not to any repository: identical content under a
  different owner renders fine, and every public repo under this owner fails, regardless of
  size (from 130 KB to 250 MB), age (created 2025-10 through 2026-10), or content.
• GitHub Status reported "All Systems Operational" throughout, with no active incident, so this
  appears not to be captured by platform monitoring.
• The failure has been continuously reproducible for at least the 45 minutes of this
  investigation, and is still reproducible now.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[LivXue]

The issue was solved. Thanks for your effort!

[aalshrawy043-ops]

اخترق اشبكه

[v-ember]

Hi @aalshrawy043-ops, thanks for participating!

Unfortunately, we don’t currently have moderators for languages other than English. Until that changes, we need to ask that everyone use English here in the GitHub Community when posting to ensure discussions are adhering to our Code of Conduct.

We’ll be locking this post for now, but please feel encouraged to create a new discussion in English if you still need support.