'watch' doesn't handle non-Status errors properly

[ankon]

npm info it worked if it ends with ok
npm info using [email protected]
npm info using [email protected]
npm info lifecycle [email protected]~prestart: [email protected]
npm info lifecycle [email protected]~start: [email protected]

> [email protected] start /app
> node src/index.js "--namespace=development"

[2017-05-19 14:58:45.004] [INFO] [default] - Watching queues at 0...
undefined:1
Forbidden: "/apis/aws.k8s.collaborne.com/v1/namespaces/development/queues?watch=true&resourceVersion=0"
^

SyntaxError: Unexpected token F in JSON at position 0
    at Object.parse (native)
    at DestroyableTransform._flush (/app/node_modules/auto-kubernetes-client/src/index.js:144:24)
    at DestroyableTransform.<anonymous> (/app/node_modules/readable-stream/lib/_stream_transform.js:115:49)
    at DestroyableTransform.g (events.js:291:16)
    at emitNone (events.js:86:13)
    at DestroyableTransform.emit (events.js:185:7)
    at prefinish (/app/node_modules/readable-stream/lib/_stream_writable.js:494:12)
    at finishMaybe (/app/node_modules/readable-stream/lib/_stream_writable.js:506:7)
    at endWritable (/app/node_modules/readable-stream/lib/_stream_writable.js:514:3)
    at DestroyableTransform.Writable.end (/app/node_modules/readable-stream/lib/_stream_writable.js:484:41)

This is similar to d037e91, where it was fixed for non-watch resources.

[ankon]

Note that we should be checking the error code as well -- it seems we're just assuming that the response will be in json-stream format and is always successful.