bob pasker

I think it might be worthwhile to conduct a high-level review of the ML API before merging it in. There are consistency and orthogonality issues that caused me a lot...

:+1:

+1 on the 'error handling' it seems that HTTP responses (eg `GET //_search` AKA `response = client.search(index="")` on a non-existing index) are thrown as errors rather than returned in the...

its actually worse because there's no semantic error checking, eg `*** Error: RequestError(400, 'resource_already_exists_exception', 'index [opinions/FduukSQQQcuRcp4ZK0w51g] already exists') ` requires: ``` except TransportError as e: if e.status_code == 400 and...

yep, there are probably also other errors that I haven't encountered yet that could probably benefit from specialization

I am having this problem as well. my app doesn't use any @werkzeug classes at all, just flask and flask-gzip. perhaps someone from @werkzeug can help.