Page MenuHomePhabricator

drcontinue parameter seems to not work
Closed, ResolvedPublic

Description

Author: mwbugzilla

Description:
After querying the deleted revisions for namespace 0 and some limit (tested with 10, 20 and 30), a drcontinue is also returned. After specifying it to continue, however, again the initial set of results (and the same drcontinue) are returned.

Repeated on 2 different wikis, one of them hosted by me.

Exchange dump (cut to save space):

Sent: Array
(

[format] => php
[maxlag] => 5
[drnamespace] => 0
[drlimit] => 30
[list] => deletedrevs
[action] => query

)

Received: Array
(

[query] => Array
     (
         [deletedrevs] => Array
             (

(--snip 30 results--)

            )
[query-continue] => Array
    (
        [deletedrevs] => Array
            (
                [drcontinue] => 0|Data Entry Jobs Winnipeg Manitoba - film jobs in prague|20120304135046
            )

    )

)

Sent: Array
(

[format] => php
[maxlag] => 5
[drnamespace] => 0
[drlimit] => 30
[drcontinue] => 0|Data Entry Jobs Winnipeg Manitoba - film jobs in prague|20120304135046
[list] => deletedrevs
[action] => query

)

Received: Array
(

[query] => Array
     (
         [deletedrevs] => Array
             (

(--snip 30 results (exactly the same ones as above)--)

            )
[query-continue] => Array
    (
        [deletedrevs] => Array
            (
                [drcontinue] => 0|Data Entry Jobs Winnipeg Manitoba - film jobs in prague|20120304135046
            )

    )

)

and so on, until I stop the bot manually.


Version: 1.18.x
Severity: normal

Details

Reference
bz35980

Event Timeline

bzimport raised the priority of this task from to Low.Nov 22 2014, 12:19 AM
bzimport set Reference to bz35980.
bzimport added a subscriber: Unknown Object (MLST).

Confirmed this bug; the problem seems to be that in "all" mode (mode #3 in the API help) it assumes drdir=newer when ordering while trying to honor it correctly in drcontinue.

A fix is in Gerrit changeset 9711.

I just noticed bug 32385 is about the same underlying problem. Perhaps one should be marked as a duplicate of the other. Either way, mentioning it here for tracking.

  • This bug has been marked as a duplicate of bug 32385 ***