[twitter] Catch rate limit errors in JSON responses

Bug #670855 reported by marcog on 2010-11-04
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Stefano Rivera

Bug Description

12:25 < marcog> tibid: http://twitter.com/#!/AI_AGW/status/29640123173
12:25 < tibid> marcog: Huh?
12:25 < marcog> tibid: tweet 29640123173
12:25 < tibid> marcog: What?
12:26 < marcog> tibid: latest tweet from marcog
12:26 < tibid> marcog: I can only see the Fail Whale

If the last one reports fail whale, why don't the first two?

Related branches

marcog (marco-gallotta) wrote :

Okay, so it seems it shouldn't be reporting the fail whale at all. What's up?

12:43 <&marcog> tibid: get http://twitter.com/#!/AI_AGW/status/29640123173
12:43 < tibid> marcog: 200 OK text/html; charset=utf-8
12:44 <&marcog> tibid: latest tweet from AI_AGW
12:44 < tibid> marcog: I can only see the Fail Whale

Stefano Rivera (stefanor) wrote :

OK, this is actually twitter's rate limiting. We should catch this.

{"error":"Rate limit exceeded. Clients may not make more than 150 requests per hour.","request":"\/statuses\/show\/29640123173.json"}

Changed in ibid:
importance: Low → Wishlist
status: New → Triaged
summary: - Not always reporting fail whale
+ [twitter] Catch rate limit errors in JSON responses
Changed in ibid:
milestone: 0.1.1 → 0.2.0
assignee: nobody → Stefano Rivera (stefanor)
status: Triaged → In Progress
Changed in ibid:
status: In Progress → Fix Committed
Changed in ibid:
milestone: 0.2.0 → 0.1.1
Changed in ibid:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers