I can try to write the test case but in the past the problem was just about creating the mysql database "properly". I can maybe get the admins to update the mysql db to support utf8 but here's how you would do that in a create script (I'm not sure how gitlab creates the db)..
CREATE DATABASE db_name CHARACTER SET utf8 DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci DEFAULT COLLATE utf8_general_ci ; -Matt On Sep 3, 2014, at 8:05 AM, Sytse Sijbrandij <sy...@gitlab.com> wrote: > Hi Matt, > > I think you are right, this is probably a GitLab or MySQL problem. I don't > have an idea to solve it, it would be great if someone could write a failing > test case for it. > > Sytse > > > On Wed, Sep 3, 2014 at 3:01 PM, Matthew Fleming <matthewdflem...@gmail.com> > wrote: > Also the git commit locally had no issues, nor did the push to the server. > What failed was the generation of the pull request due to an insert problem > with mysql handling utf-8 characters. > > -Matt > > On Sep 3, 2014, at 4:19 AM, sytse <sy...@gitlab.com> wrote: > >> Git can't handle UTF-8 characters in the branch as far as I know. >> >> >> On Friday, August 29, 2014 3:57:59 PM UTC+2, Matthew Fleming wrote: >> Hey there, >> >> We are getting a 500 error when creating merge/pull requests from a branch >> that contains UTF-8 characters in the change log. Mysql freaks out about the >> unicode characters and doesn't allow the merge request to be written to the >> db. When I removed the utf8 chars things worked properly. Interestingly, the >> merge request to my own master branch (I was on a feature branch) was >> successful, so I'm thinking there is a slightly different path taken there. >> When I submitted the merge request across repositories it always failed >> however (until the character was removed). >> >> -Matt >> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "GitLab" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/gitlabhq/IIFsrJo_nV8/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> gitlabhq+unsubscr...@googlegroups.com. >> >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/gitlabhq/8081bdc4-b8ec-4822-ad5d-9124da56864c%40googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. > > > -- > You received this message because you are subscribed to the Google Groups > "GitLab" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to gitlabhq+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/gitlabhq/939B13C2-70FB-4560-AA24-F455D850115E%40gmail.com. > > For more options, visit https://groups.google.com/d/optout. > > > -- > You received this message because you are subscribed to a topic in the Google > Groups "GitLab" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/gitlabhq/IIFsrJo_nV8/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > gitlabhq+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/gitlabhq/CAJTzhG-FDoWJ%2By-ndF9z%2B%2BiwYu5tGjfEKSbGGo4demGr-XMnnQ%40mail.gmail.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "GitLab" group. To unsubscribe from this group and stop receiving emails from it, send an email to gitlabhq+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/gitlabhq/A3F40666-497B-4120-9ECB-FD98B9272610%40gmail.com. For more options, visit https://groups.google.com/d/optout.
