Re: Getting error: 'ascii' codec can't decode byte 0xc3 in position 1264: ordinal not in range(128)

That change did miss the release. It will be present in RC1. Christian On Tue, Oct 10, 2017 at 7:27 AM, Nicolas Ferrari wrote: > Hi, the issue is still present in the 3.0.x version. > > Regards, > > On Monday, October 2, 2017 at 11:11:17 PM UTC+2, Christian Hammond

Re: Getting error: 'ascii' codec can't decode byte 0xc3 in position 1264: ordinal not in range(128)

Hi, the issue is still present in the 3.0.x version. Regards, On Monday, October 2, 2017 at 11:11:17 PM UTC+2, Christian Hammond wrote: > > Hi Ali, > > We have a fix for this in our tree > (commit 23fbc2f28742442835c4c275e81c1ad0cb163ed6), which will be part of > the next 2.5.x release. > >

Re: Getting error: 'ascii' codec can't decode byte 0xc3 in position 1264: ordinal not in range(128)

Hi Ali, We have a fix for this in our tree (commit 23fbc2f28742442835c4c275e81c1ad0cb163ed6), which will be part of the next 2.5.x release. Christian On Mon, Oct 2, 2017 at 7:05 AM, Ali Lokhandwala wrote: > Hi, > I am getting this error on our repo files when raising

Getting error: 'ascii' codec can't decode byte 0xc3 in position 1264: ordinal not in range(128)

Hi, I am getting this error on our repo files when raising reviews post commit using: - root - Unable to update new review request from commit ID 949e6492ab2c243e8828c8329218089000a4da39 on repository ID=5: 'ascii' codec can't decode byte 0xc3 in position 1264: ordinal not in range(128)