Opened 9 years ago

Closed 9 years ago

Last modified 9 years ago

#5525 closed Bug (duplicate)

Invalid JSON response on rpc call

Reported by: simon.n.lindgren Owned by:
Priority: Normal Milestone: None Set
Component: Daemon Version: 2.82
Severity: Normal Keywords:
Cc:

Description

At some point transmission-daemon started generating invalid JSON in response to the torrent-get rpc call.

I have many torrents, but this is what it looks like (formatted as if it was valid):

{
    "arguments": {
        "torrents": [
            
   -- snip --

        ]
    }
    "result" "success"
}

Notice the missing comma and colon before "result" and "success" respectively.

This causes the web client and transmission-remote-gtk to break.

Change History (3)

comment:1 Changed 9 years ago by mike.dld

  • Resolution set to duplicate
  • Status changed from new to closed

Already fixed, see #5352 and #5158.

comment:2 Changed 9 years ago by simon.n.lindgren

Hmm, I didn't find those bugs while googling...

Is there a workaround or a preliminary date for when there will be a release with the fix?

comment:3 Changed 9 years ago by mike.dld

You are free to apply the patch from r14182 and test it out. I'm not aware of release schedule, sorry.

Note: See TracTickets for help on using tickets.