Last modified: 2012-04-07 13:59:27 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 T37786, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 35786 - usercontribs ucstart returned from api may result in overlapping result sets
usercontribs ucstart returned from api may result in overlapping result sets
Status: RESOLVED DUPLICATE of bug 24782
Product: MediaWiki
Classification: Unclassified
API (Other open bugs)
unspecified
All All
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-04-07 08:54 UTC by Ariel T. Glenn
Modified: 2012-04-07 13:59 UTC (History)
5 users (show)

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


Attachments

Description Ariel T. Glenn 2012-04-07 08:54:40 UTC
Version of MW: 1.20-xxx and probably as far back as usercontribs is available in the API

Because a bot or possibly a script-assisted user may edit more than once a second, use of the ucstart parameter returned in <query-continue> tags to retrieve the next bach of changes may retrieve some changes already seen in the previous batch.  For example, see below:

zh.wikipedia.org/w/api.php?action=query&list=usercontribs&ucuser=Liangent-bot&ucstart=2012-04-07T07:44:45Z

This returns ucstart of 2012-04-07T07:44:44Z but some of those changes are already in the current result set.  Retrieving the new url gets some dups:

http://zh.wikipedia.org/w/api.php?action=query&list=usercontribs&ucuser=Liangent-bot&ucstart=2012-04-07T07:44:44Z

Suggested fix: add a revision id or other tag from what would be the first row of the new result set, to the end of the parameter in these cases:
ucstart="2012-04-07T07:44:43Z|20655891"

The revid is risky if the revision is hidden or deleted by the time the new result set is requested; perhaps there's some better unique tag that can be tacked on to the parameter instead.
Comment 1 db [inactive,noenotif] 2012-04-07 13:59:27 UTC

*** This bug has been marked as a duplicate of bug 24782 ***

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


Navigation
Links