SVN Decode error UTF-8

[Tom Schäfer]

Hi all,

we use ReviewBoard 6.0 beta1 with the docker-compose setup.
We have linked our SVN repository against the Tool and run into issues with encoding.

If we have umlauts in the commit message or the content the following error occurs in the logsfile:

2023-06-23 09:25:45,616 - ERROR - - reviewboard.scmtools.svn.pysvn - Failed to generate diff using pysvn for revisions 135481:135482 for path svn+ssh://svn@host/repos: 'utf-8' codec can't

decode byte 0xe4 in position 550: invalid continuation byte

Traceback (most recent call last):

File "/venv/lib/python3.8/site-packages/reviewboard/scmtools/svn/pysvn.py", line 252, in diff

diff = force_bytes(self.client.diff(

UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe4 in position 550: invalid continuation byte

2023-06-23 09:25:45,620 - ERROR - - reviewboard.reviews.managers - Unable to update new review request from commit ID 135482 on repository ID=2: Unable to get diff revisions 135481 through 135482: 'utf-8' co

dec can't decode byte 0xe4 in position 550: invalid continuation byte

Traceback (most recent call last):

File "/venv/lib/python3.8/site-packages/reviewboard/scmtools/svn/pysvn.py", line 252, in diff

diff = force_bytes(self.client.diff(

UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe4 in position 550: invalid continuation byte

During handling of the above exception, another exception occurred:

Traceback (most recent call last):

File "/venv/lib/python3.8/site-packages/reviewboard/scmtools/svn/__init__.py", line 251, in get_change

diff = self.client.diff(base_revision, revision)

File "/venv/lib/python3.8/site-packages/reviewboard/scmtools/svn/pysvn.py", line 263, in diff

raise SCMError(

reviewboard.scmtools.errors.SCMError: Unable to get diff revisions 135481 through 135482: 'utf-8' codec can't decode byte 0xe4 in position 550: invalid continuation byte

I think the error comes with pysvn.Can someone help here?

[Christian Hammond]

Hi Tom,

Do you know what character set's being used for those commit messages?

Christian

--
Supercharge your Review Board with Power Pack: https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
---
You received this message because you are subscribed to the Google Groups "Review Board Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/reviewboard/3300a88b-e360-4d22-8d10-f9144fe8aea6n%40googlegroups.com.

--

Christian Hammond

President/CEO of Beanbag

Makers of Review Board

[Tom Schäfer]

Hi Christian,

yes the commits should all be using ANSI standard encoding as we use Windows the the commits but umlauts and ß/€ are non printable characters there.

Tom

[Tom Schäfer]

just for clarification: The encoding of the file content is ANSI but the files don´t contain clean ANSI. The commit messages are no problem.