Description of problem:
I just managed to import a set of key/values which seems to upset the web UI greatly. Loading certain systems or the Activity page results in a 500 error.
Version-Release number of selected component (if applicable):
As far as I can tell, this is because of a key/value which contains a non-ASCII character. oocalc helpfully replaced several of my hyphens with en-dash, em-dash, or something else I didn't actually want. The offending character is this one:
IBM RSA II – ibm-x3950m2-02-rsa.ovirt.rhts.eng.bos.redhat.com
I'm going to try to fix this in the DB to make beaker useful again, but I'd like to see a fix in the future. Either beaker needs to handle extended characters, or the import process needs to reject them.
I expect a test case to be built for this that works with UTF8 characters.
Looking at this...
If we want to deal properly with utf8, we need to do a couple more things.
1) Set up DB tables for utf8
2) Set up connector for utf8
3) Ensure the code deals in utf8 strings and not ascii
4) Display content/type as utf8
1 already is the case. 2 is easy.
3 is dealt with in some areas of the code, but it isn't systematic.
4 is already done.
This change enables System details to have UTF8 characters (not the system name though).
It also allows general viewing of UTF8 characters (although not in the URL).
Test is here
merged. will be in next release.
(In reply to comment #4)
> Test is here
Ray, thanks. is there a git link to the test source?
Be great if you could link from the beaker UI to the test source. But I think that is an RFE we have outstanding.
We keep them in CVS, try something like this:
cvs -d :ext:firstname.lastname@example.org:/cvs/dist co tests/distribution/beaker/import_utf8