[03:48:56] I wanted to ask about a language label (used along with its lang code) being used on Wikidata which I believe is not accurate. Can someone here help with that? [05:17:53] PROBLEM - Query Service HTTP Port on wdqs1007 is CRITICAL: HTTP CRITICAL: HTTP/1.1 503 Service Unavailable - 298 bytes in 0.002 second response time https://wikitech.wikimedia.org/wiki/Wikidata_query_service [11:26:17] good day every1 [13:48:55] PROBLEM - Check systemd state on wdqs1007 is CRITICAL: CRITICAL - degraded: The system is operational but one or more units failed. https://wikitech.wikimedia.org/wiki/Monitoring/check_systemd_state [14:09:13] RECOVERY - Check systemd state on wdqs1007 is OK: OK - running: The system is fully operational https://wikitech.wikimedia.org/wiki/Monitoring/check_systemd_state [14:14:45] PROBLEM - Check systemd state on wdqs1007 is CRITICAL: CRITICAL - degraded: The system is operational but one or more units failed. https://wikitech.wikimedia.org/wiki/Monitoring/check_systemd_state [14:38:39] RECOVERY - Check systemd state on wdqs1007 is OK: OK - running: The system is fully operational https://wikitech.wikimedia.org/wiki/Monitoring/check_systemd_state [14:44:11] PROBLEM - Check systemd state on wdqs1007 is CRITICAL: CRITICAL - degraded: The system is operational but one or more units failed. https://wikitech.wikimedia.org/wiki/Monitoring/check_systemd_state [15:08:09] RECOVERY - Check systemd state on wdqs1007 is OK: OK - running: The system is fully operational https://wikitech.wikimedia.org/wiki/Monitoring/check_systemd_state [15:13:41] PROBLEM - Check systemd state on wdqs1007 is CRITICAL: CRITICAL - degraded: The system is operational but one or more units failed. https://wikitech.wikimedia.org/wiki/Monitoring/check_systemd_state [15:57:13] PROBLEM - WDQS high update lag on wdqs1007 is CRITICAL: 1.524e+05 ge 4.32e+04 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 [15:57:50] RECOVERY - Query Service HTTP Port on wdqs1007 is OK: HTTP OK: HTTP/1.1 200 OK - 448 bytes in 0.025 second response time https://wikitech.wikimedia.org/wiki/Wikidata_query_service [15:57:55] RECOVERY - Check systemd state on wdqs1007 is OK: OK - running: The system is fully operational https://wikitech.wikimedia.org/wiki/Monitoring/check_systemd_state [15:58:38] ACKNOWLEDGEMENT - WDQS high update lag on wdqs1007 is CRITICAL: 1.524e+05 ge 4.32e+04 Gehel catching up on lag after restart - The acknowledgement expires at: 2020-07-06 15:58:16. 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 [19:59:54] Grrr, VIAF is to hate again XD [20:00:53] what now? :D [20:02:24] Well, one of its participants reuploaded their data with a new/better format [20:03:06] but many of those values were not assigned to the original VIAF entry, but a new one was created [20:04:01] the already good cluster was arbitrarily split, like here: https://www.wikidata.org/wiki/Q16390 :)) [20:06:59] and this is not a single occurence, it happened a lot of times... [20:07:58] likely everywhere, where there were multiple RERO entries uploaded: http://viaf.org/viaf/search?query=local.personalNames%20all%20%22Mario%20Benedetti%22%20and%20local.sources%20any%20%22rero%22&sortKeys=holdingscount&recordSchema=BriefVIAF [20:11:32] :/ [20:17:35] meh i say [21:10:37] editing lexemes manually is so annoying [21:11:15] it's like the interface is trying to find as many ways to obstruct me as possible >_<