Bug 749353 - Beaker is not UTF8 Safe
Summary: Beaker is not UTF8 Safe
Keywords:
Status: CLOSED DUPLICATE of bug 749441
Alias: None
Product: Beaker
Classification: Retired
Component: web UI
Version: 0.7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified vote
Target Milestone: ---
Assignee: Dan Callaghan
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-26 19:09 UTC by Sean Waite
Modified: 2014-08-12 04:34 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-10-27 22:44:25 UTC


Attachments (Terms of Use)

Description Sean Waite 2011-10-26 19:09:57 UTC
Description of problem:

Insertion of UTF8 data into the System fields causes 500 errors during both a CSV export and when trying to view the action over on the Activities page


Version-Release number of selected component (if applicable):

0.7.3


Steps to Reproduce:
1. Put UTF8 Data into the system section
2. Try and export the Systems CSV, or view the action in Activity

  
Actual results:

500 ISE

Expected results:

A copy of the CSV downloaded, or the ability to see the action in Activity

Additional info:

Might be related to the bug fixed in BZ#584592

Comment 1 Dan Callaghan 2011-10-27 03:51:35 UTC
What data exactly did you insert? All strings in Beaker are (or should be) handled as UTF8-encoded Unicode.

Comment 2 Dan Callaghan 2011-10-27 03:54:11 UTC
We do, however, keep having problems with MySQL silently truncating our data across UTF8 character boundaries (such as bug 652334). Could that be what happened here?

Comment 3 Sean Waite 2011-10-27 13:58:12 UTC
I didn't insert anything, someone else did. We noticed the issue originally when we went to export the Systems CSV. I searched through the Activities log, but kept hitting a 500. After speaking with bpeck in IRC, he determined there was some sort of UTF8 character in the data somewhere that was causing it to choke. 

All I really know is that the data was inserted sometime between 
2011-10-26 05:28:31 -04:00 and 2011-10-25 22:09:37 -04:00

It's possible the data is being truncated, if I can figure out what record was modified to include the UTF8 stuff, I might be able to tell you more.

Comment 7 Dan Callaghan 2011-10-27 22:44:25 UTC
This particular issue was fixed in Beaker with a database change. Bug 749441 is how it happened.

*** This bug has been marked as a duplicate of bug 749441 ***


Note You need to log in before you can comment on or make changes to this bug.