Last modified: 2012-07-27 15:44:28 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T31401, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 29401 - Need a way to detect age of WURFL db and possible updates
Need a way to detect age of WURFL db and possible updates
Status: RESOLVED WONTFIX
Product: Wikimedia Mobile
Classification: Unclassified
Generic (Other open bugs)
--
All All
: High normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2011-06-14 20:45 UTC by Tomasz Finc
Modified: 2012-07-27 15:44 UTC (History)
5 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Tomasz Finc 2011-06-14 20:45:42 UTC
Since the WURFL db is constantly getting updated we should have an easy way to know that its out of date with what we have in production.
Comment 1 Patrick Reilly 2011-06-14 21:00:36 UTC
The XML file has the following tags at the beginning of the file.
    
<ver>www.wurflpro.com - 2010-12-31 05:04:30</ver>
    <last_updated>Fri Dec 31 05:10:11 -0600 2010</last_updated>
     ...
Comment 2 Patrick Reilly 2011-06-14 21:09:12 UTC
I updated the database to the following:

    <ver>www.wurflpro.com - 2011-04-24 12:07:53</ver>
    <last_updated>Sun Apr 24 12:09:17 -0500 2011</last_updated>
Comment 3 Tomasz Finc 2011-06-15 00:24:38 UTC
It would be great if we could automate this and then set an alarm whenever the WURFL db drifted past X days/months. That way it could easily be automated.
Comment 4 p858snake 2011-06-15 00:30:27 UTC
Do we really need to detect the age? could we just not have a cron script that updates it every X days no matter if there is a new version or not?
Comment 5 Tomasz Finc 2011-06-15 00:53:16 UTC
We should have a cron update it as the first step no matter what ... but crons break down and I'd hate have this as  silent failure and then lose updates because no one knows that its busted. 

It would be great to have this just happen and alarm if it explodes.
Comment 6 p858snake 2011-06-15 01:42:20 UTC
I'm sure we have the cron spam something if it breaks in a similar way to LU spams the irc channel if it does.
Comment 7 Mark A. Hershberger 2011-06-21 23:23:47 UTC
I would suggest working with OPs to have them implement something in Nagios.

Alternatively, you could start working on something that would be like WordPress's way to notify you if there are updates for WP or an extension.  It would be great if we could build an update-checker extension (I think it would have to be an extension to mitigate privacy concerns, but I could be wrong) that other extensions (like the mobile extension) could plug into.
Comment 8 Max Semenik 2012-07-27 15:44:28 UTC
No more WURFL, yay!

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links