Merge lp:~robru/friends/avatar-expiry-workaround into lp:friends
Status: | Merged | ||||
---|---|---|---|---|---|
Approved by: | Robert Bruce Park | ||||
Approved revision: | 173 | ||||
Merged at revision: | 172 | ||||
Proposed branch: | lp:~robru/friends/avatar-expiry-workaround | ||||
Merge into: | lp:friends | ||||
Diff against target: |
84 lines (+16/-7) 3 files modified
debian/changelog (+8/-2) friends/service/dispatcher.py (+4/-1) friends/utils/avatar.py (+4/-4) |
||||
To merge this branch: | bzr merge lp:~robru/friends/avatar-expiry-workaround | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Ken VanDine | Approve | ||
PS Jenkins bot (community) | continuous-integration | Approve | |
Robert Bruce Park | Approve | ||
Review via email: mp+155653@code.launchpad.net |
Commit message
Stop expiring old avatars from the cache.
Description of the change
So Ken, in light of the fact that we are quite late in the freeze, and the "correct" avatar fix would require new API (and thus a FFe), I propose that we land this workaround, and then early in the S cycle we can worry about fixing this "properly".
This commit simply neuters our ExpireAvatar dbus method (without removing it, so nothing that uses that API needs to be altered), and then it adds a simple mtime check to the download logic, causing it to trigger a redownload even if the file is already in the cache. End result: cached avatars are never deleted, but stale ones are redownloaded monthly.
This way older posts in the stream will not be robbed of their Avatar images.
Next cycle we can look at a) adding new GetCachedAvatar dbus method, b) updating libfriends API, and c) updating gwibber to know that the avatar field no longer contains cached data but raw URLs. (I almost wonder if maybe Qml doesn't provide some kind of caching mechanism that might be a bit more streamlined than having to query DBus for cached downloads...)
FAILED: Continuous integration, rev:171 /code.launchpad .net/~robru/ friends/ avatar- expiry- workaround/ +merge/ 155653/ +edit-commit- message
No commit message was specified in the merge proposal. Click on the following link and set the commit message (if you want a jenkins rebuild you need to trigger it yourself):
https:/
http:// jenkins. qa.ubuntu. com/job/ friends- ci/12/ jenkins. qa.ubuntu. com/job/ friends- raring- amd64-ci/ 12
Executed test runs:
SUCCESS: http://
Click here to trigger a rebuild: s-jenkins: 8080/job/ friends- ci/12/rebuild
http://