[00:36:30] PROBLEM - wikidata.org dispatch lag is higher than 300s on www.wikidata.org is CRITICAL: HTTP CRITICAL: HTTP/1.1 200 OK - pattern not found - 1968 bytes in 0.062 second response time [00:51:50] RECOVERY - wikidata.org dispatch lag is higher than 300s on www.wikidata.org is OK: HTTP OK: HTTP/1.1 200 OK - 1971 bytes in 0.079 second response time [03:32:30] PROBLEM - wikidata.org dispatch lag is higher than 300s on www.wikidata.org is CRITICAL: HTTP CRITICAL: HTTP/1.1 200 OK - pattern not found - 1981 bytes in 0.077 second response time [03:47:49] RECOVERY - wikidata.org dispatch lag is higher than 300s on www.wikidata.org is OK: HTTP OK: HTTP/1.1 200 OK - 1969 bytes in 0.073 second response time [05:26:50] PROBLEM - wikidata.org dispatch lag is higher than 300s on www.wikidata.org is CRITICAL: HTTP CRITICAL: HTTP/1.1 200 OK - pattern not found - 1969 bytes in 0.066 second response time [08:34:40] PROBLEM - High lag on wdqs1003 is CRITICAL: 3623 ge 3600 https://grafana.wikimedia.org/dashboard/db/wikidata-query-service?orgId=1&panelId=8&fullscreen [10:46:12] sjoerddebruin : the property proposal request have been created for one of them here https://www.wikidata.org/wiki/Wikidata:Property_proposal/StadiumDB_identifier [10:47:18] Migrant: your proposal looks good to me [10:49:45] thanks, pintoch [11:31:30] created another stadium identifier here https://www.wikidata.org/wiki/Wikidata:Property_proposal/World_Stadium_Database_identifier [11:37:34] Thanks for your support pintoch [12:20:06] Auregann_WMDE, Lydia_WMDE: Around? [13:25:00] RECOVERY - wikidata.org dispatch lag is higher than 300s on www.wikidata.org is OK: HTTP OK: HTTP/1.1 200 OK - 1955 bytes in 0.084 second response time [13:58:50] PROBLEM - wikidata.org dispatch lag is higher than 300s on www.wikidata.org is CRITICAL: HTTP CRITICAL: HTTP/1.1 200 OK - pattern not found - 1966 bytes in 0.112 second response time [14:34:39] RECOVERY - wikidata.org dispatch lag is higher than 300s on www.wikidata.org is OK: HTTP OK: HTTP/1.1 200 OK - 1960 bytes in 0.069 second response time [14:41:50] PROBLEM - wikidata.org dispatch lag is higher than 300s on www.wikidata.org is CRITICAL: HTTP CRITICAL: HTTP/1.1 200 OK - pattern not found - 1964 bytes in 0.117 second response time [15:02:19] RECOVERY - wikidata.org dispatch lag is higher than 300s on www.wikidata.org is OK: HTTP OK: HTTP/1.1 200 OK - 1957 bytes in 0.067 second response time [16:31:05] Hello. Any devs here? [16:31:55] I've tried to test Lexeme namespace and almost instantely found a bug: https://imgur.com/a/ZPiVDGG [16:32:24] There should be "���������� ����" instead of "?�?????�????N??????? N??�N???" [16:59:45] Vort: it's a known problem, I think it's also fixed but the fix hasn't been released yet [17:01:13] Hi [17:01:45] I want to use quickstatements to create entities. can I try on a sandbox first? [17:02:36] if you're only adding statements, you can use the sandbox item, but there's no way I know of to test creating new items [17:02:59] I usually just create one item first, then check for (and fix) any mistakes [17:03:40] Lydia_WMDE: has the fix for the encoding problem been released? [17:03:47] (for lexemes) [17:04:00] maybe someone help can help me check my statements before I add them? [17:16:50] PROBLEM - wikidata.org dispatch lag is higher than 300s on www.wikidata.org is CRITICAL: HTTP CRITICAL: HTTP/1.1 200 OK - pattern not found - 1971 bytes in 0.072 second response time [17:52:30] RECOVERY - wikidata.org dispatch lag is higher than 300s on www.wikidata.org is OK: HTTP OK: HTTP/1.1 200 OK - 1967 bytes in 0.062 second response time [17:59:50] PROBLEM - wikidata.org dispatch lag is higher than 300s on www.wikidata.org is CRITICAL: HTTP CRITICAL: HTTP/1.1 200 OK - pattern not found - 1973 bytes in 0.093 second response time [18:08:18] . [18:40:40] RECOVERY - wikidata.org dispatch lag is higher than 300s on www.wikidata.org is OK: HTTP OK: HTTP/1.1 200 OK - 1959 bytes in 0.091 second response time [18:42:10] https://www.wikidata.org/wiki/Special:Contributions/Elizabeth_Pullen [18:43:22] This user has no edits with her own account but she's running wrong edits with QuickStatements [18:47:23] Don't you think QuickStatements should be just for autoconfirmed users? [19:00:20] PROBLEM - wikidata.org dispatch lag is higher than 300s on www.wikidata.org is CRITICAL: HTTP CRITICAL: HTTP/1.1 200 OK - pattern not found - 1964 bytes in 0.083 second response time [19:35:21] abian: I've seen that suggested before, not sure why it wasn't changed [19:35:34] also what a surprise, they're trying to mass-add descriptions [19:36:10] Yes, curious :) [19:36:18] I really really wish we automatic descriptions so people didn't need to do that [19:36:33] We talked about semi-automatic editing again at the Hackathon, it's now the task to find the arbitrary amount of when approval is needed for a (semi)-automatic tasks. [19:36:33] +100 <3 [19:36:40] When is a task "large"? [19:37:24] Hard question :/ [19:46:31] What kind of approval? [19:46:35] Same as for a bot? [19:46:57] nikki: you accidentally a word [19:49:04] Yeah, because you are basically a bot for that time [19:49:29] reosarevok: I'll accidentally my verbs whenever I feel like it! :P [19:49:44] And so you should! [19:49:55] That's an independent sentence that doesn't need no verb! [19:50:16] sjoerddebruin: I suspect that'd make people even less willing to fix crap, although I understand the reasoning [19:50:33] Bot approval takes forever [19:52:43] Still, I don't like that people can import 300k people without useful statements in one day. [19:53:01] An automatic approval could be useful too [19:53:11] Just like the autoconfirmed flag works (?) [19:54:00] ... in case we worry about the possible new boring processes [19:54:02] Agreed [19:54:08] re: 300k people [19:54:44] Arguably, automatically creating a reasonably large number of items is worse than adding statements [19:54:54] Or is it easy to revert item creation? [19:55:03] If not, I'd have lower limits for those [19:57:09] I think admins can use https://www.wikidata.org/wiki/Special:Nuke, but obviously only admins [20:01:09] PROBLEM - High lag on wdqs1003 is CRITICAL: 3609 ge 3600 https://grafana.wikimedia.org/dashboard/db/wikidata-query-service?orgId=1&panelId=8&fullscreen [20:20:36] once a Q is created it can only marked invalid, no? ^^ [20:20:59] we can delete them [20:21:17] the id can't be reused though [20:21:34] luckily numbers are infinite [20:54:13] int32 numbers are not though [20:57:29] RECOVERY - wikidata.org dispatch lag is higher than 300s on www.wikidata.org is OK: HTTP OK: HTTP/1.1 200 OK - 1952 bytes in 0.077 second response time [21:14:50] PROBLEM - wikidata.org dispatch lag is higher than 300s on www.wikidata.org is CRITICAL: HTTP CRITICAL: HTTP/1.1 200 OK - pattern not found - 1967 bytes in 0.070 second response time [21:20:00] RECOVERY - wikidata.org dispatch lag is higher than 300s on www.wikidata.org is OK: HTTP OK: HTTP/1.1 200 OK - 1953 bytes in 0.101 second response time [21:27:19] PROBLEM - wikidata.org dispatch lag is higher than 300s on www.wikidata.org is CRITICAL: HTTP CRITICAL: HTTP/1.1 200 OK - pattern not found - 1970 bytes in 0.073 second response time [21:52:40] RECOVERY - wikidata.org dispatch lag is higher than 300s on www.wikidata.org is OK: HTTP OK: HTTP/1.1 200 OK - 1949 bytes in 0.081 second response time