[00:03:55] Good evening. I've been trying to set up my first tool, but I couldn't set up the virtual environment. It threw me "Error 1". What's the best tutorial to follow on doing that? The pages I found up to now haven't been very useful. [00:04:49] Oh, talking about Toolforge, by the way. Trying to use Python. [00:06:39] !help [00:06:39] If you don't get a response in 15-30 minutes, please email the cloud@ mailing list -- https://wikitech.wikimedia.org/wiki/Help:Cloud_Services_communication [00:08:01] Polomo: I got started with https://wikitech.wikimedia.org/wiki/Help:Toolforge/My_first_Flask_OAuth_tool [00:08:18] though arguably it’s been somewhat superseded by https://wikitech.wikimedia.org/wiki/Help:Toolforge/Building_container_images/My_first_Buildpack_Python_tool for the past 1-2 years [00:08:41] (the approach demonstrated in the former should still work fine but build packs are the recommended way going forward) [00:10:01] The problem is that, when I try to run `pip` (as a couple of the tutorials instruct me to do), it won't let me. Could that be an issue on my end? [00:10:15] Also, thanks for replying :) [00:10:21] are you inside a `webservice shell`? (probably `webservice python3.11 shell` or some other version) [00:10:59] No. Am I supposed to? [00:11:34] yes, and if the tutorials are toolforge-specific then they should definitely include that step [00:13:17] you can see it e.g. in https://wikitech.wikimedia.org/wiki/Help:Toolforge/My_first_Flask_OAuth_tool#How_to_create_a_basic_Flask_WSGI_webservice [00:16:58] Oh, that one tutorial does mention it, and I'm following it and it seems to be working. [00:18:24] yay [00:21:08] (if you were previously following some non-Toolforge-specific tutorial then it’s a bit of a gamble how well it applies… the build pack system is part of trying to bring Toolforge closer to other platforms, IIUC ^^) [00:24:15] Hm, but now I'm getting stuck again when it tells me to make the requirements.txt file... [00:24:51] "No such file". My comand to create the file must not be going through [00:25:12] ```(venv) tools.portuguesemaintenancewt@shell-1733962677:~$ cat > $HOME/www/python/src/requirements.txt << EOF``` [00:29:16] Huh. Made it work by pressing random combinations of keys [00:29:25] Hopefully the streak holds [00:30:04] Well, thanks for the help — eternally grateful! I'll definitely come back if I have anything that can't be solved by pressing random keys~ [00:30:07] :D [00:33:31] :D [00:33:45] I’m about to go to bed but maybe someone else will still be around when you come back ^^ [04:54:05] Anyone from Toolforge team? I am creating new tool on toolsadmin. It say "Tool name is already in use or invalid." for "bunny" tool name but seem https://bunny.toolforge.org/ says Not found. Can someone check? Wether I can have this. Because our project name is bunny. I want https://bunny.toolforge.org/. [05:02:49] I check /data/project on toolforge as well. There is not tool or web service with this name. [05:28:38] Jayprakash12345: I think this is probably a variation of https://phabricator.wikimedia.org/T380384. [05:31:37] Hi bd808, Can you or any high privileged user can create and assign it to me? As bunny string name is not conflicted to any other tool or webservice. [05:32:05] https://phabricator.wikimedia.org/source/labs-striker/browse/master/striker/tools/utils.py$53 https://wikitech.wikimedia.org/w/api.php?action=query&format=json&list=users&formatversion=2&ususers=Bunny [05:34:08] :( so there is no workaround? [05:34:24] Jayprakash12345: it would be a very manual process to bypass Striker. I would suggest you find a name that works with the current restrictions instead. [05:44:32] bd808: It is strange. I am not able to have "bunny-editor" as well. There is not user as well with this name. [05:49:49] https://wikitech.wikimedia.org/w/api.php?action=query&format=json&list=users&formatversion=2&ususers=Bunny-editor is missing the ``"cancreate": true` flag. I wonder if that is `related to https://phabricator.wikimedia.org/T377074 [05:54:12] Surely folks have not been unable to create new tools since August? Right? I’m on a phone with just awake eyes right now. I can try to dig deeper later today. [06:03:11] bd808: Sure, take your time. [07:46:50] I’m not sure how to check… I tried `ls -lt --time=creation /data/project/ | less` but it looks like creation time isn’t tracked (idk if it’s the fault of NFS or the underlying fs) (re @bd808: Surely folks have not been unable to create new tools since August? Right? I’m on a phone with just awake eyes right now. I can ...) [07:48:29] ok https://toolhub.wikimedia.org/search?ordering=-created_date looks more promising, https://toolhub.wikimedia.org/tools/toolforge-portuguesemaintenancewt/history claims it was created just yesterday and `stat /data/project/portuguesemaintenancewt/replica.my.cnf` concurs [07:48:39] so I think tool creation in general still looks like it’s working, phew [07:51:51] I was able to create a tool just now so not completely broken [07:54:47] @lucaswerkmeister There is a timestamp on the tool’s object in the LDAP directory. I don’t think we easily expose it elsewhere. [13:30:59] Hi, I've noticed a few times in the last days pods failing to schedule due to node constraints. Just now `15 Insufficient memory`, `56 Insufficient cpu` for cluebotng. The limits on my deployment haven't changed since last year, but perhaps something else has changed (we use the 'un-supported' way rather than the wrapper, since we need a [13:30:59] multi-container pod), otherwise is there currently constrained resources? I couldn't find the grafana instance which has the k8s metrics in to check directly sorry. [16:38:57] bd808: Any luck to find why I am not able to have "bunny-editor" as tool? [16:53:05] Jayprakash12345: I am sorry, but I did not make time. I am at an offsite team meeting this week and the program was more important than understanding this bug. [16:58:58] bd808: No problem. [22:13:52] !log lucaswerkmeister@tools-bastion-13 tools.lexeme-forms deployed 5ffdfb2c55 (l10n updates: he, nl) [22:13:56] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.lexeme-forms/SAL