René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Do not throw error on empty LRO response","articleBody":"[operation.py](https://github.com/googleapis/python-api-core/blob/master/google/api_core/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 see [`ExportInsightsDataResponse`](https://cloud.google.com/contact-center/insights/docs/reference/rpc/google.cloud.contactcenterinsights.v1#exportinsightsdataresponse) which is an empty response that is returned after the `ExportInsightsData` LRO is complete.\r\n\r\nWe should update [operation.py](https://github.com/googleapis/python-api-core/blob/master/google/api_core/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](https://github.com/googleapis/gax-nodejs/pull/1087).","author":{"url":"https://github.com/TrucHLe","@type":"Person","name":"TrucHLe"},"datePublished":"2021-08-18T18:01:58.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/257/python-api-core/issues/257"}