HTTP 500 / Server Error on topmost repo view for logged in users #83985
-
Select Topic AreaBug BodyWe have a repo for a community website here: https://github.com/dorkbotpdx/dorkbotpdx.org Sub-pages like pulls and commits work fine. Even the file browser for project dirs seems to work fine. The /tree/main subpath does not. This has been confirmed across firefox and chrome on both macos and linux, both with users in the org and users outside the org. Does anybody NOT see a 500 for that repo? I did search for related an found #76872 which seems similar, but different browsers with different extensions all experience this problem. |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 6 replies
-
Forks of this repo also appear to have this same issue, strongly suggesting something with the navigation code. |
Beta Was this translation helpful? Give feedback.
-
Welp, as if by magic, the problem has worked itself out through no action on our part. Presumably a bug was fixed. Thanks. |
Beta Was this translation helpful? Give feedback.
-
Thanks for reporting this. I am looking into which team to direct the problem to, but in the meanwhile I looked into it. I think the problem is that the repository has a |
Beta Was this translation helpful? Give feedback.
-
Late to the party, but doesn’t seem to matter if I’m logged in to GitHub or not. iPadOS + Firefox + authenticated == 500 error. iPadOS + Chrome + unauthenticated == 500 error. iPadOS + Safari + unauthenticated == 500 error. Struck out in all cases. Assuming these browsers are isolated (as they should be), this seems conclusive that being logged in or not isn’t a factor. |
Beta Was this translation helpful? Give feedback.
-
Just checked behavior on Arch Linux: Firefox + authenticated == 500 error. Chromium + unauthenticated == 500 error. I have not yet seen this page load, in all the combinations I've cited here and in my last comment. |
Beta Was this translation helpful? Give feedback.
I think I've figured out the problem. If you want to work around it until I can fix the issue, making the
code_of_conduct
in your root directory not a symlink to a directory will help. Alternatively, you could add a.github/code_of_conduct
file - that should be picked up first and avoid the bug.