It's not sustainable to have this as a maintenance script when it's needed all the time.
|mediawiki/vagrant : stretch-migration||Remove dangling reference to ORES checkModelVersions|
|mediawiki/vagrant : stretch-migration||Remove CheckModelVersions.php from ores role|
|mediawiki/vagrant : master||Remove dangling reference to ORES checkModelVersions|
|mediawiki/vagrant : master||Remove CheckModelVersions.php from ores role|
|mediawiki/extensions/ORES : master||Remove maintenance/CheckModelVersions.php|
|mediawiki/extensions/ORES : master||Update model version when it's different in Scoring|
- Mentioned In
- Blog Post: Status Update (January 30, 2018)
T182012: Deploy ORES filters to Simple Wikipedia
T184127: Add models when initializing the table
T183862: Recent Changes is broken on Dutch Wikipedia Beta on Beta Cluster
T183266: wikidata.beta.wmflabs.org/wiki/Special:RecentChanges InvalidArgumentException No model available for [goodfaith]
The best I can imagine so far is a two-prong strategy:
- When a changes feed is displayed for a wiki which a) has models configured in $wg vars, but b) no models are available, we do a synchronous CheckModelVersions. (Async would be acceptable as well, but slightly harder on us to debug.)
- Every time scores are retrieved, we compare with the (cached) database model versions. If the retrieved score models have incremented or are not included in the database models, we stuff the new model data into the db without an explicit CheckModelVersions.
We would need to log and cache exceptional conditions, e.g. one of these checks was triggered but the pulled data showed that the local configuration is in error, and the model is not actually available.