Last modified: 2007-08-18 23:30:22 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 T12979, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 10979 - Contribs not migrated after rename.
Contribs not migrated after rename.
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
Renameuser (Other open bugs)
unspecified
PC Windows XP
: Normal major (vote)
: ---
Assigned To: Nobody - You can work on this!
: shell
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-08-17 22:06 UTC by Magnus animum
Modified: 2007-08-18 23:30 UTC (History)
6 users (show)

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


Attachments

Description Magnus animum 2007-08-17 22:06:26 UTC
I was recently renamed on en.wikipedia from "Magnus animum" to "Animum". ~3 hours afterward, I noticed *none* of my contribs had been migrated; in fact, it was at ~6:00 AM EDT that ~1000 *were* migrated. I dunno if a dev with root/shell access needs to manually migrate them, if it has something to do with the job queue (yes, robchurch, more job queue paranoia :-)), or if it is a really severe Renameuser problem. Any suggestions/possible fixes?
Comment 1 Aaron Schulz 2007-08-17 22:11:52 UTC
Have any other users had this?
Comment 2 Aaron Schulz 2007-08-17 22:14:27 UTC
(In reply to comment #1)
> Have any other users had this?
> 

Gah, checking the logs, I see that the last 10 are not going through either.
Comment 3 R 2007-08-17 22:26:09 UTC
Umm...has anyone noticed the job queue has been over a million since a slave crashed a few days ago? Name changes are pretty low on queue priority, so you'll probably be waiting a while. Check [[w:en:Special:Statistics]]
Comment 4 E 2007-08-17 22:29:34 UTC
(In reply to comment #3)
> Umm...has anyone noticed the job queue has been over a million since a slave
> crashed a few days ago? Name changes are pretty low on queue priority, so
> you'll probably be waiting a while. Check [[w:en:Special:Statistics]]

Yes, indeed. You possibly may be looking at quite a while. There may be a possibility of speeding it up though.
Comment 5 Magnus animum 2007-08-17 22:31:06 UTC
(In reply to comment #3)
> Umm...has anyone noticed the job queue has been over a million since a slave
> crashed a few days ago? Name changes are pretty low on queue priority, so
> you'll probably be waiting a while. Check [[w:en:Special:Statistics]]
> 

I don't think renames have anything to do with the job queue...
Comment 6 Majorly 2007-08-17 22:32:47 UTC
I renamed Magnus animum on Meta yesterday, and the contributions didn't change straightaway either.
Comment 7 Rob Church 2007-08-17 22:35:24 UTC
RenameUser shouldn't be putting updates for the `revision` table into the job queue; this strikes me as madness; the table should be indexed well enough that the updates can be done along with the `user` update.

This will now require the attention of a shell user (to do a one-off job queue run for the English Wikipedia), and I suggest altering the current, paranoid job queue use in the extension.
Comment 8 Magnus animum 2007-08-17 22:41:21 UTC
(In reply to comment #7)
> RenameUser shouldn't be putting updates for the `revision` table into the job
> queue; this strikes me as madness; the table should be indexed well enough that
> the updates can be done along with the `user` update.
> 
> This will now require the attention of a shell user (to do a one-off job queue
> run for the English Wikipedia), and I suggest altering the current, paranoid
> job queue use in the extension.
> 

Should someone contact brion/starling/avar, or will they know about this bug quickly w/o being emailed (since a lot of devs seem to...)?
Comment 9 Casey Brown 2007-08-18 14:53:48 UTC
(In reply to comment #8)
> (In reply to comment #7)
> > RenameUser shouldn't be putting updates for the `revision` table into the job
> > queue; this strikes me as madness; the table should be indexed well enough that
> > the updates can be done along with the `user` update.
> > 
> > This will now require the attention of a shell user (to do a one-off job queue
> > run for the English Wikipedia), and I suggest altering the current, paranoid
> > job queue use in the extension.
> > 
> Should someone contact brion/starling/avar, or will they know about this bug
> quickly w/o being emailed (since a lot of devs seem to...)?

There's a mailing list and a live feed we can get. :-)  But if you really feel they need to know and would be able to fix it, go ahead and contact them (probably best on IRC).
Comment 10 Majorly 2007-08-18 15:01:43 UTC
(In reply to comment #9)
> (In reply to comment #8)
> > (In reply to comment #7)
> > > RenameUser shouldn't be putting updates for the `revision` table into the job
> > > queue; this strikes me as madness; the table should be indexed well enough that
> > > the updates can be done along with the `user` update.
> > > 
> > > This will now require the attention of a shell user (to do a one-off job queue
> > > run for the English Wikipedia), and I suggest altering the current, paranoid
> > > job queue use in the extension.
> > > 
> > Should someone contact brion/starling/avar, or will they know about this bug
> > quickly w/o being emailed (since a lot of devs seem to...)?
> There's a mailing list and a live feed we can get. :-)  But if you really feel
> they need to know and would be able to fix it, go ahead and contact them
> (probably best on IRC).

They were already contacted via those means.
Comment 11 JeLuF 2007-08-18 23:30:22 UTC
I've reset the job queue runners, they were hanging after the master switches. enwiki's queue lenght is slowly decreasing.

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


Navigation
Links