Aaron Lehmann c94c2a47a3 Don't return empty errcode.Errors slices ... If this slice ends up empty after parsing the HTTP response body, it means the body is not well-formed. We've probably encountered an error message produced by something that uses a different JSON schema, or an error that just happens to validate as JSON. An empty errcode.Errors slice is not a very useful thing to return, since its Error() output is just `<nil>`. Detect this case, and instend return an UnexpectedHTTPResponseError. Signed-off-by: Aaron Lehmann <aaron.lehmann@docker.com>		2016-03-14 10:27:01 -07:00
..
auth	Add client ID to token fetch to GET endpoint	2016-03-09 12:44:55 -08:00
transport	Fix some typos in comments and strings	2016-02-23 22:33:38 +01:00
blob_writer.go	Adds new storagedriver.FileWriter interface	2016-03-08 16:37:44 -08:00
blob_writer_test.go	Add ability to pass in substitution args into an Error	2015-07-15 11:02:10 -07:00
errors.go	Don't return empty errcode.Errors slices	2016-03-14 10:27:01 -07:00
errors_test.go	Don't return empty errcode.Errors slices	2016-03-14 10:27:01 -07:00
repository.go	Enable proxying registries to downgrade fetched manifests to Schema 1.	2016-02-22 17:56:48 -08:00
repository_test.go	Add manifest put by digest to the registry client	2016-01-26 14:20:23 -08:00