-
Notifications
You must be signed in to change notification settings - Fork 21
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
Production: reviews for -0 and -1 cause server error #78
Comments
@katyhuff if this also happens in prod, I'll change the title to remove staging. |
yep, this is happening in prod. |
Is this an issue with utf8 support in the backend on those columns? Can the values be remapped to some other |
I just checked and the vote column is of a latin1 encoding so perhaps that is the cause. |
(This also probably means we will break people's names) |
Indeed, we have been, and @aterrel suggested we'd fix it before we announced speakers (see email below from @certik . So, you can fix two birds with this one UTF8 stone! Goooooooooo Sheila!!!!! On Mon, Mar 31, 2014 at 10:33 AM, Ondřej Čertík [email protected] wrote: I put in my name as Ondřej Čertík, but the website shows my name as: Ond?ej ?ertík [email protected] Looks like some unicode errors. So for now I fixed it by just using Ondřej Scipy-organizers mailing list |
argargarg I haven't fixed it yet because I am at pycon and did everything yesterday. Perhaps also today too! Hoping today! |
A fix would be nice for tutorial reviews but not mandatory. We have a small On Sun, Apr 13, 2014 at 6:53 AM, Sheila Miguez [email protected]:
Kristen M. Thyng |
I can take a look - but don't see the database - I guess it's using different credentials than the ones I am using... Jim On Apr 13, 2014, at 6:53 AM, Sheila Miguez wrote:
|
Hi all, I emailed more of a braindump, but here is a shorter recap: Before doing anything in prod I wanted to check locally, and did a mysqldump. Well, this was silly of me since mysqldump does not dump exactly to a file with the encoding I would want. Now I would like to have a way to get this without first serializing to a text file so that I can try the alter commands with some verisimilitude before wacking the prod data willy-nilly. I've passed along the key to Jim! I hope we get this done soon! The beast of character encoding is not yet slain. |
I went ahead and posted to the symposion mailing list to ask for more help. https://groups.google.com/forum/#!topic/pinax-symposion/OJxw2vkzzX0 And while writing up a description I realized I had not explicitly stated here that votes are varchar(2) and not int. So take that in to consideration while reviewing this bug. |
The traceback on https://groups.google.com/forum/#!topic/pinax-symposion/OJxw2vkzzX0 ('BIGINT UNSIGNED value is out of range') looks different from the one which started this thread ('Incorrect string value:'). But I concur with jlaura: '\xE2\x88\x921' is the utf-8 encoding of '−1', which doesn't fit in 2 latin-1 characters. '−1' is u'\u2212' which doesn't seem to be transcodable losslessly to latin-1: would it be possible to work around in the short term by doing .replace('−', '-') when updating, or using '-' more globally? |
Hi folks. I'm getting an email about this about once a day. Just wanted to bump it up. If it can't be fixed, maybe it can be removed? |
While testing reviews, I found that ranks of -0 and -1 cause a server error. log excerpts:
The text was updated successfully, but these errors were encountered: