Incorrect last_updated date in plugin API

[SergeyBiryukov]

Just noticed a weird thing in plugin API:

$api = plugins_api( 'plugin_information', array( 'slug' => 'all-in-one-seo-pack' ) );
echo $api->last_updated;

This currently returns 1969-12-31, and results in "Last Updated: 44 years ago" message in plugin update dialog in the admin.

The plugin directory says "Last Updated: 2013-9-6", however the ​current latest changeset was in August.

[SergeyBiryukov]

Saw a similar error in the Plugins Trac: meta-185.plugins-trac.png​ (note the Age column). Clicking any of the files on the left results in the error message: "No changeset 10993 in the repository".

[coffee2code]

This issue has been fixed for the originally mentioned plugin and the less than two dozen others with the same issue.

It looked like some sort of transient issue caused their last-updated dates to fail to set properly, so the UNIX epoch time (the default) was the result. Very few were affected and none have exhibited the issue in the few days since I fixed it. The plugins didn't share anything in common in terms of age, size, number or frequency of commits, number of tags, time of their last update, authors, etc.

As for what was raised in comment 2, that's a different issue. It looks at though the trac DB may have corrupted records for commits ranging from 10001 through 13076. Only trac seems to be affected. The plugin shown in the screenshot (​http://wordpress.org/plugins/just-unzip/) has its plugin page properly generated and the code is available through SVN (​http://plugins.svn.wordpress.org/just-unzip/). That warrants a separate ticket for systems to take a look at if anyone cares about those old commits through trac.