[01:35:08] I'm getting a "no connected implementations" error at Z28323 even though the referred Z28312 does have a working connected implementation. [03:45:18] I thought Z23680 was working before, but the test currently shows "failed" with no errors. [05:30:44] this issue seems to have been around for a while T404186 (re @u99of9: I'm getting a "no connected implementations" error at Z28323 even though the referred Z28312 does have a working connected imple...) [05:58:21] Can someone try to put Z28327 in as the function for Z28332? For me it's not showing up in the function search. [07:36:19] Done ✅ You left it expecting the function for a function-call, but it needed to be just a reference to the function. (re @u99of9: Can someone try to put Z28327 in as the function for Z28332? For me it's not showing up in the function search.) [07:37:39] Oh, duh, I must've been in too much of a rush. Thanks (re @Al: Done ✅ You left it expecting the function for a function-call, but it needed to be just a reference to the function.) [10:23:01] It has. We’ve had it lurking in *T402079* for a month, but it’s been discussed here before. I’ll connect the tasks, but let’s keep the new one for Z503s specifically? (re @u99of9: this issue seems to have been around for a while T404186) [10:33:00] T404797 (https://phabricator.wikimedia.org/T404797) – All (?) Python implementations currently time out `[open] [10:33:01] The `outage continues. Is it time to escalate? @staff [10:41:16] T404797 (https://phabricator.wikimedia.org/T404797) – All (?) Python implementations currently time out `[open] [10:41:16] The o`utage continues. Is it time to escalate? @Sannita [10:41:18] (with apologies) [12:36:08] will report immediately, sorry but I'm at an in-person meeting, and that slipped out of my sight (re @Al: T404797 – All (?) Python implementations currently time out [open] [12:36:09] The outage continues. Is it time to escalate? @Sannita [12:36:10] (with...) [12:37:38] done, I'll try to keep an eye open on this and report back as soon as I can [12:41:08] No worries. We should have an agreed escalation mechanism. In this case, I’ve taken the view that the immediate impact is not too disruptive. I’ve updated [[Wikifunctions:Status]], to be on the safe side. 🙏 (re @Sannita: will report immediately, sorry but I'm at an in-person meeting, and that slipped out of my sight) [12:43:48] let's discuss it, maybe at the next Corner? (re @Al: No worries. We should have an agreed escalation mechanism. In this case, I’ve taken the view that the immediate impact is not to...) [12:43:54] or we can just do it on wiki [12:57:50] Either or both 😎 I’ll start a topic on [[Wikifunctions:Project chat]] and/or [[Wikifunctions talk:Report a technical problem]], shall I? (re @Sannita: or we can just do it on wiki) [13:00:32] The fastest option at [[Wikifunctions:Report_a_technical_problem]] is this Telegram channel. Personally I still think it's the best for quick broad visibility and am sad that most staff have disengaged. It's good to have you bridging efficiently Luca. I understand that it got too sweary for a while, but thankfully that seems to have passed. (re @Al: No worries. We [13:00:32] should have an [13:00:33] agreed escalation mechanism. In this case, I’ve taken the view that the immediate impact is not to...) [13:07:37] Yes, I would expect reporting it here would be the first step, if only to avoid having more than one of us filing a ticket for the same issue! 😏 (re @u99of9: The fastest option at [[Wikifunctions:Report_a_technical_problem]] is this Telegram channel. Personally I still think it's the b...) [13:31:22] I'm pretty sure Z28327 was passing a few hours ago, but now there's a timeout!? [13:40:32] Object equality still prefers Python 🤷‍♂️ (re @u99of9: I'm pretty sure Z28327 was passing a few hours ago, but now there's a timeout!?) [14:24:52] Python evaluations now succeed. Thanks! 🙏 (re @Sannita: will report immediately, sorry but I'm at an in-person meeting, and that slipped out of my sight) [14:34:14] you should hear me IRL 😂 (re @u99of9: The fastest option at [[Wikifunctions:Report_a_technical_problem]] is this Telegram channel. Personally I still think it's the b...) [14:34:20] fantastic! (re @Al: Python evaluations now succeed. Thanks! 🙏) [14:37:07] saw that you did it, thank you for this (re @Al: Either or both 😎 I’ll start a topic on [[Wikifunctions:Project chat]] and/or [[Wikifunctions talk:Report a technical problem]], ...) [14:37:23] I'll chime in when I have time, which is not going to be today, sadly [15:00:49] On https://phabricator.wikimedia.org/T404797: as far as I can tell, we had a bad Python evaluator image, although it's strange that this only cropped up now. In any case, we've deployed and things seem to be working. [15:15:00] Thanks. I thought it was odd that test cases apparently carried on evaluating correctly in the background 🤔 (re @wmtelegram_bot: On https://phabricator.wikimedia.org/T404797: as far as I can tell, we had a bad Python evaluator image, although it's s...) [21:37:22] This has gone away. I wonder if it's also somehow connected to the python issue? (re @u99of9: I'm getting a "no connected implementations" error at Z28323 even though the referred Z28312 does have a working connected imple...) [22:10:26] Hard to say. We redeployed all the services at once, so it could be related or it could be a symptom of something else. In any case, if any of these things recurs, we should take a closer look. For now, I'm hoping these were just transient issues. (re @u99of9: This has gone away. I wonder if it's also somehow connected to the python issue?)