Broken UI and 404 to files and directories with non-ASCII names #188152
-
Select Topic AreaBug BodyHi community, I'm trying to explore a repository1, but it seems that I can't access the files or directories listed there. I am consistently getting 404s:
Looking around, I found that every repository with CJK (or non-ASCII perhaps?) characters in its filenames/paths seems clobbered and inaccessible, to name but a few 2345. I remembered accessing 5 just a few days ago, and back then it worked without problem. If it is GitHub's problem, it's likely a recent regression. Update 1: I filed a ticket for this, but have not heard back from GH yet. Update 2: There is an automated incident thread at https://github.com/orgs/community/discussions/188156. Update 3:
Related issues
Footnotes |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments
-
|
💬 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 ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
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. ⭐ |
Beta Was this translation helpful? Give feedback.
-
|
Note, https://github.com/orgs/community/discussions/188151 is about wiki pages, not directory listing. |
Beta Was this translation helpful? Give feedback.
-
|
Same.. GitHub._20260227_.404.mp4 |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
As per https://www.githubstatus.com/incidents/kv1lzpgzr9yp, the incident has been resolved. |
Beta Was this translation helpful? Give feedback.



As per https://www.githubstatus.com/incidents/kv1lzpgzr9yp, the incident has been resolved.