[01:46:37] Guest108: no, one tool can have many cronjobs using the same virtualenv, and you choose the python image with the version you want, see https://wikitech.wikimedia.org/wiki/Help:Toolforge/Kubernetes [01:50:41] you should create a different virtualenv for each python version though. [01:58:09] Hi i received an email stating puppet failed on my cloudvps a few days ago was this due to maint? [02:00:27] did you also get the email telling you to ignore it? [02:00:50] I don’t believe so, let me double check [09:03:27] Sorry, my browser collapsed, and now I don't see previous chat. So thank you for the earlier answers, and the new question was: do I have to reinstall the bot whenever a Python version gets depricated? [10:53:58] Guest108: most probably yes, you will want to recreate the whole virtualenv it's installed into also (as the way python installs/uses the packages and the versions installed will most probably be different). An exception where you could be able to get away is minor versions upgrades, but for any other (3.X -> 3.(X+1), 2 -> 3) I'd recommend rebuilding it always [14:10:38] Hello [14:14:50] yes? [14:53:43] dcaro, thank you. :-( [17:16:01] !log toolhub Update demo server to 5dbae1 [17:16:03] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Toolhub/SAL [17:27:35] Greetings. [17:32:07] @JeanFred is https://toolsadmin.wikimedia.org/tools/id/a something that you are still planning on using, or just an old namesquatting? [17:54:46] Greetings. [17:56:06] hello, do you need help with something? [17:56:17] I had a conversation with Rook re: the SPARQL kernel for PAWS. We have a similar requirement for a project called Lucyfer, with similar aims to PAWS. [17:56:53] We discussed us forking the original SPARQL kernel (while still trying to engage the original author(s)) because the project seems abandoned. [17:57:08] If you have any suggestions about this please let us know. [17:58:17] We're evaluating how to best fork SPARQL kernel and take care of the fork, while respecting the original authors, yet ensuring it remains available to PAWS/WikiMedia. [17:58:43] With that, I go to lurking and will keep an eye here for feedback. Everyone have a great week. [17:59:19] Yeah if yinz were going to fork the sparql-kernel code, I would probably point PAWS to pull from there rather than the current, seemingly abandon, version. So long as it is a git repo and maintains license...what license is it now? It should be accessible to PAWS, and anyone else who needs it. [17:59:39] BSD-3-Clause license [17:59:40] Rook: BSD-3, same as Lucyfer. [17:59:56] Rook: Simplifies things. [18:00:18] True [18:00:32] Were yinz planning on forking it into your repo and maintaining it there? [18:00:33] Rook: It's end of year so we're super busy, but we'll try to carve Lucyfer out of my GitHub repos into a separate project. [18:00:49] Rook: Who is yinz? [18:00:52] Seems like a reasonable thing to do first [18:01:07] https://en.wikipedia.org/wiki/Yinz [18:01:14] Sorry local words in international spaces :p [18:01:22] Hah!!! [18:01:49] second person plural that English largely lacks [18:03:00] Rook: Yeah - got it. And Pittsburgh: my company is based there (though I'm in the Bay Area). Close ties to CMU/Eric Nyberg. [18:04:30] Rook: And yes, we'll fork the SPARQL kernel code straight to Lucyfer, then perhaps ask you to apply your changes to that fork. Or we can fork yours directly. Not quite sure yet what's best. We'll know by Thu or so. [18:04:38] Rook: And whatever works for you, of course. [18:05:15] Oh I'm the other way around, from the bay area now stationed in pgh. I forgot who use to run support for Nyberg at CMU, it wasn't me. He's not the one who always wanted his UID to be 80 is he? [18:05:45] Rook: Heh - nah, he's a pretty mellow guy. [18:06:00] Rook: He's the one behind the IBM system that broke Jeopardy. [18:06:36] "SPARQL kernel code straight to Lucyfer" by which you mean you'll make an organization called "Lucyfer" and add a sparql-kernel fork repo in that org? [18:06:43] Rook: We're doing some cool ontological work now, will move to optimizations by mid 2023 using genetic algorithms. Fun stuff. [18:06:57] pr3d4t0r: Oh yeah that guy! Alas no I didn't work with him [18:07:14] Rook: Yes on Lucyfer - so that I don't import it to my account, then have to export it to Lucyfer again. [18:07:51] pr3d4t0r: Also you're more than welcome to do anything with my patch, I don't need credit or anything for it. If it makes it work excellent [18:08:26] Rook: Too late! You're already listed as a contributor/friend of the Lucyfer project (since we're using your code). [18:08:38] lol, perfectly fine as well :p [18:09:16] Rook: https://is.gd/W1Uq9y [ https://github.com/pr3d4t0r/lucyfer#contributors ] [18:09:34] heh, awesome. Glad to be of assistance [18:09:41] Rook: Thanks. [18:11:05] Rook: You saved us time and energy -- cookies are due! And thanks for educating me on yinz - love it. I'll use it next week, when I come for meetings. For now... lurking here, awaiting feedback. Please ping me if anything comes to mind. [18:11:37] because I'm selfish, to verify how I can tie this back into PAWS. Yinz are planning over the next few weeks/months (I mean to imply no hurry, I've pinned PAWS to an older version of notebook that will tide sparql over for months), to make an lucyfer org, with a sparql-kernel fork in it, and I can then point paws at that to build the sparql kernel? [18:13:17] Rook: Correct. That's the plan. [18:13:52] pr3d4t0r: Excellent! If you remember, could you ping me once that is in motion [18:14:42] Rook: From our end: I'm the CTO for a PNC subsidiary, which we'll spin off some time in 2023 as a separate entity. Lucyfer is slated to become a company-sponsored/funded project (namely, peeps who work here will contribute to it with a clear conscience). That will ensure that Lucyfer stays funded and has active developers for the foreseeable future. [18:15:27] Rook: The copyrights for everything stay with the Lucyfer contributors. It's just a way for us to ensure someone always has time and can pay attention to Lucyfer, so it doesn't go stale. [18:15:56] pr3d4t0r: That gives a lot more stability than a lot of the projects that get included in PAWS get, awesome [18:16:36] Rook: It's part of how I operate. I don't let anyone hire me unless they are willing to do open source stuff without weird restrictions. [18:17:15] pr3d4t0r: It's a good moral scruple to have. One that is, I would say, rather popular around here :) [18:17:19] Rook: https://is.gd/QlknNn [ https://ciurana.eu/fotki/upload/2018/10/17/20181017051213-e03cf693.jpg ] [18:17:36] Rook: That goes back to when I was the chief architect at Walmart.com. [18:17:57] awesome [18:18:20] Rook: I'm kind of selling you because I want to ensure you feel comfortable trusting your fork to the Lucyfer team :) [18:19:47] Rook: One thing we learned with another open source project we already sponsored is that it's easier to bring something open source into triple (the PNC subsidiary) instead of the othr way around, at least while we're part of PNC, because reasons. [18:20:23] pr3d4t0r: PNC is not small. I'm not surprised that open sourcing things is not a straight forward process [18:20:43] Rook: That's also why I waited until now to bring Lucyfer in. The other project has limited appeal, I used it to learn how the process works with the pointy heads and the lawyers. [18:21:31] pr3d4t0r: I haven't had time to play with Lucyfer yet. It is intended to be run locally, there isn't an out there service running for people to connect to? [18:21:43] Rook: Correct. [18:21:56] Rook: Lucyfer -> you bring it to your computer; sort of a zero-install IDE. [18:22:32] Rook: That way if you have tons of data, or you have MFA to access S3, or whatever -- you can control that from your local machine. Wipe it when done. [18:22:48] pr3d4t0r: Perfect. Makes sense for the use case [18:22:59] Rook: It also coexists without interferring with your local Git, your IDE, etc. [18:25:03] Rook: My use case: I code on MacVim over a shared drive to the machine running Lucyfer. Depending on what I'm doing, VS Code or PyCharm to work on the same Git-managed directory. So at any point I could have Lucyfer for notebooks and visual debugger, PyCharm for editing/debugging some Python thing, Vim for when PyCharm navigation annoys me, all against the same directory. [18:25:51] Rook: Lucyfer lets you issue something like git commit -a -m "blah" from inside a shell, or you're free to issue it from your IDE, or from a native terminal, and so on. It doesn't interfere at all with anything local. [18:26:18] pr3d4t0r: So drop in, do your analysis, then shut it down? [18:26:23] Rook: Yup. [18:26:27] pr3d4t0r: nice [18:26:43] Rook: There's even a built-in command do kill Lucyfer itself: ./lucy neuter [18:27:07] Rook: That deletes everything Lucyfer installs (e.g. .config, .iPython, whatever) and cleans after itself. [18:27:12] pr3d4t0r: sweet. Things that clean themselves up are very pleasing [18:27:25] Rook: :) [18:28:08] pr3d4t0r: one of the nicer parts of recent computing for me are the ease with which VM and Docker have made test/build/run environments that keep my system in a state that I left it [18:28:11] Rook: I will pick your brain about PAWS later. I made a proposal for an article/guest blog comparing PAWS and Lucyfer, the use cases, etc. That'll come later. [18:28:24] Rook: Agreed. [18:28:42] pr3d4t0r: That sounds like a good article. Please ask away when ready [18:28:51] Rook: My last startup was all dockerized. Huge advantage when I sold it - helped with valuation. [18:28:54] Rook: Will do., [18:29:09] Rook: Have an awesome day -- meetings demand attention -- meh. [18:29:20] Rook: Ping me if you need anything. [18:29:29] pr3d4t0r: Same to you. "enjoy" your meetings [19:40:33] !log paws Do not load index files automatically cd85e584824c983ac5eef6fe1a6010d69c4c8003 T296870 [19:40:34] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Paws/SAL [19:54:37] * chicocvenancio peeks at Lucyfer, nice [20:03:57] Hello, I'm having trouble SSHing into an instance in a new Cloud VPS project. I followed the steps in https://wikitech.wikimedia.org/wiki/Help:Accessing_Cloud_VPS_instances (including setting my my ~/.ssh/config and making sure my public key is in wikitech. When I try to SSH in, I get "Connection closed by UNKNOWN port 65535". Any tips? [20:05:11] I don't know if you're supposed to be able to ssh directly onto the bastion, but when I try that I get "Connection closed by 185.15.56.87 port 22" [20:05:52] kindrobot: in Horizon you can click on console output to see what it is currently doing. before SSH can work it needs to finish a puppet run. on console you can see if puppet is still running or not [20:06:00] afair [20:06:11] or basically just wait a few minutes and try again [20:07:03] if it's not a brandnew VM or it still doesnt work that's another story though [20:07:51] kindrobot: you should be able to ssh directly to a bastion but your ssh config might not be set up for it since it's an edge case. [20:08:18] The most common cause of this issue is not specifying @ when you try to connect. [20:09:11] 'connection closed' usually indicates that either the instance is still provisioning, doesn't exist, or you're not a member of the project that it's in [20:10:10] Thank you everyone for your assistance. I've just checked the log and confirmed the provisioning finished up through the test login. [20:10:41] kindrobot: what is the fqdn of the host you're trying to reach? [20:13:13] test.wikifunctions.eqiad1.wikimedia.cloud [20:14:09] The instance name is "test" and the project name is "wikifunctions". [20:14:46] I don't see any login attempts for your user (or for anyone else, if that matters) [20:15:46] That's interesting. I also can't log into the bastion with "ssh kindrobot@bastion.wmcloud.org" if that matters. [20:16:06] "Connection closed by 185.15.56.87 port 22" [20:16:10] well, that's probably the actual issue, since if you can't log in to the bastion there's no way for you to try to log in there [20:16:37] can you try with `ssh -v` and paste the output somewhere and link it here? [20:17:16] Looking in LDAP I think something went wrong when kindrobot was added to the wikifuncitons project. Specifically they are not listed as a member of the bastion project. [20:17:42] oh, just found the same thing from the auth logs [20:17:55] Le gasp! :o [20:18:48] oh, I think I found what's wrong [20:18:50] let's see [20:19:28] In case you still need it: https://pastebin.mozilla.org/V76XF6ha/raw [20:19:45] not at the moment, but thanks [20:19:57] kindrobot: try now? [20:20:36] Got in to both the bastion and my instance. Thank you very much. :) [20:20:49] !log wikifunctions added kindrobot to the 'user' role too [20:20:50] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Wikifunctions/SAL [20:21:17] not sure why, but when the project was created you were added only with the 'projectadmin' role, while the bastion access automation is based on the 'user' role [20:21:41] that seems buggy on both counts :) [20:22:02] teh roles bit is manual though I think [20:22:37] Interesting. Is that something I could have self-serviced, if I knew what I was looking for? [20:22:44] not really [20:23:48] In theory you could have granted yourself the user role via Horizon, but it is really a platform admin problem. [20:24:00] Should jforrester (the other projectadmin) also be added to user? Though I imagine he's probably in user in another project. [20:24:45] * taavi adds [20:25:02] Thank you again. :) [20:42:12] !log tools.lexeme-forms deployed 2cb7ac792f (l10n updates: pnb) [20:42:14] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.lexeme-forms/SAL [21:35:05] !log tools.lexeme-forms deployed 4d781fb933 (Hindko noun templates) [21:35:07] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.lexeme-forms/SAL [22:16:45] !log tools.borked-bot Set count/jobs.batch to 30 T323846 [22:16:46] balloons: Unknown project "tools.borked-bot" [22:16:46] T323846: Request increased quota for borkedbot Toolforge tool - https://phabricator.wikimedia.org/T323846 [22:16:53] !log tools.borkedbot Set count/jobs.batch to 30 T323846 [22:16:55] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.borkedbot/SAL [22:17:42] !log tools.mix-n-match Update cpu rangelimit to 3 T323502 [22:17:44] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.mix-n-match/SAL [22:17:45] T323502: Request increased quota for mix-n-match Toolforge tool - https://phabricator.wikimedia.org/T323502