lp:~pitti/friends/fix-autopkgtest

Branch merges

Propose for merging

No branches dependent on this one.

Merged into lp:friends at revision 162

PS Jenkins bot (community): Approve (continuous-integration) on 2013-03-18

Ken VanDine: Approve on 2013-03-18

Diff: 35 lines (+13/-2)

3 files modified

debian/changelog (+10/-0)
debian/tests/control (+1/-1)
debian/tests/unit (+2/-1)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

164. By Martin Pitt on 2013-03-18

Add dbus-x11 test dependency, for D-BUS autospawning.

163. By Martin Pitt on 2013-03-18

Run autopkgtests under xvfb, otherwise D-BUS autospawn fails.

162. By Martin Pitt on 2013-03-18

debian/tests/unit: Redirect stderr to stdout, as unittest discover writes
to stderr by default. Succeeding autopkgtests must not write anything
there.

161. By PS Jenkins bot on 2013-03-12

Releasing 0.1.2daily13.03.11.1-0ubuntu1 to ubuntu.

Approved by Robert Bruce Park.

160. By Robert Bruce Park on 2013-03-08

    Start using since_id= on Twitter API requests. (LP: #1152417)

    This was accomplished by implementing two new classes, and ended up
    simplifying some of the RateLimiter code as a side effect.

    The first new class is called JsonCache. It is a subclass of dict,
    which attempts to populate it's initial state by reading in a json
    text file at a configurable location, and also adds a new "write()"
    method that dumps the json back out to the same location. This class
    was a generalization of what we were already doing inside the
    RateLimiter, so it should not be considered a "new feature" if we are
    going to butt heads with today's feature freeze.

    The second new class is a subclass of JsonCache, which enforces that:

    A) keys may not contain slashes, to avoid it getting polluted with
    every search term ever searched for, or every message that's ever been
    replied to ever, it only observes the values of the "main" streams,
    such as "messages", "mentions" and "private", although those values
    are not hardcoded so it's flexible to adapt to new streams in the
    future.

    B) values must be ints (tweet_ids), and values can only be
    incremented. This is so that we can easily just throw every observed
    tweet_id into the cache, and it only records the largest (newest) one.

    The end result is that we now have two new files located at
    ~/.cache/friends/twitter_ids.json and
    ~/.cache/friends/identica_ids.json which track the newest tweet_id
    that we have ever seen for each of the streams that we publish to.
    These values are then consulted to form the since_id= argument to
    several of Twitter's API endpoints, which solves bug #1152417.

    As an added bonus, this also greatly reduces our network usage because
    we are no longer redownloading duplicate messages over and over, so if
    there are no new messages, Twitter is now returning an empty list of
    Tweets rather than a large list of stale tweets.

    This commit includes full test coverage for all new code. Fixes: https://bugs.launchpad.net/bugs/1152417.

Approved by Ken VanDine, PS Jenkins bot.

159. By Ken VanDine on 2013-03-08

set back to UNRELEASED

158. By Robert Bruce Park on 2013-03-08

Release 0.1.2-0ubuntu1

157. By Robert Bruce Park on 2013-03-04

Bring up DBus interface sooner during startup.

We were having some racy timeout issues where we'd be invoked by dbus,
but then didn't get the dispatcher up in time to respond to dbus
method invocations before dbus timed out on us, because waiting for
the DeeModel to sync was too slow.

Instead, we bring up the dispatcher first, but also acquire the
_publish_lock, which prevents the dispatcher from trying to publish
prematurely (eg, before caches have been populated and and the
DeeModel syncronized). Then once the DeeModel syncs, we release the
lock and allow the dispatcher to function as normal.

Ken & I both tested this branch throughout the entire weekend and not
a single timeout occurred the entire time, so this is a big win.

156. By Robert Bruce Park on 2013-03-01

Fix quantal compatibility.

155. By Robert Bruce Park on 2013-02-28

Persist Twitter rate limiter data (LP: #1118878)