The dbus-invocation stuff that just landed broke Twitter's rate limiter.
Bug #1118878 reported by
Robert Bruce Park
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Friends |
Fix Released
|
Medium
|
Unassigned | ||
| friends (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
The Twitter rate limiter doesn't persist it's rate limiting information between invocations, which means it has no way of remembering how long it needs to wait before making the next HTTP request, which means it's possible to run afoul of Twitter's limiter and become rate limited.
It's going to need a minor overhaul in order to cache it's rate limiter data somewhere (disk? dee?), or just be removed, because it's not functioning in it's current state.
Related branches
| Changed in friends: | |
| status: | Triaged → Fix Committed |
| Changed in friends: | |
| assignee: | Robert Bruce Park (robru) → nobody |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #1 |
| Changed in friends (Ubuntu): | |
| status: | New → Fix Released |
| Changed in friends: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
This bug was fixed in the package friends - 0.1.2daily13.
---------------
friends (0.1.2daily13.
[ Robert Bruce Park ]
* Automatic snapshot from revision 145 (bootstrap)
* Friends re-publishing and re-notifying about stale tweets. (LP:
#1152417)
* The dbus-invocation stuff that just landed broke Twitter's rate
limiter. (LP: #1118878)
[ Ubuntu daily release ]
* Automatic snapshot from revision 160
-- Ubuntu daily release <email address hidden> Mon, 11 Mar 2013 10:43:35 +0000