[09:44:17] !log tools.stewardbots deployed 5fb61ab, restarted SULWatcher [09:44:20] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.stewardbots/SAL [09:48:31] !log tools.stewardbots deployed e86e8ef, restarted StewardBot [09:48:32] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.stewardbots/SAL [12:42:10] Hello everyone! I wonder how to update version of Node.js to 12 or above? [12:43:11] im tried nvm but looks like i can't install it to my tools [12:49:36] use `node12` as the webservice type? (assuming you’re using the kubernetes backend) [12:50:58] no, for a bot. [12:52:50] but I do use Kubernetes [12:53:33] I'm tried to install nvm via install Script, but looks like it's not working for me. [12:56:17] uh... [12:56:21] i guess [12:56:31] the question have solved [12:57:06] Thnaks for your help! lucaswerkmeister [12:59:16] ok ^^ [12:59:42] for a bot (based on toolforge-jobs, I’m guessing?) the image name would be a bit different but there should also be a node12 image available, yeah [12:59:54] (and hopefully node14 soonish too) [13:01:05] ya [13:06:01] do we already have a task for providing node14/16 images? [13:08:12] usually we try to only ship what's included in debian, but with node12 already falling off upstream support we might want to consider using nodesource packages or something similar [13:08:57] although node 16 is in debian testing, so I wonder if it'll be soon available in bullseye-bpo [13:10:58] there’s T306996 and its parent task for production (based on nodesource) [13:11:31] based on that, I assume nodesource should also be acceptable for Toolforge images, but it doesn’t look like there’s an existing task for that [13:14:05] maybe, https://phabricator.wikimedia.org/T306996#7891286 isn't exactly ideal for us [13:16:08] true, tool maintainers would have to stay on top of supported Node versions [13:25:20] although we already don't do a great job of getting rid of old versions on containers, so maybe not the best reason to use to block newer node versions [13:26:11] so if someone wants to make a patch we can definitely consider it [15:13:07] Hi there, sorry to bother but I need assistance when migrating from old grid engine to k8s [15:16:24] the tool is "yifeibot", but maintainer is no longer active; when I tried to do it myself, I noticed there exist too many entries in crontab, which makes me kind of afraid of moving them (as it said if you want to migrate, old grid engine must be shutdown) [16:08:20] !log tools.wd-image-positions deployed b2fea9010f (image scaling support, better width+height+srcset) [16:08:23] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.wd-image-positions/SAL [16:51:28] Hi, everyone. Is there a way to pass environment variables to a command that's executing in toolforge-jobs? [16:59:13] I am trying to move a script to the Kubernetes backend. I didn't write the original code, and I'm having a hard time [17:00:10] I have managed to resolve all the dependencies, but now I am hitting runtime errors, and it seems I need to inherit environment variables that are set on .profiel [18:15:01] Joutbis: you probably need some sort of wrapper script that sets the environment variables that you need and then launches your actual script [18:15:54] alternatively you can try to run the actual script via `sh -i -c command` to make it use an 'interactive' shell that will read .profile [18:16:52] koi: hey, what kind of assistance are you looking for? we don't have any more information what those crontab entries are for than what you do [18:20:02] it's a problem related to pip - I just perform a trial migrate of a job, and the guidance said a new venv need to be created, so I tried to dump packages installed in previous venv but it said something like pip is missing blah blah [18:20:43] I store the Oauth tokens and secrets in my .profile. I can copy them in the wrapper script, but how secure is that? [18:21:45] That's for a bot that makes edits in both wikipedia and commons. [18:30:24] Joutbis: you can use 'source ~/.profile' in the wrapper script to make it just read them from .profile, or remove the read permission from everyone and then copy them to the wrapper script [18:32:10] Good idea, thank you very much [19:08:31] !log tools.integraality Deploy d395b4c, 591c450, 6d09e5b [19:08:33] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.integraality/SAL [19:14:59] !log tools.integraality Install all requirements and restart webservice [19:15:01] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.integraality/SAL [19:29:04] !log tools.integraality Deploy f6dc34b [19:29:06] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.integraality/SAL [19:31:30] !log tools.integraality Uninstall removed requirements and restart webservice [19:31:31] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.integraality/SAL [20:32:35] !log tools.integraality Deploy 80f073e [20:32:38] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.integraality/SAL [21:30:37] !log tools.integraality Deploy 3a675b6 [21:30:39] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.integraality/SAL [23:50:53] !log tools.stewardbots Deploy d92b3c1, restart SULWatcher [23:50:56] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.stewardbots/SAL