[09:27:36] (03PS1) 10Framawiki: Update privacy link to the new foundation site [labs/tools/cdnjs-index] - 10https://gerrit.wikimedia.org/r/452035 (https://phabricator.wikimedia.org/T201735) [11:30:54] (03CR) 10Zhuyifei1999: [V: 032 C: 032] "Is jenkins here?" [labs/tools/cdnjs-index] - 10https://gerrit.wikimedia.org/r/452035 (https://phabricator.wikimedia.org/T201735) (owner: 10Framawiki) [11:31:20] (03CR) 10Zhuyifei1999: [V: 032 C: 031] Update privacy link to the new foundation site [labs/tools/cdnjs-index] - 10https://gerrit.wikimedia.org/r/452035 (https://phabricator.wikimedia.org/T201735) (owner: 10Framawiki) [11:33:51] (03CR) 10Zhuyifei1999: [V: 032 C: 032] Update privacy link to the new foundation site [labs/tools/cdnjs-index] - 10https://gerrit.wikimedia.org/r/452035 (https://phabricator.wikimedia.org/T201735) (owner: 10Framawiki) [11:46:41] !log tools.cdnjs Updated git 942ff92..bdb9f72 and running ~/update-index.sh T201735 [11:46:46] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.cdnjs/SAL [11:46:46] T201735: Change href link of "Wikimedia Privacy Policy" in cdnjs and cdnjs-beta tools - https://phabricator.wikimedia.org/T201735 [11:58:56] hi zhuyifei1999_ ! thanks for the manual merge [11:59:03] :) [12:00:10] any thoughts on https://gerrit.wikimedia.org/r/#/c/451698/ and https://gerrit.wikimedia.org/r/#/c/428140/ ? [12:00:53] will take a look now [12:00:58] ok [12:01:20] I haven't tested the latter in a vagrant install yet [14:35:17] (03CR) 10Rosalieper: [C: 032] Updated the README.md and added license url to the tweet [labs/tools/Commons-twitter-bot] - 10https://gerrit.wikimedia.org/r/450390 (https://phabricator.wikimedia.org/T190163) (owner: 10Rosalieper) [14:36:34] (03CR) 10Rosalieper: [V: 032 C: 032] Updated the README.md and added license url to the tweet [labs/tools/Commons-twitter-bot] - 10https://gerrit.wikimedia.org/r/450390 (https://phabricator.wikimedia.org/T190163) (owner: 10Rosalieper) [14:37:18] (03CR) 10Rosalieper: [V: 032 C: 032] Edited the test scripts to suit to changes for the bot [labs/tools/Commons-twitter-bot] - 10https://gerrit.wikimedia.org/r/450475 (https://phabricator.wikimedia.org/T190163) (owner: 10Rosalieper) [14:38:23] (03Abandoned) 10Rosalieper: Implemented text-like emoji tweet reply [labs/tools/Commons-twitter-bot] - 10https://gerrit.wikimedia.org/r/450619 (https://phabricator.wikimedia.org/T190163) (owner: 10Rosalieper) [16:06:32] !help please I am trying to run a webservice for my bot on toolforge but that doesn't work [16:06:33] r054l13: 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 [16:07:21] I only get a message Starting webservice ... [16:07:52] then the promt shows. But when I check online if the bot is runing it is not [16:09:28] https://wikitech.wikimedia.org/wiki/Help:Toolforge/Web#node.js_web_services This is what I follow omiting step 3 as I could not set a listening port for a bot [16:09:44] is there something am doing wrog please [16:10:14] note the bot run well when I run 'npm start'. The tool is in nodejs [17:37:22] r054l13: is this in your home or a project? [17:37:41] Basically, where would I find it? Looking to find more info. [18:13:17] bstorm_: Please what do you mean by my home? [18:14:08] bstorm_: the project is on my home directory in www/js [18:14:13] the bot* [18:29:18] r054l13: Hey, are you there? [18:29:39] yes [18:29:54] Okay, before the meeting, let's try something out [18:30:11] okay, thank you [18:30:12] We will begin with the docs [18:30:27] https://wikitech.wikimedia.org/wiki/Help:Toolforge/Web#node.js_web_services [18:31:16] Okay [18:31:49] Let me update my upstream [18:36:19] one more thing [18:36:48] r054l13: Okay, what is it? [18:37:09] step 5 in the docs gives me kubectl command not found [18:38:41] hmm.... [18:49:47] I presume you have already 'become' the tool? [18:50:57] yes [18:53:27] what host are you on? [18:54:57] r054l13: [18:57:33] host? [18:57:44] yes [18:57:58] what host ware you on where you gave the become command etc [18:58:23] *were [18:58:55] r054l13: are you running a bot via the `webservice command`? [18:59:08] *`webservice` command [18:59:13] nm I think you are on tools-bastion-03 [18:59:30] the kubectl is in your path unless you have set it to something strange [18:59:35] zhuyifei1999_: That's what am trying to do but not working [18:59:37] try 'which kubectl' [18:59:52] ok [19:00:48] yeah [19:01:01] what's the name of the tool? [19:02:06] r054l13: ^ [19:02:18] wm-commons-emoji-bot [19:02:46] I'm going to shut up because there are enough people talking here, I was only weighing in on the issue of the kubectl command being apparently missing [19:03:11] apergos: I was in the k8 node shell when I ran the kubectl command and go command not found [19:03:27] I did not run it directly on the bastion [19:03:38] got* [19:04:01] heh yeah you don't run it from the node shell :-) [19:04:44] zhuyifei1999_: wm-commons-emoji-bot [19:04:46] oh yeah that ^ [19:04:53] yeah I saw [19:05:52] (I just checked your $PATH looks sane, but looks like you figured out you werein the wrong shell) [19:06:55] have you checked the stdout / stderr of the pod with `kubectl logs`? [19:10:40] I have a wild guess, that since the webservice code invokes `npm start` on the pod, your `"start": "`npm bin`/nf run bin/reply",` may not have the npm managed by your npm [19:10:50] *by your nvm [19:11:46] in which case you might have to specify the absolute path to nf [19:13:05] but can I ask, why are you using `webservice` command instead of grid for running bots? I'm aware people do this to get more updated versions of the runtimes (like node), but in your case nvm manages them anyways [19:13:46] r054l13: Can you create me a new tool and give me access [19:14:00] I want to start from the ground up while you're trying with the already existing tool [19:15:37] For some reason, I can't create tools anymore, but I've just made a request [19:16:44] (oh wait, you don't have nvm on, but why am I seeing all this in .bashrc?) [19:16:59] d3r1ck: on striker? [19:17:31] zhuyifei1999_: I don't understand [19:18:05] I mean, creating a tool via toolsadmin.wikimedia.org (a.k.a. striker)? [19:18:07] zhuyifei1999_: Maybe I'm missing your question [19:18:14] zhuyifei1999_: yeah [19:18:51] I don;t have access to the logs of that thing, but is there any error messages visible to you> [19:18:53] *? [19:18:56] d3r1ck: I Ijust did that [19:19:11] zhuyifei1999_: let me check [19:22:38] zhuyifei1999_: Timed out attempting to start webservice (15s) [19:22:53] I got that line from services.log [19:23:16] anything from `kubectl logs`? [19:23:56] I don't know where 'Timed out attempting to start webservice' is from though. never seen this message [19:27:23] meh, I checked it [19:27:31] zhuyifei1999_: (node:1) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version. [19:27:40] https://www.irccloud.com/pastebin/UFRXHQd4/ [19:27:43] yes [19:30:59] node version is v6.11.0, is that too old or okay? [19:31:23] too old [19:31:45] then I think you could go with nvm [19:31:56] zhuyifei1999_: The NPM version in the node shell is 1.4.21 [19:32:17] and I really think running bots on webservice is weird (hackish) [19:32:32] And node version is v6.11.0 [19:32:38] zhuyifei1999_: :) [19:33:11] zhuyifei1999_: I created a virtual env and installed recent versions in [19:33:21] and I work and run the bot from there [19:33:23] d3r1ck: yes. however I'm not very aware of the lifecycle of node and npm versions to know whether a version is too old for normal use or not [19:33:45] r054l13: you mean the environment from nvm? [19:34:03] or the python virtualenv? [19:34:13] no, the one from nodeenv [19:34:48] there's a nodeenv? /me googles [19:36:53] ok. how do you invoke your bot if you were outside the env? [19:37:35] (because k8s and grid don't magically go into the env) [19:38:26] hmm [19:39:07] out of the env the bot doesn't run [19:39:15] i get errors [19:39:50] well, then you could figure out how to make k8s or grid activate the env [19:40:30] `webservice start` will invoke `npm start` with the system-wide npm install [19:40:47] which will be outside the env [19:41:23] ok I get it [19:41:44] but how to get that into the env I'm unsure. maybe you could use some shell scripts for that [19:42:46] yeah! you ealier mentioned nvm [19:43:21] could that be an alternative? [19:43:56] I think they work in a similar way (or maybe I'm wrong, not a node guy here) [19:44:09] by they I mean nodeenv and nvm [19:44:34] I only nvm before, and locally not on toolforge [19:44:43] ok i get you [19:44:46] *only used [20:34:43] r054l13: I'm still around here, so anytime you need some help, you can poke