[07:16:04] Join [07:17:19] Enjoy [08:00:56] wtf. [08:01:07] "catalog is not a valid qualifier for KulturNav-id – the only valid qualifier is mapping relation type." [08:01:16] But it's listed on https://www.wikidata.org/wiki/Property:P1248 as a mandatory qualifier :D [08:01:31] The "potential issues" tool has potential issues :p [08:01:40] Suck my cock [08:01:48] Please? [08:02:16] * reosarevok puts on his robe and wizard hat [08:02:58] Guess not [08:45:34] reosarevok: there are two allowed qualifier constraints, I assume it's only using the last one [08:46:00] Yeah, I imagine that's the case, hence the tool having potential issues :D [08:46:07] clearly there needs to be a constraint for only allowing one allowed qualifier constraint, if it's going to insist on only having one :P [08:46:12] Any idea where to complain about it? Phabricator somewhere? [08:46:21] phabricator sounds best [08:47:58] ohh, maybe it does check both, but it's only the last one which fails [08:48:38] Huh? But the other is not mandatory, so why would it fail if not present :) [08:55:45] * reosarevok reports it anyway [08:57:28] whether they're mandatory or not is mostly related to how important it is to fix it, they show up either way [09:00:10] I mean. One is allowed *and* mandatory, the other is allowed but not required [09:00:29] Oh, you mean it checks both separately [09:01:00] So it checks the first, sees the second allowed one isn't there and does not complain, but then it checks the second and does a dumb [09:01:04] Yeah, probably [09:01:08] Needs fixing, in any case :p [09:01:44] It would make sense to have only one allowed qualifier constraint with n qualifiers, but I guess that'd break the "mandatory constraint" bit. Although that's already there with "mandatory qualifier" anyway, so not sure why it's needed [09:10:16] well, the allowed qualifiers is for saying that only the listed qualifiers are allowed, it's not supposed to have other qualifiers [09:11:33] so either there shouldn't be any other qualifiers than the two listed and they can both go in the same constraint, or there should only be one of the two qualifiers and the other constraint is wrong [09:15:35] having two separate ones where one is mandatory is contradictory, the "catalog" one is saying it must not have "mapping relation type" (or any others), then there's another saying it can have that and shouldn't have "catalog" (or any others) [09:18:04] (which is why I mentioned that it needs a constraint for the constraints - it should complain that there are two separate allowed qualifier constraints... but I don't know if we can do that) [09:44:42] I think what that *wants* to say is "catalog is mandatory and the other optional" [09:44:48] But it might very well be that it's wrongly entered [09:45:36] that sounds like https://www.wikidata.org/wiki/Q21510856 instead [10:03:51] Yeah, that's also used, so I suspect that might just be wrongly entered [10:04:05] In this case though, I'd expect the potential issues thing to instead say "the property has issues!" [11:34:02] PROBLEM - Check systemd state on wdqs1008 is CRITICAL: CRITICAL - degraded: The system is operational but one or more units failed. [11:34:05] PROBLEM - Check systemd state on wdqs1010 is CRITICAL: CRITICAL - degraded: The system is operational but one or more units failed. [11:34:09] PROBLEM - Check systemd state on wdqs2001 is CRITICAL: CRITICAL - degraded: The system is operational but one or more units failed. [11:34:51] PROBLEM - Check systemd state on wdqs2006 is CRITICAL: CRITICAL - degraded: The system is operational but one or more units failed. [11:34:55] PROBLEM - Check systemd state on wdqs1009 is CRITICAL: CRITICAL - degraded: The system is operational but one or more units failed. [11:35:01] PROBLEM - Check systemd state on wdqs1007 is CRITICAL: CRITICAL - degraded: The system is operational but one or more units failed. [11:35:57] PROBLEM - Check systemd state on wdqs2003 is CRITICAL: CRITICAL - degraded: The system is operational but one or more units failed. [11:35:59] PROBLEM - Check systemd state on wdqs2005 is CRITICAL: CRITICAL - degraded: The system is operational but one or more units failed. [11:36:07] PROBLEM - Check systemd state on wdqs2004 is CRITICAL: CRITICAL - degraded: The system is operational but one or more units failed. [11:36:15] PROBLEM - Check systemd state on wdqs1003 is CRITICAL: CRITICAL - degraded: The system is operational but one or more units failed. [11:36:19] PROBLEM - Check systemd state on wdqs2002 is CRITICAL: CRITICAL - degraded: The system is operational but one or more units failed. [11:37:13] RECOVERY - Check systemd state on wdqs1009 is OK: OK - running: The system is fully operational [11:37:35] RECOVERY - Check systemd state on wdqs2001 is OK: OK - running: The system is fully operational [11:38:16] RECOVERY - Check systemd state on wdqs2003 is OK: OK - running: The system is fully operational [11:38:16] RECOVERY - Check systemd state on wdqs2005 is OK: OK - running: The system is fully operational [11:38:19] RECOVERY - Check systemd state on wdqs2006 is OK: OK - running: The system is fully operational [11:38:25] RECOVERY - Check systemd state on wdqs2004 is OK: OK - running: The system is fully operational [11:38:27] RECOVERY - Check systemd state on wdqs1007 is OK: OK - running: The system is fully operational [11:38:33] RECOVERY - Check systemd state on wdqs1003 is OK: OK - running: The system is fully operational [11:38:37] RECOVERY - Check systemd state on wdqs1008 is OK: OK - running: The system is fully operational [11:38:39] RECOVERY - Check systemd state on wdqs2002 is OK: OK - running: The system is fully operational [11:38:41] RECOVERY - Check systemd state on wdqs1010 is OK: OK - running: The system is fully operational [11:41:37] PROBLEM - Check systemd state on wdqs1004 is CRITICAL: CRITICAL - degraded: The system is operational but one or more units failed. [11:42:59] PROBLEM - Check systemd state on wdqs1009 is CRITICAL: CRITICAL - degraded: The system is operational but one or more units failed. [11:44:05] PROBLEM - Check systemd state on wdqs2005 is CRITICAL: CRITICAL - degraded: The system is operational but one or more units failed. [11:44:07] PROBLEM - Check systemd state on wdqs2006 is CRITICAL: CRITICAL - degraded: The system is operational but one or more units failed. [11:44:13] PROBLEM - Check systemd state on wdqs1006 is CRITICAL: CRITICAL - degraded: The system is operational but one or more units failed. [11:44:15] PROBLEM - Check systemd state on wdqs2004 is CRITICAL: CRITICAL - degraded: The system is operational but one or more units failed. [11:44:17] PROBLEM - Check systemd state on wdqs1007 is CRITICAL: CRITICAL - degraded: The system is operational but one or more units failed. [11:44:21] PROBLEM - Check systemd state on wdqs1003 is CRITICAL: CRITICAL - degraded: The system is operational but one or more units failed. [11:44:27] PROBLEM - Check systemd state on wdqs1008 is CRITICAL: CRITICAL - degraded: The system is operational but one or more units failed. [11:44:31] PROBLEM - Check systemd state on wdqs1010 is CRITICAL: CRITICAL - degraded: The system is operational but one or more units failed. [11:44:35] PROBLEM - Check systemd state on wdqs2001 is CRITICAL: CRITICAL - degraded: The system is operational but one or more units failed. [11:45:15] PROBLEM - Check systemd state on wdqs2003 is CRITICAL: CRITICAL - degraded: The system is operational but one or more units failed. [11:45:35] PROBLEM - Check systemd state on wdqs1005 is CRITICAL: CRITICAL - degraded: The system is operational but one or more units failed. [11:46:37] RECOVERY - Check systemd state on wdqs2004 is OK: OK - running: The system is fully operational [11:47:55] RECOVERY - Check systemd state on wdqs1005 is OK: OK - running: The system is fully operational [11:48:05] RECOVERY - Check systemd state on wdqs2001 is OK: OK - running: The system is fully operational [11:49:09] PROBLEM - Check systemd state on wdqs2002 is CRITICAL: CRITICAL - degraded: The system is operational but one or more units failed. [11:52:31] RECOVERY - Check systemd state on wdqs1008 is OK: OK - running: The system is fully operational [11:53:21] RECOVERY - Check systemd state on wdqs2003 is OK: OK - running: The system is fully operational [11:54:33] RECOVERY - Check systemd state on wdqs2006 is OK: OK - running: The system is fully operational [11:54:53] RECOVERY - Check systemd state on wdqs1010 is OK: OK - running: The system is fully operational [11:55:43] RECOVERY - Check systemd state on wdqs1006 is OK: OK - running: The system is fully operational [11:57:01] RECOVERY - Check systemd state on wdqs1003 is OK: OK - running: The system is fully operational [12:04:45] RECOVERY - Check systemd state on wdqs2005 is OK: OK - running: The system is fully operational [12:04:45] RECOVERY - Check systemd state on wdqs1009 is OK: OK - running: The system is fully operational [12:04:51] RECOVERY - Check systemd state on wdqs1007 is OK: OK - running: The system is fully operational [12:05:07] RECOVERY - Check systemd state on wdqs2002 is OK: OK - running: The system is fully operational [12:05:41] RECOVERY - Check systemd state on wdqs1004 is OK: OK - running: The system is fully operational [21:31:32] We should totally move that bot [23:12:15] "GCI is still running for another 2½ weeks. We will need more tasks." --Andre Klapper [23:12:18] :D [23:17:00] abian: hehe [23:17:09] abian: I think I just fixed that label & descriptions being the same patch [23:18:16] That's what we though last time... and the previous one xD [23:19:51] *thought [23:19:57] What was the problem? [23:31:08] Indeed, fixed :D