Re: [fossil-users] JSON API exit codes

2012-06-25 Thread Stephan Beal
On Sun, Jun 24, 2012 at 10:45 PM, Steve Waggoner wrote: > Perhaps another way to be consistent is have the "fossil json xxx" always > return 0 (success) if command just returns valid json. That's essentially what happens right now. The only cases i know about which exit with non-0 do not generat

Re: [fossil-users] JSON API exit codes

2012-06-24 Thread Steve Waggoner
Perhaps another way to be consistent is have the "fossil json xxx" always return 0 (success) if command just returns valid json. Then include a special success code in the "resultCode" attribute when the operation was actually successful. Steve On Sun, Jun 24, 2012 at 11:49 AM, Stephan Beal wrote

Re: [fossil-users] JSON API exit codes

2012-06-24 Thread Stephan Beal
On Sun, Jun 24, 2012 at 6:17 PM, Steve Waggoner wrote: > In general whenever a "fossil json xxx" command fails the exit code is not > zero. But sometimes "user xxx" subcommands return zero (success) even when > they fail. > Hi! Thanks for the feedback, but that's a documented behaviour of JSON m

[fossil-users] JSON API exit codes

2012-06-24 Thread Steve Waggoner
I am using "fossil version 1.22 [5dd5d39e7c] 2012-03-19 12:45:47 UTC" compiled with JSON API. In general whenever a "fossil json xxx" command fails the exit code is not zero. But sometimes "user xxx" subcommands return zero (success) even when they fail. For example the following is expected to e