Skip to content
This repository has been archived by the owner on Nov 19, 2020. It is now read-only.

Include statusCode when failure to unmarshal #58

Merged
merged 1 commit into from
Sep 7, 2017

Conversation

chesleybrown
Copy link
Contributor

We experienced a bit of trouble debugging when the unmarshal failed. We were getting the following error message:

decode error status: payload is not a kubernetes protobuf object

We eventually realized it was because the body simply contained Unauthorized. But had the statusCode been included in the error message we would have realized this much quicker.

So this simply updates the unmarshal error message to include the statusCode along with the unmarshal error message.

@manute
Copy link

manute commented Sep 7, 2017

I think this issue is related to #46

@ericchiang
Copy link
Owner

lgtm, thanks!

@ericchiang ericchiang merged commit fa30591 into ericchiang:master Sep 7, 2017
conorbranagan added a commit to DataDog/datadog-agent that referenced this pull request Oct 10, 2017
* The latest version of the library includes better logging for errors
which include the status code. See ericchiang/k8s#58
* The deployment API is unavailable in older versions of Kubernetes. We
don't really _need_ this information since we can parse it from the
ReplicaSet name.
masci pushed a commit to DataDog/datadog-agent that referenced this pull request Oct 12, 2017
* [k8s] Update library, allow deployment API to fail

* The latest version of the library includes better logging for errors
which include the status code. See ericchiang/k8s#58
* The deployment API is unavailable in older versions of Kubernetes. We
don't really _need_ this information since we can parse it from the
ReplicaSet name.

* [k8s] Import log package in metadata provider
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants