Ticket #1917 (closed bug: fixed)

Opened 22 months ago

Last modified 18 months ago

UnicodeDecodeError with long torrent names

Reported by: OmegaPhil Owned by:
Priority: major Milestone: 1.4.0
Component: new_console Version: master (git branch)
Keywords: Cc: nick, non7top@…

Description

After apparently successfully connecting to a localhost instance of deluged via deluge-console, masses of the following occur:

exceptions.UnicodeDecodeError?: 'ascii' codec can't decode byte 0xe2 in position 8: ordinal not in range(128)

See log attached.

Client Version: 1.3.900-dev Libtorrent Version: 0.15.7.0

Attachments

errors.log (9.2 KB) - added by OmegaPhil 22 months ago.
Log of errors
0002-Fix-UnicodeDecodeError-with-long-torrent-names.patch (1.1 KB) - added by Cas 22 months ago.

Change History

Changed 22 months ago by OmegaPhil

Log of errors

Changed 22 months ago by OmegaPhil

One torrent was seeding for testing purposes: [gg]_Sacred_Seven_-_06_[6A405769].mkv

Changed 22 months ago by Cas

Changed 22 months ago by Cas

  • cc nick added

I think this is the correct fix for the problem.

Changed 22 months ago by Cas

  • summary changed from exceptions.UnicodeDecodeError on connecting deluge-console to deluged to UnicodeDecodeError with long torrent names

Changed 22 months ago by OmegaPhil

I can confirm the console ui works now.

Changed 20 months ago by non7top

  • cc non7top@… added

I can confirm that this patch applies to 7227c97cacd6c3a7a1cf3d75e8dcd04e0eb71693 and fixes the issue.

Changed 18 months ago by non7top

This still applies to current git master and does fix the issue. Please commit the patch to git.

Changed 18 months ago by Cas

  • status changed from new to closed
  • resolution set to fixed

Thanks, I knew I had missed one :)

Fixed in master:  9d16b500

Note: See TracTickets for help on using tickets.