[09:37:50] I'm assuming the js2 stuff will soon be available on trunk after reading the blog posts about the usability stuff going on WMF wiki's as default. Any ETA on that? [12:22:06] JeroenDeDauw: JS2 is not going to exist as such [12:22:18] but its functionality, in bits and pieces, will be available over the coming months [12:22:24] what particularly are you thinking about? jQuery? [16:59:59] werdna: yeah, that and the i18n stuff of MwEmbed, the add media wizard and the scaffolding for dialogs I presume there is. [19:42:23] JeroenDeDauw: As of the next software update (supposed to happen like next week I think), we'll have jQuery in core [19:42:36] As for dialogs support: that's in jQuery UI, which extensions currently include individually [19:42:41] AMW will not be going live just yet [19:47:33] RoanKattouw: Ok. What's AMW though? [19:48:26] add media wizard [19:48:32] michael dale's stuff [19:52:37] I know. But it's not on trunk ATM :( [19:58:12] RoanKattouw: Can you help me out with the limit parameter in extensions/Storyboard/api/ApiQueryStories.php? I looked at the other API modules using it, but am a bit mistified by how it works. [20:01:03] Looking [20:01:06] ViewVC is slow as hell [20:01:24] Seems you got it right [20:01:42] $this->addOption( 'LIMIT', $params['limit'] ); --> needs $params['limit'] + 1 [20:01:55] So your query-continue code will work [20:02:22] The reason for requesting one more entry is to be able to detect whether there's more results and to grab the ID/whatever of the next result to set query-continue to [20:02:49] Looks like you should be continuing by story_modified as that's what you're sorting by [20:03:22] You may want to sort and continue on (story_modified, story_id) instead to make sure it's unique [20:13:58] RoanKattouw: What about $this->setContinueEnumParameter( 'continue', "" ); ? I don't get what i'm supposed to do there.3 [20:14:53] OK so let me tell you how continuing queries works [20:15:04] First, you need to identify a tuple of fields that your sort on and that's identical [20:15:20] You're currently sorting by story_modified DESC [20:15:45] So a good candidate for paging would be (story_modified, story_id) , which is unique [20:15:56] (i.e. sort by modified and use ID as a tiebreaker) [20:16:05] So in practice you'd take the following steps [20:16:19] Sort by story_modified DESC, story_id DESC (yes, DESC on ID, not ASC, or indexing won't work) [20:16:30] Add an index on (story_modified, story_id) [20:17:01] Use $this->setContinueEnumParameter( 'continue', wfTimestamp(TS_MW, $row->story_modified) . '|' . $row->story_id ); [20:17:43] Then if $params['continue'] is set, you'd use $continue = explode( $params['continue'], '|' ); , then verify its length is exactly 2 and throw an error otherwise (see other extensions) [20:17:54] Then you'd construct a WHERE clause like: [20:18:33] WHERE story_modified > {$cont[0]} OR (story_modified = {$cont[0]} AND story_id = {$cont[1]}) [20:19:45] Ah oops [20:20:06] WHERE story_modified < {$cont[0]} OR (story_modified = {$cont[0]} AND story_id <= {$cont[0]}) [20:23:18] RoanKattouw: So what does setContinueEnumParameter do? Adds the conetnts for the continue parameter of the query output? [20:23:34] Yes [20:24:07] Oh.. [20:24:14] Ok, then it does make sense yeah :) [20:24:28] Thanks :d [20:29:05] *JeroenDeDauw thinks it now seems so oviouse [23:34:33] I've added some documentation to keep track of tesla, and its VMs: http://ryandlane.com/wiki/Category:Servers [23:34:56] It'll keep track of the allocated vs available storage, so we know how much we have left. [23:51:45] This kind of documentation should really be on wikitech.wikimedia.org