Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 2047 by UnicodeDecodeError: 'utf8' codec can't decode byte

* NOTE: Do not post confidential information in this bug report. *
*       If you need immediate support, please contact            *
*                             *

What version are you running?

What's the URL of the page containing the problem?

What steps will reproduce the problem?
1. On Windows or OSX add a typographical double quote to the Perforce description of the CLN you are attempting to post ( e.g. on windows Alt + 0147 ).

2. post the review using post-review <CLN>

What is the expected output? What do you see instead?

Expected to post a review, but get error message

User Message

<html xmlns=""; xml:lang="en" lang="en">
  <title>500 - Internal Server Error | Review Board</title>
  <h1>Something broke! (Error 500)</h1>
   It appears something broke when you tried to go to here. This is either
   a bug in Review Board or a server configuration error. Please report
   this to your administrator.

Server Message:

File "/build/toolchain/lin32/python-2.6.1/lib/python2.6/json/", line 294, in _iterencode
    yield encoder(o)

UnicodeDecodeError: 'utf8' codec can't decode byte 0x93 in position 0: unexpected code byte

What operating system are you using? What browser?

Centos 5.5 x86_64

Please provide any additional information below.

From what I can tell by default Windows and OSx will encode these type of characters as ASCII using one byte. The Django framework will attempt to decode these using utf-8 but fails because not encoded as expected.

This primarily appears to have when users have these type of characters within the change description on Perforce.

It appears potentially that scmtool/ could be patched to replace these characters within function parse_change_desc ( e.g. <str>.decode('utf-8', 'replace'). Haven't given it much thought yet in case there are any side-effects to this but at least the review appears to be successfully posted.

You received this message because you are subscribed to the Google Groups 
"reviewboard-issues" group.
To post to this group, send email to
To unsubscribe from this group, send email to
For more options, visit this group at

Reply via email to