Closed jtlz2 closed 6 years ago
So, that's deserialization issue, and seeing the trace you received something from the server. That something wasn't matching the expected behavior it seems. Could you enable HTTP logs to see what you received from the server? To do that, turn on the HTTP logging (disabled by default):
client.config.enable_http_logger = True
and log using logging as usual in DEBUG mode.
I will try to see if I find time myself to reproduce it.
Edit: let's keep both issue opened until I know if it's msrest, or SDK or server.
It seems the service team did an update in the dev branch I didn't release yet: https://github.com/Azure/azure-sdk-for-python/pull/2614
That updates OCRResult. Could you try from that PR? You will find a direct wheel download from that PR, no need to use pip black magic to install from git.
After investigation, not a msrest issue but really a generated SDK. Track the fix in the SDK repo.
I have modified the example
image_analysis_in_stream
athttps://github.com/Azure-Samples/cognitive-services-python-sdk-samples/blob/master/samples/vision/computer_vision_samples.py
to rather carry out OCR, i.e.This gives the following Traceback:
Line 962 requires a response code of 200, so can I assume
image_stream
is valid?How do I then deserialize
OcrResult
to JSON?Is this an API version mismatch..?
Thanks for any speedy help.
(This is a cross-posting of https://github.com/Azure/azure-sdk-for-python/issues/2769)