Last modified: 2014-04-16 15:52:23 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 T47892, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 45892 - Make Wikidata changes appear quicker in the watchlist on the client
Make Wikidata changes appear quicker in the watchlist on the client
Status: VERIFIED FIXED
Product: MediaWiki extensions
Classification: Unclassified
WikidataClient (Other open bugs)
unspecified
All All
: High major with 2 votes (vote)
: ---
Assigned To: Wikidata bugs
http://lists.wikimedia.org/pipermail/...
:
Depends on: 39384
Blocks:
  Show dependency treegraph
 
Reported: 2013-03-08 10:33 UTC by Michael M.
Modified: 2014-04-16 15:52 UTC (History)
15 users (show)

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


Attachments

Description Michael M. 2013-03-08 10:33:42 UTC
I have [[de:Hilfe:Suche]] on my watchlist, which is connected with [[d:Q5525084]]. On my watchlist on de.wikipedia I see the two changes from 12:xx UTC, 7 March. But the next change (8:20 UTC, 8 March) is still not on my watchlist. This is now two hours ago, and many other Wikipedia changes are on my watchlist on the top. When this change will eventually appear, it will be somewhere in the middle of a list of changes I already looked at and won't look at again.

This means that I probably won't see that change once it appears on my watchlist (unless I'm really looking for it). The change should appear almost immediatly, otherwise it's useless, at least for users with big watchlists.
Comment 1 Aude 2013-03-08 11:54:34 UTC
probably need more cron jobs.... or part of the issue could be in the job queue part, but I think the dispatcher would be the issue here
Comment 2 Aude 2013-03-08 13:26:39 UTC
https://gerrit.wikimedia.org/r/#/c/52797/ although it might not be that simple or maybe not enough cronjobs.
Comment 3 Lydia Pintscher 2013-03-09 16:37:17 UTC
Getting more reports about this.
Comment 4 Mikko Silvonen 2013-03-10 07:24:10 UTC
I assume that this affects also recent changes? I have seen Wikidata changes only sporadically on the fiwiki recent changes list, although I have switched on the option. Currently I don't see any Wikidata changes among the last 500 edits.

http://fi.wikipedia.org/w/index.php?title=Toiminnot:Tuoreet_muutokset&limit=500
Comment 5 Per A.J. Andersson 2013-03-17 12:59:44 UTC
Is this bug related the lacking iw links in this article?

http://sv.wikipedia.org/wiki/Casterman

The article was added eight hours ago. It still lacks iw links in or out of it. I remember having added the svwp link at Wikidata, but the history says otherwise.

http://www.wikidata.org/w/index.php?title=Q568077&action=history

This adding by an IP address was done while I was asleep. The added description was done by me a short while ago.

Has the system been ok overnight?
Comment 6 Per A.J. Andersson 2013-03-18 15:06:20 UTC
(In reply to comment #5)
> Is this bug related the lacking iw links in this article?
> 
> http://sv.wikipedia.org/wiki/Casterman
> 
> The article was added eight hours ago. It still lacks iw links in or out of
> it.
> I remember having added the svwp link at Wikidata, but the history says
> otherwise.
> 
> http://www.wikidata.org/w/index.php?title=Q568077&action=history
> 
> This adding by an IP address was done while I was asleep. The added
> description
> was done by me a short while ago.
> 
> Has the system been ok overnight?

Now the IW links are OK. Best of wishes/P
Comment 7 Mikko Silvonen 2013-03-21 18:01:40 UTC
Per, missing iw links are bug 45839.
Comment 8 Per A.J. Andersson 2013-03-21 19:20:40 UTC
Thanks. I'll get back to the right bug report then, when I happen upon the bug again. :-)
Comment 10 Nemo 2013-04-07 10:15:42 UTC
If https://www.wikidata.org/wiki/Special:DispatchStats can be trusted, the situation is getting worse and worse: the number for "Stalest" seems to increase by 400.000 every day, and I've never seen it going down in the last few days.
Comment 11 Lydia Pintscher 2013-04-26 15:08:24 UTC
This seems to be fine now. Closing.
Comment 12 Nemo 2013-04-26 15:22:04 UTC
(In reply to comment #11)
> This seems to be fine now. Closing.

Does it? Oldest change to dispatch is still 3 days old.
Are bots running freely?
Comment 13 denny vrandecic 2013-05-08 11:33:42 UTC
The DispatchStats have been at 0 for several weeks now. Verifying.
Comment 14 Nemo 2013-05-09 21:38:08 UTC
(In reply to comment #13)
> The DispatchStats have been at 0 for several weeks now. Verifying.

Denny, I don't understand, why then does https://www.wikidata.org/wiki/Special:DispatchStats *always* have the "Oldest" in "Change log statistics" being *exactly* 72 h before?
If IDs means something, there's currently a 2 millions items backlog.
Comment 15 denny vrandecic 2013-05-13 10:46:33 UTC
Nemo, that's a good question. I will forward it to Daniel K., who wrote the code.

As you can see below, in

https://www.wikidata.org/wiki/Special:DispatchStats#Dispatch_statistics

the "stalest" wiki has usually 0 minutes lag, which is what is relevant. I am not sure what the Change log statistics show. Maybe the whole log that is still in memory, whether or not it has been dispatched?
Comment 16 Nemo 2013-05-13 10:52:43 UTC
(In reply to comment #15)
> the "stalest" wiki has usually 0 minutes lag, which is what is relevant. I am
> not sure what the Change log statistics show. Maybe the whole log that is
> still
> in memory, whether or not it has been dispatched?

Daniel recently rewrote the special page into, which now says «Change log statistics shows the number and the date for the oldest and the most recent items currently in the queue», so it seems it's about current rather than old queue.

Also: «"Lag" is the time between the change last dispatched to the wiki, and the last change performed on Wikidata», so it's correct to infer it equals the lag between submission and dispatch only if the queue follows a FIFO model (does it?).
Comment 17 Nemo 2013-09-10 16:40:28 UTC
Now [[d:Special:DispatchStats]] still shows a queue of exactly 3 days in the top section, but only 68116161-67530667 = ~ 600k items instead of 2 millions.
Comment 18 Malafaya 2013-09-10 17:24:49 UTC
Right now, not exactly 3 days but nearly:

	ID	Timestamp
Oldest	67541606	17:15, 7 September 2013
Newest	68126934	17:24, 10 September 2013
Comment 19 Nemo 2013-09-10 17:31:47 UTC
(In reply to comment #18)
> Right now, not exactly 3 days but nearly:

That's because they are pruned by a cronjob every 20 min IIRC.

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


Navigation
Links