Last modified: 2014-08-11 20:29:41 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 T47894, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 45894 - Async saving of page translation edits?
Async saving of page translation edits?
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
Translate (Other open bugs)
unspecified
All All
: Low minor (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-03-08 11:04 UTC by Nemo
Modified: 2014-08-11 20:29 UTC (History)
8 users (show)

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


Attachments

Description Nemo 2013-03-08 11:04:55 UTC
Two edits to two translation units were collated in a single edit to the translation page: <https://meta.wikimedia.org/w/index.php?title=Special:Contributions/Nemo_bis&dir=prev&offset=20130308105148&limit=3&target=Nemo+bis>
Is this intentional? If yes we should document how the edit summary is chosen, so that the user knows what to write.
Comment 1 Niklas Laxström 2013-03-08 18:14:40 UTC
Each save triggers complete refresh of the translation page. There is a race condition here and the order is essentially random.

1) Multiple translations are updated about the same time
2) Some of them can complete faster
3) A hook runs after each save is complete, loading the most recent translation units from master. It saves the updated translation page using the summary of the translation unit which triggered the hook.
4) For the other saves, they also load the most recent translations, but as the content is the same, no revision is recorded in the history.

The harm is mostly only a confusion to the users.
Comment 2 Nemo 2013-03-08 18:50:28 UTC
Thanks.

(In reply to comment #1)
> The harm is mostly only a confusion to the users.

Sure.
What's strange is that I didn't save the two messages so quickly, several seconds passed.
Comment 3 Nemo 2013-03-13 13:25:16 UTC
Here a manual edit (translation) was attributed to FuzzyBot: http://www.mediawiki.org/w/index.php?title=Fr%C3%A9ttinga%2Fit&diff=659306&oldid=659295
If you check the previous edits you'll see that no diff is associated to the correct timestamp or summary.
Comment 4 Nemo 2013-04-12 20:19:46 UTC
Here it took three dummy edits to get all the updates (confirming outdated translations) applied to the translation page: https://meta.wikimedia.org/w/index.php?title=Free_knowledge_based_on_Creative_Commons_licenses/es&diff=5389201&oldid=5386388
Comment 5 Nemo 2014-06-06 07:00:26 UTC
Curiously, it's possible to trigger an update of a translation page even with a null (API) edit to a translation unit page: https://www.mediawiki.org/w/index.php?title=Academic_hub/it&diff=prev&oldid=1023362 doesn't have any corresponding edit in Translations namespace because content is the same as a (2 months old) previous edit.
Comment 6 Ricordisamoa 2014-08-11 20:29:41 UTC
(In reply to Nemo from comment #5)
> Curiously, it's possible to trigger an update of a translation page even
> with a null (API) edit to a translation unit page.

I think this is intentional. For instance, I used my bot to clear some usages of obsolete images: https://meta.wikimedia.org/wiki/Special:Contributions/SamoaBot?offset=20130630&limit=36

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


Navigation
Links