You should likely be able to use the ssh review command
instead.
-Martin
Ugh. Gson doesn't like the JSON object tree the server built as a
response to your call. That probably means you tripped an error path
with your request, and that particular error path is apparently not
well tested.
> DEBUG headers - >> POST /gerrit/rpc/UserPassAuthService HTTP/1.1
> DEBUG headers - >> Content-Type: application/json
> DEBUG headers - >> Host: <myHost>
> DEBUG wire - >> "{"jsonrpc":"2.0","method":"authenticate","params":
> ["myUser","myPass"],"id":1}"
> DEBUG wire - << "HTTP/1.1 500 condition failed: false[EOL]"
The request almost seems correct. Have you tried also setting
Content-Length and adding "; charset=UTF-8" to the Content-Type
header?
Content-Length: 73
Content-Type: application/json; charset=UTF-8
{"jsonrpc":"2.0","method":"authenticate","params":["test","user"],"id":3}
> I compared the JSON I'm sending to what I saw in firebug and it looks
> right to me (I hardcoded the "id" to 1 - I don't think that's the
> problem though).
Yea, the id doesn't really matter here. Its just a sequential counter
from the web UI.
You are right, the ssh review command doesn't (yet) support commenting
on files within a patch set. Missing feature. :-\