Last modified: 2007-06-19 20:55:55 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 10315 - API's xml parameter 'log events start' (lestart) is broken
API's xml parameter 'log events start' (lestart) is broken
Product: MediaWiki
Classification: Unclassified
API (Other open bugs)
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2007-06-19 20:11 UTC by Waldir
Modified: 2007-06-19 20:55 UTC (History)
2 users (show)

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


Description Waldir 2007-06-19 20:11:04 UTC
If I enter, for instance, the following query:
I get in the results
   <logevents lestart="20070619143631" />
However, the results are correct. It seems to me that the xml tag shows the timestamp of the edit right after the default limit (10). And this can be seen by querying
As can be seen, the timestamp of the last entry on the list is the same as the one that was presented in the tag on the previous query:
   <item pageid="0" ns="2" title="Usuário:Jorge Bispo Lopes Fausto" type="newusers" action="create" user="Jorge Bispo Lopes Fausto" timestamp="2007-06-19T14:36:31Z" />

Please, fix this as even not compromising the results, it gets very confusing until you understand what is going on.
Comment 1 Roan Kattouw 2007-06-19 20:38:01 UTC
This is actually correct behavior. You may understand this better when you see some of the XML context:

    <logevents lestart="20070619143631" />

This means that to continue your query (i.e. to get the next ten logevents), you need to set the lestart parameter to 20070619143631. It does *not* mean the lists starts at that timestamp, although the name may lead you to think that.
Comment 2 Waldir 2007-06-19 20:41:52 UTC
Hum, I see.. it really seems to be that, though... :\

Can you think of a less ambiguous way to express that? I think it's rather confusing the way it is...
Comment 3 Roan Kattouw 2007-06-19 20:43:55 UTC
(In reply to comment #2)
> Can you think of a less ambiguous way to express that? I think it's rather
> confusing the way it is...

The query-continue thing is pretty clear to me. I agree that it should be documented, but then the API hardly documents what it returns. Someone should work on that. 

Comment 4 Yuri Astrakhan 2007-06-19 20:46:07 UTC awaits you!
Comment 5 Roan Kattouw 2007-06-19 20:47:26 UTC
(In reply to comment #4)
> awaits you!
If you mean me, I prefer writing the code ;) But it wouldn't be a bad idea to recruit one or two people to write documentation.
Comment 6 Yuri Astrakhan 2007-06-19 20:55:55 UTC
Doc is for the API. API is for devs.  Devs like to write code. Devs do not like to write docs...  Catch 22 :)

No, i didn't mean you, I meant everyone :)

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