[00:00:12] <aude>	 but disabling, it's not broken
[00:02:10] <aude>	 maybe requires running jobs
[00:07:23] <bd808>	 aude: when you can recreate locally, I think https://gerrit.wikimedia.org/r/#/c/313680/ will fix it. It would also need testing with something that causes a dberror to see if that still works right too.
[00:10:11] <icinga-wm_>	 PROBLEM - Response time of WDQS on wdqs1002 is CRITICAL: CRITICAL: 10.00% of data above the critical threshold [300000.0]
[00:14:20] <aude>	 ok
[00:15:13] <icinga-wm_>	 RECOVERY - Response time of WDQS on wdqs1002 is OK: OK: Less than 5.00% above the threshold [120000.0]
[00:40:17] <icinga-wm_>	 PROBLEM - Response time of WDQS on wdqs1002 is CRITICAL: CRITICAL: 10.00% of data above the critical threshold [300000.0]
[00:42:47] <icinga-wm_>	 RECOVERY - Response time of WDQS on wdqs1002 is OK: OK: Less than 5.00% above the threshold [120000.0]
[02:10:54] <icinga-wm_>	 PROBLEM - Response time of WDQS on wdqs1002 is CRITICAL: CRITICAL: 10.00% of data above the critical threshold [300000.0]
[02:13:43] <icinga-wm_>	 RECOVERY - Response time of WDQS on wdqs1002 is OK: OK: Less than 5.00% above the threshold [120000.0]
[02:41:25] <icinga-wm_>	 PROBLEM - Response time of WDQS on wdqs1002 is CRITICAL: CRITICAL: 10.00% of data above the critical threshold [300000.0]
[02:46:46] <icinga-wm_>	 RECOVERY - Response time of WDQS on wdqs1002 is OK: OK: Less than 5.00% above the threshold [120000.0]
[03:08:16] <icinga-wm_>	 PROBLEM - Response time of WDQS on wdqs1002 is CRITICAL: CRITICAL: 10.00% of data above the critical threshold [300000.0]
[03:13:36] <icinga-wm_>	 RECOVERY - Response time of WDQS on wdqs1002 is OK: OK: Less than 5.00% above the threshold [120000.0]
[03:20:40] <holaalvarito>	 !ops hola alvaro molina
[03:43:37] <icinga-wm_>	 PROBLEM - Response time of WDQS on wdqs1002 is CRITICAL: CRITICAL: 10.00% of data above the critical threshold [300000.0]
[03:46:07] <icinga-wm_>	 RECOVERY - Response time of WDQS on wdqs1002 is OK: OK: Less than 5.00% above the threshold [120000.0]
[03:46:42] <JD|cloud>	 AlexZ: hhm
[03:47:03] <AlexZ>	 Does icinga-wm_ need to be making a racket in here?
[03:47:07] <AlexZ>	 :p
[03:47:17] <JD|cloud>	 I'd leave it
[03:47:26] <JD|cloud>	 WDQS is a Wikidata thing
[03:47:36] <AlexZ>	 It's going to keep triggering
[03:47:53] <AlexZ>	 so if you can live with the pings..
[04:11:06] <icinga-wm_>	 PROBLEM - Response time of WDQS on wdqs1002 is CRITICAL: CRITICAL: 10.00% of data above the critical threshold [300000.0]
[04:16:00] <icinga-wm_>	 RECOVERY - Response time of WDQS on wdqs1002 is OK: OK: Less than 5.00% above the threshold [120000.0]
[04:43:35] <icinga-wm_>	 PROBLEM - Response time of WDQS on wdqs1002 is CRITICAL: CRITICAL: 10.00% of data above the critical threshold [300000.0]
[04:48:29] <icinga-wm_>	 RECOVERY - Response time of WDQS on wdqs1002 is OK: OK: Less than 5.00% above the threshold [120000.0]
[05:16:01] <icinga-wm_>	 PROBLEM - Response time of WDQS on wdqs1002 is CRITICAL: CRITICAL: 10.00% of data above the critical threshold [300000.0]
[05:21:01] <icinga-wm_>	 RECOVERY - Response time of WDQS on wdqs1002 is OK: OK: Less than 5.00% above the threshold [120000.0]
[05:46:16] <icinga-wm_>	 PROBLEM - Response time of WDQS on wdqs1002 is CRITICAL: CRITICAL: 10.00% of data above the critical threshold [300000.0]
[05:51:08] <icinga-wm_>	 RECOVERY - Response time of WDQS on wdqs1002 is OK: OK: Less than 5.00% above the threshold [120000.0]
[06:16:24] <icinga-wm_>	 PROBLEM - Response time of WDQS on wdqs1002 is CRITICAL: CRITICAL: 10.00% of data above the critical threshold [300000.0]
[06:23:57] <icinga-wm_>	 RECOVERY - Response time of WDQS on wdqs1002 is OK: OK: Less than 5.00% above the threshold [120000.0]
[06:54:32] <icinga-wm_>	 PROBLEM - Response time of WDQS on wdqs1002 is CRITICAL: CRITICAL: 10.00% of data above the critical threshold [300000.0]
[06:59:42] <icinga-wm_>	 RECOVERY - Response time of WDQS on wdqs1002 is OK: OK: Less than 5.00% above the threshold [120000.0]
[07:30:23] <icinga-wm_>	 PROBLEM - Response time of WDQS on wdqs1002 is CRITICAL: CRITICAL: 10.00% of data above the critical threshold [300000.0]
[07:33:03] <icinga-wm_>	 RECOVERY - Response time of WDQS on wdqs1002 is OK: OK: Less than 5.00% above the threshold [120000.0]
[07:34:00] <AlexZ>	 :)
[07:53:57] <multichill>	 aude: Nice talk page @ https://www.wikidata.org/wiki/User_talk:Aude  [V-C84gpAAEUAARIU2PoAAABK] 2016-10-02 07:53:06: Fatal exception of type "Flow\Exception\InvalidInputException" 
[07:54:41] <sjoerddebruin>	 https://phabricator.wikimedia.org/T147122
[08:03:39] <doctaxon>	 multichill: what an editrate is BotMultichill set up?
[08:04:01] <doctaxon>	 I think, I have seen edits every second
[08:04:12] <doctaxon>	 in wikidata
[08:11:40] <multichill>	 Just the normal pywikibot. So it backs off when the replag goes up
[08:18:50] <multichill>	 doctaxon: It generally seems to be at around 10-15 edits per minute
[08:19:38] <doctaxon>	 multichill: I saw edits in recent changes every second yesterday evening
[08:19:50] <doctaxon>	 evening UTC
[08:23:06] <doctaxon>	 multichill: SuccuBot actually  edits twice in the second
[08:23:33] <doctaxon>	 how much is allowed with flooder flag
[08:26:29] <multichill>	 Dunno, never used it, bots have a botflag
[08:29:55] <doctaxon>	 multichill: yes, this was my question, is there an editrate maximum in Wikidata for bot users with bot flag?
[08:30:24] <doctaxon>	 you are admin there, I ask you for that
[08:32:44] <multichill>	 https://meta.wikimedia.org/wiki/Bot_policy#Edit_throttle_and_peak_hours & https://www.wikidata.org/wiki/Wikidata:Bots & https://www.mediawiki.org/wiki/API:Etiquette are the relevant pages.
[08:32:54] <multichill>	 No hard limit, just don't go too fast and respect replag
[08:33:20] <multichill>	 We've blocked bots in the past that were going too fast. Several edits per second
[08:34:28] <doctaxon>	 ah okay multichill, yes - my maxlag is set up to 5 - that's okay
[08:37:54] <sjoerddebruin>	 multichill: https://www.wikidata.org/w/index.php?title=Q2027954&type=revision&diff=383119869&oldid=205011862
[08:43:21] <doctaxon>	 sjoerddebruin: nameguzzler forgets the entity description
[08:43:58] <sjoerddebruin>	 ?
[08:46:28] <doctaxon>	 ya, you only inserted the entity label
[08:47:21] <sjoerddebruin>	 Yes, that's where the script was designed for.
[08:47:31] <multichill>	 Vreemd sjoerddebruin. Je zou eens kunnen kijken of het met https://nl.wikipedia.org/wiki/Categorie:Hoogleraar_aan_de_Katholieke_Universiteit_Leuven te maken heeft?
[08:47:43] <sjoerddebruin>	 multichill: ik ga zo kijken of er nog meer zijn
[08:47:52] <sjoerddebruin>	 Kan zijn dat je iets te diep ging ;)
[08:47:54] <doctaxon>	 then it's time to make the script better
[08:48:33] <sjoerddebruin>	 Well, feel free to improve it. Perfect descriptions are really hard.
[08:48:43] <doctaxon>	 yes it is
[08:48:53] <sjoerddebruin>	 And if I add occupation and country, a bot will add a Dutch description at last.
[08:51:51] <sjoerddebruin>	 multichill: 5 anderen, verkeerd gemarkeerd door Gerard in 2014.
[08:53:01] * doctaxon loves Wikidata every second more and more
[11:00:08] <sjoerddebruin>	 At least a homosexual Muppet got a source for his sexuality. https://www.wikidata.org/wiki/Q7356093
[11:24:34] <sjoerddebruin>	 Impressive. https://www.wikidata.org/w/index.php?title=Q26761745&type=revision&diff=372720138&oldid=372719940
[12:50:58] <nikki>	 phabricator is inconsistent in the order of the tags and subscribers field. it has tags first on the create task page but subscribers first on the search page >_<
[13:04:59] <Dereckson>	 nikki: fill a bug, ask for permission to fix the UI, and if greenlighted, submit a patch
[13:05:04] <Dereckson>	 secure.phabricator.com the tracker
[13:05:28] <Dereckson>	 but they don't like third party contributions as a general rule
[13:05:48] <Dereckson>	 I imagine here if you wish to fix the UI that's a low cost maintenance change, so would be acceptable
[13:06:15] <nikki>	 I don't particularly want to fix it myself, I have plenty of other things to do already :P
[13:07:15] <Dereckson>	 oh sorry, I didn't know why, I were on the strange assumption you already fixed it in your local Phabricator installation, and not seen it on Wikimedia tracker
[13:07:26] <sjoerddebruin>	 :P
[13:07:27] <Dereckson>	 that's better, they are pretty responsive for small fixes
[13:12:18] <chewieQC>	 Is there an equivalent guideline to wikipedia's in wikidata for semi-bot? I have a dataset that I want to merge with wikidata as a one time thing. Should I submit it as a bot proposition?
[13:13:44] <sjoerddebruin>	 chewieQC: I think you can request the flood flag for that. https://www.wikidata.org/wiki/Wikidata:Flooders
[13:15:36] <chewieQC>	 sjoerddebruin: It seems to be exactly what I needed, thanks!
[14:42:52] <doctaxon>	 Hi! What value have I to take to replace the value of property P2566 using API wbsetclaimvalue?
[14:43:45] <doctaxon>	 is here anybody with some API knowledge?
[14:44:01] <multichill>	 doctaxon: Use a framework that talks with the api?
[14:44:01] <doctaxon>	 yurik: maybe you?
[14:44:34] <doctaxon>	 multichill: I have the example: api.php?action=wbsetclaimvalue&claim=q42$D8404CDA-25E4-4334-AF13-A3290BCD9C0F&snaktype=value&value={"entity-type":"item","numeric-id":1}&token=foobar&baserevid=7201010
[14:44:50] <doctaxon>	 and there is a value to set
[14:45:05] <multichill>	 Back doctaxon, what do you try to do and why are you communicating with the api directly?
[14:45:31] <doctaxon>	 cause I am using a flooder account
[14:46:02] <doctaxon>	 let me explain:
[14:46:07] <multichill>	 please do
[14:49:55] <doctaxon>	 multichill: as example: entity Q408432, property P2566, its value is wrong and I want to change it using wbsetclaimvalue to the right value "100.006.474"
[14:50:57] <doctaxon>	 snaktype value property P2566 datavalue {value 100.006.474 type string} datatype external-id
[14:51:30] <multichill>	 Let's rephrase that, as example: entity Q408432, property P2566, its value is wrong and I want to change to the right value "100.006.474"
[14:52:02] <doctaxon>	 yes, it's right
[14:52:15] <multichill>	 In one of the frameworks like pywikibot or the java thingie that's just a couple lines of code
[14:52:36] <doctaxon>	 but I have the framework
[14:52:39] <multichill>	 And it takes care of everything. If you are going to communicate with the api directly you have to implement that all yourself
[14:52:47] <multichill>	 Which one?
[14:52:56] <doctaxon>	 tcl framework
[14:53:10] <multichill>	 Link?
[14:53:13] <doctaxon>	 I only have to know the json for the value
[14:53:33] <multichill>	 It's a string
[14:53:50] <doctaxon>	 "type":"string"
[14:54:14] <doctaxon>	 "type":"string","value":"100.006.474"
[14:54:34] <doctaxon>	 but this does not work
[14:55:14] <doctaxon>	 i have only this not matching example: https://www.wikidata.org/w/api.php?action=help&modules=wbsetclaimvalue
[14:55:50] <doctaxon>	 there is stated something like this: value={"entity-type":"item","numeric-id":1}
[14:56:08] <doctaxon>	 what is that?
[14:57:25] <multichill>	 That's item Q1
[14:57:28] <multichill>	 The universe
[14:57:41] <doctaxon>	 but what item do I need?
[14:58:11] <multichill>	 The data type is external-id so it's a string
[14:58:25] <doctaxon>	 and the json?
[14:58:54] <multichill>	 Just do some edits in your browser with debug console open
[14:58:55] <doctaxon>	 "entity-type":"external-d" ?
[14:59:02] <multichill>	 Than you'll see all the api requests and answers
[14:59:37] <doctaxon>	 my trials give the error: servedby mw1233 error {code invalid-snak info {Invalid snak. (Can only construct StringValue from strings)} messages {{name wikibase-api-invalid-snak parameters {} html {* {Invalid snak.}}}} * {See https://www.wikidata.org/w/api.php for API usage}}
[15:01:22] <doctaxon>	 multichill: can you give me the URL for such a replace, that will help me a lot
[15:04:09] <doctaxon>	 multichill: this doesn't work too: "entity-type":"external-id","value":"100.242.450"
[15:07:21] <doctaxon>	 multichill: can you give me the URL for such a replace, that will help me a lot
[15:18:31] <doctaxon>	 multichill: I got it, thank you for any help
[15:47:28] <multichill>	 good luck
[15:48:11] <multichill>	 sjoerddebruin: I run into quite a few items like https://www.wikidata.org/w/index.php?title=Q21552930&oldid=276376461 . Do you happen to be working on these already? 
[15:48:28] <multichill>	 Could do a sparql query now we have the number of statements in there :-)
[15:49:22] <sjoerddebruin>	 multichill: I'm working on UGent first, then I will focus on the Dutch Senate I think.
[15:49:47] <multichill>	 Ok. I just move around a bit. Did a huge RKDartists clean up this weekend
[15:50:39] <sjoerddebruin>	 It's so annoying that a lot of sites don't include simple stuff like genders.
[15:51:22] <sjoerddebruin>	 Parlement.com for example, 444 items without gender.
[16:39:04] <timmy>	 I have noticed that some metro stations have "metro station" in its name, for example https://www.wikidata.org/wiki/Q2331863
[16:39:59] <sjoerddebruin>	 timmy: yeah, that's because that was the title of the page on the English Wikipedia.
[16:40:08] <sjoerddebruin>	 It can be removed imo.
[16:40:46] <timmy>	 So, is it ok to remove all such occurencies that I find?
[16:41:22] <sjoerddebruin>	 Yeah, if it is noted in the description it is not needed in the label.
[16:42:10] <timmy>	 Thanks, I'll try.
[16:43:38] <DanielK_WMDE>	 though in some cases, "Station" may be part of the proper name
[16:50:10] <timmy>	 but how to find out if it is the case?
[16:52:34] <sjoerddebruin>	 Reading sources.
[18:21:10] <nikki>	 timmy: if things like that are not capitalised (for english, at least), it's usually just descriptive and not part of the name, if it is capitalised, I would recommend checking more carefully
[18:22:46] <nikki>	 sitelinks for other languages can be useful too, since enwiki tends to use a descriptive page name where others often treat it like any other disambiguation (you can see that in your example :))
[19:41:52] <alvaramolino>	 !ops hola alvaro molina