[00:02:50] RECOVERY - Response time of WDQS on einsteinium is OK: OK: Less than 5.00% above the threshold [120000.0] [09:02:57] hoo: i'll join the 13:00 meeting via hangout [09:06:30] DanielK_WMDE_: Cool [09:07:57] DanielK_WMDE_: Regarding the serialization… ok, makes sense… just seemed somewhat inconsistent to me [09:09:19] hoo: well, we can be inconsistent about the keys, or about the values. i haven't really decided on which is worse in principle, but changing this now, or doing it differently for new entity types, seems like a bade idea. [09:09:50] DanielK_WMDE_: Agreed [09:09:58] Will comment that on the change in question [09:18:32] Sorry for the serialization mess, Amir1… I'll try to get it reviewed today [09:19:05] hoo: Hey, no problem. I'm planning to make jenkins work again in master [09:19:14] (probably finish off Jakob patch) [09:19:30] yeah, that would be cool [09:19:30] right now, I'm working on Anomie's comments [09:23:35] DanielK_WMDE_: hm… should we use "claims" in the Serialization (for legacy reasons?) [09:24:00] Hey Amir1! Sorry for the lack of feedback lately. I'll catch up on code review today. I will probably also be working over the weekend. I twised my ankle, so I'll be stting alone at home anyway. [09:24:03] Item/ PRoperty do it [09:24:08] MediaInfo doesn't [09:24:23] MediaInfo doesn't? really? *sigh* [09:24:43] I vote to fix this. let's be consistent about hte keys for statements across all entity types that have them [09:24:45] $this->statementListDeserializer->deserialize( $serialization['statements'] ) [09:24:50] Yeah, agreed [09:25:08] DanielK_WMDE_: Sure, amazing, thanks :) I heard from Abraham what happened :D [09:25:12] MEdiaInfo is still very alpha, so it would even be ok to break reading of old data [09:25:34] Yeah, we should create a bug about it [09:25:43] don't think we need to worry about b/c in any way [09:25:55] only developer instance/ the test thing on wmflabs use it [09:26:00] * instances [09:26:00] Amir1: i just came back from the doctor. now i know that nothing is broken. that's something, at least :) [09:26:16] ok, i'm going afk for a bit. will be back for the meeting at 13:00 [09:26:20] \o/ [09:26:22] Sure [09:26:48] hoo: can you file the ticket? should be high prio - it's trivial, but should be fixed asap [09:27:00] * DanielK_WMDE_ wonders if it was him who got this wrong [09:27:17] might well have been my bad [09:27:22] DanielK_WMDE_: No, Bene did the patches and Thiemo reviewed [09:30:05] DanielK_WMDE_: Amir1 https://phabricator.wikimedia.org/T149410 [09:30:56] thanks [09:31:26] let me fix that in lexeme [09:31:45] :) [09:33:05] hoo: Should I change deserializeStatements function name to deserializeClaims too? [09:34:53] Amir1: You can, but don't need to [09:34:59] either can be argued for [09:35:06] we still call them Statements in the code [09:35:19] and are using a StatementsListDeserializer [09:35:32] yeah, I thought the same [09:35:42] let's go with Statement here [09:38:49] oops [09:38:52] :D [09:46:37] hoo: ping! [09:46:53] One sec :) [09:52:23] hoo: Simple question. Why did you introduced a second setting for the lua feature instead of reusing the same setting for both the parser function and the same feature in lua? [09:52:41] Thiemo_WMDE: Because of the name of the setting [09:52:46] mostly [09:52:55] what if we change it? [09:55:39] Thiemo_WMDE: Not sure, the settings are temporery [09:56:00] sure. [09:56:26] my argument is, it's the same amount of patches and changed lines anyway. but easier to understand if it's only 1 setting. [09:56:38] Not sure [09:56:49] What would you call it? [09:56:59] Anyway, I' afk for a bit [09:57:06] statementsthingymadoo? ;-) [09:57:40] :P [10:04:47] hoo daily? [10:04:59] https://hangouts.google.com/hangouts/_/wikimedia.de/jklmt-tla-daily?authuser=0 [10:28:19] Is somebody admin on https://de.wikipedia.beta.wmflabs.org and add my account there to some groups? [10:36:13] Thiemo_WMDE: SOrry...I am a "Global_sysops", but "You do not have permission to add or remove user rights." :/ [10:36:28] Uh. :-( [10:39:18] I just need to be in the group so nobody needs to approve my changes. [10:39:38] Or I need somebody approving what I'm going to do on https://de.wikipedia.beta.wmflabs.org/w/index.php?title=Statements&stable=0&redirect=no [10:40:01] yeah, Iyou'd need a local admin or a 'crat to assign rights :/ [10:40:08] But I can accept changes [11:08:55] Josve05a: It works! Cool, thank you very much! [11:08:56] https://de.wikipedia.beta.wmflabs.org/wiki/Statements [11:53:24] oooooh, https://upload.wikimedia.org/wikipedia/commons/c/cb/Wikidata_items_map_with_difference%2C_April_2016_to_Oct_2016.png [12:05:50] addshore: nice! but i think i would turn the color scheme around: color is density, and brightness is rate of change [12:06:28] Maybe for the next one ;) [12:40:18] Jonas_WMDE: Hey! Thanks for the fix to WDQS! [12:41:00] Jonas_WMDE: I still have no idea how the packaging of all that works (I probably only need to spend a few minutes with SMalyshev to understand that, but I have still not taken that time) [12:41:00] sorry for the mistake I should use firefox more often m) [12:41:18] Jonas_WMDE: cross browser compatibility is hard! [12:43:20] gehel I think stas will handle it in the evening [12:43:45] Jonas_WMDE: ok, I'll be there in any case. Ping me if you need me [12:43:53] thanks [13:11:53] Thiemo_WMDE: Still need something at beta? [13:12:16] dont think so. thanks. [13:12:21] ok :) [13:51:21] Thiemo_WMDE: mw.wikibase.entity:formatStatements works on beta now :) [13:51:29] manually verified [17:18:52] Why can't I find documentation on wbc_entity_usage database table? [17:23:55] Because https://www.mediawiki.org/wiki/Wikibase/Schema has not been updated? [17:29:34] party! [17:36:27] Dispenser: https://github.com/wikimedia/mediawiki-extensions-Wikibase/blob/master/docs/usagetracking.wiki [17:36:41] that'S not specifically for the db table, but it should help [17:56:19] PROBLEM - Response time of WDQS on einsteinium is CRITICAL: CRITICAL: 11.11% of data above the critical threshold [300000.0] [17:59:23] RECOVERY - Response time of WDQS on einsteinium is OK: OK: Less than 5.00% above the threshold [120000.0] [18:03:34] PROBLEM - Response time of WDQS on einsteinium is CRITICAL: CRITICAL: 12.50% of data above the critical threshold [300000.0] [18:09:13] RECOVERY - Response time of WDQS on einsteinium is OK: OK: Less than 5.00% above the threshold [120000.0] [18:09:52] DanielK_WMDE_: Thank you [18:14:33] PROBLEM - Response time of WDQS on einsteinium is CRITICAL: CRITICAL: 12.50% of data above the critical threshold [300000.0] [18:18:43] RECOVERY - Response time of WDQS on einsteinium is OK: OK: Less than 5.00% above the threshold [120000.0] [18:38:47] DanielK_WMDE_: Q: There seem to be "holes" in wb_items_per_site and wbc_entity_usage. e.g. https://www.wikidata.org/wiki/Q127582 Is missing from wikidatawiki_p.wb_items_per_site [18:44:18] Yah! The imdb linker bot is up and running :-D [18:44:20] nvm, was mis-reading [[Andrew_Dawson]] and [[Andre_Dawson]] [18:44:21] 10[1] 04https://www.wikidata.org/wiki/Andrew_Dawson13 => [18:44:24] 10[2] 04https://www.wikidata.org/wiki/Andre_Dawson [19:16:42] https://twitter.com/StrynWM/status/791989101536903168 [19:48:38] Nemo_bis: Works for me… in which browser can you reproduce this? [19:50:32] Just relaying [19:51:39] Ok, think this has been fixed :) [20:08:12] yes it's fixed now :) [20:21:04] Cool :) [20:22:33] Hi. Got a beginner question: can I link a wikidata item to an article on test.wikipedia.org? If so, what site ID should I use to do so? [20:24:29] bearND: Not really… test.wikipedia.org "thinks" it's the English Wikipedia [20:24:38] so you can only link articles with the same name on enwiki [20:25:49] hoo: thanks. I guess same for test2 wiki. Are there any other Wikipedia wikis that are not allowed? [20:27:14] No current ones [20:27:40] I might then try to link a sandbox item to my user page. The description on https://www.wikidata.org/wiki/Q4115189 claims it should be possible but I don't see an example. [20:27:57] Yeah, you can do it (temporarily) [20:28:52] Why not permanently? I would like to set up something that I could use for automated testing of our Android code, which would edit WD descriptions [20:30:01] bearND: That sounds like a use case for testwikidata [20:30:22] Or do you also use enwiki for other testing code? Is that a thing? [20:31:58] it happens in a few cases. I'd be happy to use testwikidata for this if I can make it work with test.wikipedia.org [20:32:36] Basically the edit flow is started from a WP article [20:33:42] I've created https://test.wikidata.org/wiki/Q25395 and want to link it to https://test.wikipedia.org/wiki/Wikipedia_Android_app [20:35:27] I get 'The site ID "testwiki" is unknown' [20:42:10] yeah [20:42:16] that's difficult indeed [20:42:35] we wanted to change testwiki to use testwikidata, but that never happened (for reasons I don't know) [20:43:37] hoo: oh well. I guess I'll use the temporary solution for manual testing then. Thanks! [23:01:18] hi wikidata. relative noob here. could someone point me to a COI policy of sorts for images? I just replaced an image with a higher resolution one I uploaded myself and felt a twinge of "this could be abused". [23:02:24] most of us who upload images to common like to see the images used. if we don't already have a good one -- all the better. for that reason, making adding to wikidata, where appropriate, part of my uploading process seems like it makes sense. as long as it is indeed arguably the best available image for a given item, is this controversial? [23:02:28] common=commons