docs: HTTP API Status Codes

[lidel]

This PR updates HTTP API docs with a newly generated version from ipfs-inactive/http-api-docs#23, which adds docs about status codes in HTTP API

Any issues should be reported in the above issue.
This should be merged if upstream PR gets accepted.

[lidel]

@hsanjuan any idea why cluster panics in https://circleci.com/gh/ipfs/docs/621 ?

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x9c4c80]

goroutine 84 [running]:
main.main.func6.1(0xc00002b574, 0xc0004d6280, 0xc0000b4780)
	github.com/ipfs/ipfs-cluster/cmd/ipfs-cluster-ctl/main.go:436 +0x320
created by main.main.func6
	github.com/ipfs/ipfs-cluster/cmd/ipfs-cluster-ctl/main.go:417 +0x60f
Exited with code 2

[hsanjuan]

It seems there were no api changes at all in last release. nice

[hsanjuan]

@hsanjuan any idea why cluster panics in https://circleci.com/gh/ipfs/docs/621 ?

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x9c4c80]

goroutine 84 [running]:
main.main.func6.1(0xc00002b574, 0xc0004d6280, 0xc0000b4780)
	github.com/ipfs/ipfs-cluster/cmd/ipfs-cluster-ctl/main.go:436 +0x320
created by main.main.func6
	github.com/ipfs/ipfs-cluster/cmd/ipfs-cluster-ctl/main.go:417 +0x60f
Exited with code 2

I don't know, but this seems to have been fixed...

[jessicaschilling]

@lidel @hsanjuan I'm still seeing the same CircleCI failure. Any ideas?

[hsanjuan]

@olizilla will update the deploy docker image thing. Then we should just re-trigger the build and it should not panic anymore.

[jessicaschilling]

@olizilla -- can you please let me know when you've deployed the Docker image @hsanjuan refers to in this issue, so this can be merged? Thank you!

[olizilla]

It's all good to go. We couldn't connect to cluster. It's fixed now.

[jessicaschilling]

@olizilla Thank you so much!