[10:58:26] * arturo waves to joakino [10:58:53] * joakino waves back [11:04:59] FYI you all in the community, joakino is a developer advocate that joined the Technical Engagement group today, will be working closely with us in the WMCS team to help with stuff like Toolforge and other resources that technical contributors usually use [11:05:11] please correct me if I got the job title wrong :-) [11:05:41] yes sounds right! hi everyone! 👋 [11:06:32] cool :) hi! [11:11:20] cc andre__ [11:11:33] Oy [11:11:45] * andre__ waves to joakino [11:12:12] morning andre__! [11:12:24] hi lucas [13:21:59] Hi, Pywikibot has issues with e-mails using tool account: https://github.com/pypa/pypi-support/issues/297 [13:22:44] Is there someone who could check those e-mails? [13:24:53] or check why they haven't been deployed to tool maintainers? [14:07:12] Dvorapa: That could have been because of T248731. We think that is fixed now. [14:07:12] T248731: tools.wmflabs.org email isn't received (puppet failure at tools-mail-02) - https://phabricator.wikimedia.org/T248731 [14:08:30] bd808: I think not, because it happens for more than a year [14:08:54] and even today (13 PM UTC) [14:17:42] Dvorapa: could please you make a phabricator task linking to that report you have made upstream? That will make it easier for us to track and look into [14:20:57] ok [14:29:39] done [16:06:23] regarding https://wikitech.wikimedia.org/wiki/News/Toolforge.org - why use 307 instead of 301 (permanently moved) ? [16:16:39] DSquirrelGM: because browsers cache 301 responses which makes moving back in the short term to fix problems more difficult [16:17:30] and 307 instead of 302 because 307 clarified the behavior for POST commands [16:18:22] ok, just noticed that, the reason wasn't particularly obvious [16:27:56] !log admin [codfw1dev] enable puppet across the fleet clean vxlan changes (T248881) [16:27:59] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Admin/SAL [16:27:59] T248881: CloudVPS: research VXLAN implementation for neutron - https://phabricator.wikimedia.org/T248881 [17:07:52] ooh, I hadn’t seen that migration page, neat [17:08:07] *yet (and I’m aware the timeline for announcement is only in a week ^^) [17:23:43] Lucas_WMDE: will ping you next week to be early tester/adopter of the `webservice --canonical` thing [17:24:29] cool! [17:24:47] I already have a suggestion for the flask section, will add that once I’m not on working time anymore [17:29:06] !help is there any way to get phpmyadmin for toolforge databases? [17:29:07] Sorry, you are not authorized to perform this [17:29:20] !help [17:29:20] Examknow: If you don't get a response in 15-30 minutes, please create a phabricator task -- https://phabricator.wikimedia.org/maniphest/task/edit/form/1/?projects=wmcs-team [17:30:07] Examknow: installing phpmyadmin as a tool is explicitly prohibited on the in our terms of service, so no [17:30:32] I saw on wikitech that it used to be there on toolserver [17:30:39] has that been discontinued? [17:31:17] yes. many things that were normal on toolserver were not continued in the Toolforge project [17:31:27] ok [17:31:28] thx [17:31:37] including using Jira as a bug tracker and svn for version control [17:32:17] Examknow: you may find quarry.wmflabs.org to be useful [17:32:21] Examknow: what sort of things were you hoping to use phpmyadmin for? Maybe we can suggest alternatives [17:32:53] I basically just like using phpadmin better when I work with databases [17:33:03] rather than the command line [17:34:09] welcome joakino [17:36:10] * joakino waves [17:39:09] Examknow: you could run phpmyadin locally and connect it with the wiki replicas and/or ToolsDB via an ssh tunnel. Some info at https://wikitech.wikimedia.org/wiki/Help:Toolforge/Database#SSH_tunneling_for_local_testing_which_makes_use_of_Wiki_Replica_databases [17:40:48] phpmyadmin is not well hardened for being exposed on the public internet. It is also not well designed for using multiple database connection credentials. Both of these are problematic for ToolsDB and the Wiki Replicas [21:33:02] I will let you know when I see Dvorapa and I will deliver that message to them [21:33:02] @notify Dvorapa I can PM you the pypi activation link [21:34:47] I keep forgetting about that function ... [21:35:41] :) [21:36:27] there is also memoserv if the recipient is freenode-registered [21:37:00] usually I just send a message on a talk page or something if I know their wiki account [21:38:09] yeah that works too [21:38:40] actually. good point. I should leave a message on the ticket in case it takes a long time for him to come back to IRC [21:44:44] also the issue of - if there's a connection issue between when the message is sent and when they get to reading it ...