googleapis / googleapis/google-api-ruby-client
User-rate limit exception/error returns wrong retry-after time, creating forwarding filter not possible
- Langage dominant
- Ruby
- Étoiles
- 2.9k
- Forks
- 888
- Merge moyen
- 6 min
- PR mergées (30 j)
- 218
Description
#### Environment details
- OS: macOS 15.1 (doesn't matter)
- Ruby version: ruby 3.3.6
- Gem name and version: google-apis-gmail_v1 (0.41.0)
#### Steps to reproduce
When creating a Filter via the GMail API (Google::Apis::GmailV1) which includes a forward action, this is apparently user-rate limit throttled.
In my Ruby API client I get the following error messages: rateLimitExceeded: User-rate limit exceeded. Retry after 2024-11-12T11:16:42.247Z (Forwarding rules)
Unfortunately, the time returned when to try again is wrong.
My code waits until this time plus a grace period of 60 seconds. When trying at 11:17:42 UTC I get another rateLimitExceeded: User-rate limit exceeded. Retry after 2024-11-12T11:32:42.968Z (Forwarding rules).
Even when I tried the code a couple of hours later, I still get that error on the first request. So the given retry-after time is clearly wrong.
#### Code example
```ruby
begin
@client = Google::Apis::GmailV1::GmailService.new # Authorization code skipped
criteria = Google::Apis::GmailV1::FilterCriteria.new(…some query…)
action = Google::Apis::GmailV1::FilterAction.new(forward: "test@email.com") # This is a verified address, cross-checked with list_user_setting_forwarding_addresses
filter = Google::Apis::GmailV1::Filter.new(criteria: criteria, action: action)
result = @client.create_user_setting_filter('me', filter_content)
rescue Google::Apis::RateLimitError => e
puts "Rate Limit Exceeded: #{e}
end
> User-rate limit exceeded. Retry after 2024-11-12T11:16:42.247Z (Forwarding rules)
```
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
Reproduisez la création d’un filtre Gmail avec Google::Apis::GmailV1::GmailService#create_user_setting_filter et examinez la sortie de Google::Apis::RateLimitError, en vous concentrant sur la valeur Retry after signalée. Le travail est considéré comme terminé lorsque le client indique un délai de nouvelle tentative cohérent avec la réponse du service ; l’issue ne nomme aucun fichier ni test à exécuter.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- ruby
- Domaine
- api
- Type d'issue
- Bug
- Difficulté
- 3/5
- Temps estimé
- 1-2 jours
- Activité
- À l'abandon
- Clarté
- Plutôt claire
- Accessibilité débutants
- 35/100