jszwedko / circleci-cli Goto Github PK

As mentioned in #4 if you do not have an API token set, you currently get an opaque error message about having to log in. We should catch this and provide an error message telling the user that they need to set -t or CIRCLE_TOKEN.

It'd be useful to include bash and zsh autocompletion.

eyal@eyal-Lenovo-Y50-70:~/develop/git/booyah-android$ circleci-cli projects
json: cannot unmarshal string into Go value of type bool

This is AFTER i've set export CIRCLE_TOKEN=my_token (before that i got 401 u need to loging first which is also bad error message since your cli does not have 'login' command, should be 'please supply API TOKEN either using -t or using CIRCLE_TOKEN environment variable.'

circleci-cli projects results in

`parsing time "null" as ""2006-01-02T15:04:05Z07:00"": cannot parse "null" as """``

Other commands work fine

the program fails to start with this error message:

json: cannot unmarshal string into Go value of type bool

I am using the 0.2.0-pre binaries.

I am presuming this is because the schema for the CircleCI API changed, but I don't know how to track it down at any lower level.

Panics:

panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xb code=0x1 addr=0x0 pc=0x40f113]

goroutine 1 [running]:
main.main.func9(0xc8200ba0f0)
        /Users/jszwedko/gopath/src/github.com/jszwedko/circleci-cli/main.go:573 +0x6f3
github.com/jszwedko/circleci-cli/vendor/github.com/codegangsta/cli.Command.Run(0x7db910, 0x5, 0x0, 0x0, 0x0, 0x0, 0x0, 0x8186e0, 0x13, 0x0, ...)
        /Users/jszwedko/gopath/src/github.com/jszwedko/circleci-cli/vendor/github.com/codegangsta/cli/command.go:127 +0x1052
github.com/jszwedko/circleci-cli/vendor/github.com/codegangsta/cli.(*App).Run(0xc8200a4200, 0xc82000a500, 0x2, 0x2, 0x0, 0x0)
        /Users/jszwedko/gopath/src/github.com/jszwedko/circleci-cli/vendor/github.com/codegangsta/cli/app.go:159 +0xc2f
main.main()
        /Users/jszwedko/gopath/src/github.com/jszwedko/circleci-cli/main.go:697 +0x3545

cc/ @stephenchu

Hi.
If i had -d | --debug that might:

1. print the full uri + headers of the request
2. print the full body of the request\ response in an orderly manner
3. print error in the line they occur like stacktrace

i could have discovered more easily where the error i get comes from and why...

Maybe integrate with show?