Do not throw error on empty LRO response #257
Labels
priority: p2
Moderately-important priority. Fix may not be included in next release.
type: bug
Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
operation.py throws an error if an LRO finishes but returns an empty response (the error message that it throws is "Unexpected state: Long-running operation had neither response nor error set"). However some APIs, such as Contact Center Insights, end LRO without setting either result or error (but set
done: true
). For example, please seeExportInsightsDataResponse
which is an empty response that is returned after theExportInsightsData
LRO is complete.We should update operation.py to return an empty response instead of an error when it encounters an empty LRO. For reference, we found a similar issue in the NodeJS operation library and it was fixed here.
The text was updated successfully, but these errors were encountered: