e.g. http://musicbrainz.org/recording/7f73d052-e286-43ed-a2e3-55378ae99b6e/open_edits and http://musicbrainz.org/release/ecac3be5-d4db-4c06-981d-d6d20a796ff9/open_edits
Also applies to relationships, e.g. on http://musicbrainz.org/url/ddd68e7e-3806-4c9d-9a27-dce51e800316 and http://musicbrainz.org/url/2cc1a010-2596-424a-8f4f-483555a37a7c
We're in freeze, but I'm not sure if this needs to be moved to the next fix version – what's the status here?
It is still a problem, and I don't have a solution yet.
A script to fix this is in review at http://codereview.musicbrainz.org/r/2201/
The fixup script is still running because of this "don't make big replication packets" policy. I will have a look when it's finished.
The script has finished running, but there are a few entities that it can't fix. The way the script works is if something hasn't been updated for over 20 days and still has a positive edits_pending value, then edits_pending is reset to 0. However, that release you linked above was last updated yesterday, so that one can't be fixed. I'm considering adding a daily cron job to run the script to gradually catch these remaining problems.
I've been running this script a while now, and it's still catching the odd row from time to time. I want to keep this open until the script runs without changing a single row.
Ok, the script finally ran and made no changes. I'm going to close this issue. If you find more entities who look like they are 'stuck', then please send me a message.