Opened 8 years ago

Closed 8 years ago

#5807 closed Bug (incomplete)

RPC torrent-get function returns invalid JSON

Reported by: AlmightyDragon Owned by: jordan
Priority: Highest Milestone: None Set
Component: libtransmission Version: 2.84
Severity: Normal Keywords:


I have at least 1 torrent where the JSON for a RPC request is invalid and it looks like this:

{"lastScrapeResult":"Torrent(s) not found on this tracker - hash(s): e

the e and the B are special characters and are not displayed correctly here.

I perform "torrent-get" with the field "trackerStats" under Debian.

Please fix this asap because this bug is very nasty.

Change History (2)

comment:1 Changed 8 years ago by mike.dld

"Invalid JSON" and "invalid display" are two different things. Please be more specific. If you're able to parse the response this means that JSON itself is valid. Having troubles displaying the data received is whole other story. Since this message comes from the tracker and is intended to be human-readable, you might want to contact tracker administrator add tell him/her to fix the error message (e.g. encode hash in HEX).

comment:2 Changed 8 years ago by mike.dld

  • Resolution set to incomplete
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.