Likelybad and Verylikelybad predictions catches too much edits that are good:
https://pl.wikipedia.org/w/index.php?hidebots=1&hidecategorization=1&hideWikibase=1&hidelog=1&limit=100&days=30&enhanced=1&damaging__likelybad_color=c3&damaging__verylikelybad_color=c5&title=Specjalna:Ostatnie_zmiany&highlight=1&urlversion=2&uselang=en
https://ores.wikimedia.org/v3/scores/plwiki/50818911?models=damaging
Probably started after T175180.
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Fixes damaging/goodfaith config for plwiki | mediawiki/services/ores/deploy | master | +2 -2 |
Change 388252 had a related patch set uploaded (by Halfak; owner: halfak):
[mediawiki/services/ores/deploy@master] Fixes damaging/goodfaith config for plwiki
Change 388252 merged by Halfak:
[mediawiki/services/ores/deploy@master] Fixes damaging/goodfaith config for plwiki
Mentioned in SAL (#wikimedia-operations) [2017-11-02T22:39:56Z] <halfak@tin> Started deploy [ores/deploy@82a13ae]: T179621
The deploy finished. However, it looks like a bunch of bad scores got cached and will continue to show up in Wikipedia until we can get them purged (@Ladsgroup, do you know a good way of handling this?)
For the time being, new scores should be much better. Sorry for the difficulty and thanks for reporting to us.
I think we can run
mwscript extensions/ORES/maintenance/PurgeScoreCache.php --wiki plwiki --all
Will that also reload some recent score or just delete off all of the current scores?
It should be resolved by now, ores_classification doesn't store anything after one month, the version gets automatically updated. etc. Nothing to do here.