[02:35:35] nikki: oh well, i hit the drawback that the target site hides the data behind some javascript crap [02:36:19] eww :( [02:36:21] which site? [02:41:02] Trove [03:03:06] i even tried to use requests-html to render page first, which *should* work, but meh [03:07:38] oh, looks i have to use their api. which means dealing with XML. hm. double meh. [03:10:00] otoh, this actually looks like very nice [03:47:48] crazy, i tried 3, in words three, xml parsers on the output, and none of them works, well then its RE time. [04:51:28] nikki: hmh, maybe you could help me with the date representation later, when accessing an item via pywikibot? i mean you're smart :D [09:22:06] PROBLEM - Blazegraph process -wdqs-categories- on wdqs1011 is CRITICAL: PROCS CRITICAL: 0 processes with UID = 499 (blazegraph), regex args ^java .* --port 9990 .* blazegraph-service-.*war https://wikitech.wikimedia.org/wiki/Wikidata_query_service/Runbook [09:22:16] RECOVERY - WDQS HTTP on wdqs1011 is OK: HTTP OK: HTTP/1.1 200 OK - 17017 bytes in 0.006 second response time https://wikitech.wikimedia.org/wiki/Wikidata_query_service/Runbook [09:22:24] RECOVERY - WDQS SPARQL on wdqs1011 is OK: HTTP OK: HTTP/1.1 200 OK - 17017 bytes in 0.001 second response time https://wikitech.wikimedia.org/wiki/Wikidata_query_service/Runbook [09:22:40] PROBLEM - Blazegraph Port for wdqs-categories on wdqs1011 is CRITICAL: connect to address 127.0.0.1 and port 9990: Connection refused https://wikitech.wikimedia.org/wiki/Wikidata_query_service/Runbook [09:22:46] PROBLEM - Blazegraph Port for wdqs-blazegraph on wdqs1011 is CRITICAL: connect to address 127.0.0.1 and port 9999: Connection refused https://wikitech.wikimedia.org/wiki/Wikidata_query_service/Runbook [09:22:58] PROBLEM - Blazegraph process -wdqs-blazegraph- on wdqs1011 is CRITICAL: PROCS CRITICAL: 0 processes with UID = 499 (blazegraph), regex args ^java .* --port 9999 .* blazegraph-service-.*war https://wikitech.wikimedia.org/wiki/Wikidata_query_service/Runbook [09:23:06] RECOVERY - SSH on wdqs1011 is OK: SSH OK - OpenSSH_7.9p1 Debian-10+deb10u2 (protocol 2.0) https://wikitech.wikimedia.org/wiki/SSH/monitoring [09:23:06] PROBLEM - Query Service HTTP Port on wdqs1011 is CRITICAL: HTTP CRITICAL: HTTP/1.1 502 Bad Gateway - 380 bytes in 0.001 second response time https://wikitech.wikimedia.org/wiki/Wikidata_query_service [09:23:32] PROBLEM - Check systemd state on wdqs1011 is CRITICAL: CRITICAL - degraded: The system is operational but one or more units failed. https://wikitech.wikimedia.org/wiki/Monitoring/check_systemd_state [09:23:42] RECOVERY - Blazegraph process -wdqs-categories- on wdqs1011 is OK: PROCS OK: 1 process with UID = 499 (blazegraph), regex args ^java .* --port 9990 .* blazegraph-service-.*war https://wikitech.wikimedia.org/wiki/Wikidata_query_service/Runbook [09:23:44] PROBLEM - WDQS high update lag on wdqs1011 is CRITICAL: 1.787e+05 ge 3600 https://wikitech.wikimedia.org/wiki/Wikidata_query_service/Runbook%23Update_lag https://grafana.wikimedia.org/dashboard/db/wikidata-query-service?orgId=1&panelId=8&fullscreen [09:24:18] RECOVERY - Blazegraph Port for wdqs-categories on wdqs1011 is OK: TCP OK - 0.000 second response time on 127.0.0.1 port 9990 https://wikitech.wikimedia.org/wiki/Wikidata_query_service/Runbook [09:24:24] RECOVERY - Blazegraph Port for wdqs-blazegraph on wdqs1011 is OK: TCP OK - 0.000 second response time on 127.0.0.1 port 9999 https://wikitech.wikimedia.org/wiki/Wikidata_query_service/Runbook [09:24:36] RECOVERY - Blazegraph process -wdqs-blazegraph- on wdqs1011 is OK: PROCS OK: 1 process with UID = 499 (blazegraph), regex args ^java .* --port 9999 .* blazegraph-service-.*war https://wikitech.wikimedia.org/wiki/Wikidata_query_service/Runbook [09:24:46] RECOVERY - Query Service HTTP Port on wdqs1011 is OK: HTTP OK: HTTP/1.1 200 OK - 448 bytes in 0.021 second response time https://wikitech.wikimedia.org/wiki/Wikidata_query_service [09:41:26] RECOVERY - Check systemd state on wdqs1011 is OK: OK - running: The system is fully operational https://wikitech.wikimedia.org/wiki/Monitoring/check_systemd_state [10:32:33] Hello. Newish to wikidata. Just wondering about the etiquette around merging items. If I spot duplicate items (https://www.wikidata.org/wiki/Q83560023 and https://www.wikidata.org/wiki/Q83544972), should I just merge them or should I start a discussion on the duplicate? [11:28:47] bytesnz: if you're sure they're exactly the same thing, it's fine to go ahead and merge them (bearing in mind that wikidata often makes distinctions that places like wikipedia don't) [11:28:58] in this case I'd agree with merging, I can't see how they would be different [11:30:46] and if you do ever want to start a discussion about whether to merge, it's best to do it in one of the more general discussion places (e.g. project chat on wiki, here or the telegram group) since not many people see discussions on talk pages [12:56:35] nikki: do you have information about the json representation of items? [12:57:26] i mean there is this: https://www.mediawiki.org/wiki/Wikibase/DataModel/JSON [12:58:39] especially time. [12:59:39] what sort of information? I usually just look at the json for an item that has statements like ones I want to add [13:00:14] looks like i have to puzzle the "time" together by myself from year, month and day? [13:00:52] (I also have a user script for adding a section to the sidebar with links for different formats so I can get to it easily) [13:00:54] yeah probably [13:05:48] :< [13:15:00] oh well, i have to. the only part that is missing now is the writing XD (: [13:20:07] if you need help, just say :D I'm not that great at python but if I can't help surely someone else can [13:21:14] nikki: how can i create a query for test.wikidata. org? [13:22:11] if you mean sparql query, I don't think it's possible [13:23:14] how can i find suitable items on test then for me to edit? :D [13:23:36] probably have to hardcode some ids :/ [13:27:43] meh :D [13:32:34] <[d]_> i mean there is this: https://www.mediawiki.org/wiki/Wikibase/DataModel/JSON [13:32:35] <[d]_> [edit]: [13:32:38] <[d]_> especially time. [13:32:40] <[d]_> [edit]: [13:34:16] :-) [14:32:35] <[d]_> looks like i have to puzzle the "time" together by myself from year, month and day? [14:32:37] <[d]_> [edit]: [16:03:50] SothoTalker, just so you know I don't think your edits are coming through [16:04:03] The bridge just says "[edit]:" with nothing after it [16:04:17] thats not me (: [16:04:55] i let my subconscious work on a way how to best achieve it. [16:06:02] Oh I just realized you're here as well [16:06:15] Oh, does the bridge not show the person talking? [16:20:42] perryprog: i dont know what the bridge is doing o.o [16:21:03] Eh, no one does. Insert Discord is bad rant here. [16:32:44] <[d]> what sort of information? I usually just look at the json for an item that has statements like ones I want to add [16:32:44] <[d]> [edit]: [16:46:54] I guess I'll stop talking if a bot is going to start repeating random things I say [16:53:10] just wait for the day when bots take over the world :p [16:59:39] Oh wait, I didn't even realize that [d] is repeating the messages? [16:59:49] I'm even more confused now [17:02:14] bridge bot getting confused [17:02:37] and if you thought human errors are bad, well bots will be worse :D [18:05:38] [mattermost] Not all bridges are created equally 😆 [18:07:27] Mattermost I can get behind. [18:28:18] :) [19:15:03] RECOVERY - WDQS high update lag on wdqs1011 is OK: (C)3600 ge (W)1200 ge 588.5 https://wikitech.wikimedia.org/wiki/Wikidata_query_service/Runbook%23Update_lag https://grafana.wikimedia.org/dashboard/db/wikidata-query-service?orgId=1&panelId=8&fullscreen [20:16:15] I'm trying to use https://sourcemd.toolforge.org [20:16:27] but I'm getting a CORS error when it tries to connect to quickstatements [20:16:30] is there anything to do here?