-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
How to restore a project to functionality after pushing a branch with non-ASCII UTF-8 characters #2632
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I fixed this for your project by deleting the version, but the issue seems to be in the packaging library we're using for version comparison. Full traceback:
|
Hi, I just tested this on my local instance, when creating a branch like So, was this problem fixed at some point? |
It sounds like the original issue was resolved. I think we have some more work to do on git parsing of this information though. Closing this issue as we have a few already around utf8 support. |
Our project had some UTF-8 characters in branch names. Since according to #1822, these aren't allowed in branch names, I've removed them. But even after running a new build of my project, the Versions page remains inaccessible and Admin -> Versions still features the old, removed, UTF-8 branch.
This is not a duplicate of #1410; that issue deals with proper support for UTF-8 characters in branch names, while this issue deals with the correct recovery procedure for fixing a project that has had unsupported UTF-8 characters in its branch names.
Details
Expected Result
New branches should show up under Admin -> Versions immediately after the next successful build, now that no branch names on the Github repo contain UTF-8 characters. Also, the main "Versions" button for the project should return a page full of versions.
Actual Result
New branches are still not appearing under Admin -> Versions after a successful build, and the old, invalidly-named branches are still there. The main "Versions" page still just has an error message saying "Fail. Check back in a bit!".
The text was updated successfully, but these errors were encountered: