Catching rate limit exceptions

I highly doubt I will reach the threshold of 400 reqs per second but just incase how should I handle any rate limit exceptions I might encounter, here is a sample of code I am using currently:

static void Main(string[] args)
        {
            var credential = GoogleCredential.FromFile(AppDomain.CurrentDomain.BaseDirectory + "license.json")
                .CreateScoped(ImageAnnotatorClient.DefaultScopes);
            var channel = new Grpc.Core.Channel(
                ImageAnnotatorClient.DefaultEndpoint.ToString(),
                credential.ToChannelCredentials());
            var client = ImageAnnotatorClient.Create(channel);
            // Load the image file into memory
            var image = Image.FromUri("http://lincolnshiretoday.net/mag/wp-content/uploads/2017/07/high-street-lbig-web.jpg");
            // Performs label detection on the image file
            var labels = client.DetectLabels(image);
            foreach (var label in labels)
            {
                // Description
                // Score
                Console.WriteLine(label.Description + " - " + label.Score);
                Console.WriteLine(Environment.NewLine);
            }
            Console.ReadLine();

        }

[jskeet]

Confirmed: the error status code is ResourceExhausted. I’d expect this to be consistent across APIs, and I know that’s the case for Speech for example.

Closing as I think we’ve answered everything we can here - exactly how you handle that error is up to your application, as I mentioned before.

[jskeet]

One side note by the way: Image.FromUri doesn’t load the image into memory. Instead, the URI is sent in the request. If you want to load the image data into memory and then send that in a request, use FetchFromUri or FetchFromUriAsync instead.

Finally trying to provoke the error so I can confirm its status.