-
Notifications
You must be signed in to change notification settings - Fork 7
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
Commit messages containing unicode characters causes submission failure #14
Comments
chisubmit will (hopefully) be migrated to Python 3 before the next school year (we attempted this a year ago, but there were still a couple dependencies that were available only in Python 2; it seems like all those dependencies are finally available for Python 3). At that point, I'm hoping all unicode issues will go away on their own. So, we'll probably not fix this issue specifically until then (and, as you point out, you can just ask students to not use non-ascii characters in their commit messages). However, I'll leave the issue open until we do the Python 3 migration and can verify it's been resolved. |
chisubmit was migrated to Python 3 a few months ago, so hopefully this issue (and other unicode-related issues) have been dealt with automatically. I will reopen this issue if this reoccurs. |
Issue persists on chisubmit running on CSIL machines. Commits with the ellipsis character '\u2026' will cause an unexpected exception and fail to submit. I think git will automatically truncate any messages that are more than 50 characters long and add an ellipsis to make the header fit, then put the entirety of the commit message in the body. Therefore anyone who writes extremely eloquent commits like "turns out you'll get a null ptr exception if you try to copy stuff into an array initialized as null. fascinating!" and tries to submit it will hit this issue. Successfully submitted the assignment after making a new commit with the comment "touch".
|
Could you provide a link to the commit on mit.cs.uchicago.edu? (I'd like to experiment further on this) |
A student in intro to security ran into this issue (names & traceback modified for privacy) when submitting trying to submit an assignment.
Looking at the commit message for , the message does include u'\u2026', or the triple dot ellipsis.
I have not been able find whether or not git commit messages should be able to contain all unicode characters, so it is possible this is not a bug because not all unicode characters should be supported for commit messages. In either case, it is low priority issue as we can easily instruct students to avoid including non-latin-1 characters in their commit messages.
The text was updated successfully, but these errors were encountered: