702350 - Make better use of caching with currentVersions.py

Status: RESOLVED FIXED

(Socorro :: General, task)

Comment 1

[Robert Helmer [:rhelmer]]

This appears to be the cause of most of the intermittent errors people have alerted me to since the last release, here is an example:

2011-11-23 06:26:18 -08:00 --- error: Web_Service 28 connect() timed out! while retrieving http://socorro-mware-zlb.webapp.phx1.mozilla.com/bpapi/201106/current
/versions/product_name%2Cversion_string which was HTTP status 0

Comment 2

[[github robot]]

Commits pushed to https://github.com/mozilla/socorro

https://github.com/mozilla/socorro/commit/2ec94ed318a88fb6ea5a10493012060c12a748dd
Fixes Bug 702350 - Add caching by default, and set up a way to clear the cache when we intentionally change the data.

https://github.com/mozilla/socorro/commit/5d8a58e9a9e0c9da83590bd7d479e05786c33089
Merge pull request #179 from brandonsavage/bug702350

Fixes Bug 702350 - Add caching by default, and set up a way to clear the...

Comment 3

[Robert Helmer [:rhelmer]]

Notes for QA - I tested this locally (by adding debug logging to see what the cache hit looked like before/after), looks as-expected after (cache is set once, then all pages fetch the same cache instead of each having their own).

This code affects every page (product/value pulldowns) so I think this could be qa- and the automated tests should help flush out any regressions.

Comment 4

[[github robot]]

Commit pushed to https://github.com/mozilla/socorro

https://github.com/mozilla/socorro/commit/e17d6c3b6536903cd040dde6c3a289f27039f09c
Fixes Bug 702350 - Add caching by default, and set up a way to clear the cache when we intentionally change the data.