Support Retry() while using response iterator #12731
Labels
api: cloudchannel
Issues related to the Channel Services API.
status: investigating
The issue is under investigation, which is determined to be non-trivial.
Per recommendation of support case GCP #51120117 I'm opening a ticket here. Not sure if this is a bug report, feature request, or I'm just doing something wrong, but it appears the basic Retry() functionality for google-cloud-channel (and maybe others) only works if the limit is reached when the initial request is made. If a limit is reached while paging through the response iterator, Retry() is not implemented.
Example code:
Running three simultaneous executions of this script will result in a RESOURCE_EXHAUSTED error. Immediately running a single instance of the script (while still within the window to be rate limited) will properly implement the Retry() with exponential backoff until the limit is removed. Once it can progress, it will fail again shortly while paginating through
response.pages
with another RESOURCE_EXHAUSTED.The text was updated successfully, but these errors were encountered: