On Sun, Jun 24, 2012 at 6:17 PM, Steve Waggoner <[email protected]>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 mode. It's a side-effect of: a) we never want an HTTP 500 to be sent in CGI mode (which is what happens if fossil exits with non-0). b) most of the JSON code doesn't distinguish between CGI and CLI modes. It would be feasible to exit with non-0 in CLI mode, but that would mean another inconsistency between CGI/server and CLI modes. i'm up for hearing arguments for/against either approach. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
