[00:07:38] !log tools rebooting tools-puppetdb-1 in case that straightens out the puppet failures [00:07:42] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools/SAL [00:13:17] !log puppet-diffs rebooting pcc-worker1002 in case it helps with T347358 [00:44:51] 103.127.3.38 [00:45:07] this ip was blocked without any reason [11:46:36] please consider approving https://toolsadmin.wikimedia.org/tools/membership/status/1553 [11:47:19] it's the school holidays and she's bored and she's asking me what DBAs do [11:54:25] TimStarling: hi, sure :-) can you please have them create a phabricator account and link it to https://toolsadmin.wikimedia.org/profile/settings/accounts/ [13:47:42] !log tools.stashbot stashbot.sh restart [13:47:46] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.stashbot/SAL [13:48:15] thx [13:50:04] TimStarling: oh that's adorable :D [16:07:44] Excellent, we're recruiting a new generation [16:08:48] Somewhat basic question: I notice that the dumps site and its mirrors often store more than just the most recent dump, often going back 2-5 dumps, but not containing every dump in history (which is understandable). I would understand hosting only the most recent, and I would understand hosting all of them, but what's the point of hosting the most recent 2-5? [16:09:41] Like why would someone want the second- or third-most recent dump, as opposed to the most recent, or a historical dump from several years ago [16:12:38] Hi. ORES is broken, doesn't return a callback and Petscan hard-depends on it. Can someone restart or seomthing? [16:15:40] T347344 ? [16:16:24] Seems like it, thanks [16:54:13] Error deleting file: cannot create index mwstore://local-multiwrite/local-deleted/1/2/0 [16:54:14] [16:54:15] Is this a Mediawiki bug? [16:56:20] Yetkin: How is this related to Toolforge/CS? Please provide context [17:08:52] this is about an error on the production server (trwiki) [17:09:25] There's been some file/image serving issues [17:09:39] Though, this would be different... But as andre says, probably off topic for this channel [17:10:08] Yetkin: Then this should be in #wikimedia-tech I'd say. This is the colud channel [17:11:35] I am on Telegram (re @wmtelegram_bot: Yetkin: Then this should be in #wikimedia-tech I'd say. This is the colud channel) [17:12:13] and this is the wrong Telegram channel [18:24:57] !log tools.integraality Deploy 3caa9ed, a8029ed, c88ad35, e575508, 3e3f47f, 63ab297, 06cb52d, ac64840, 6178698 (T312728) [18:25:03] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.integraality/SAL [19:37:23] Hi everyone! I'm trying to set up my first Toolforge project and experiencing some difficulties. I would like it to a be a Vite+Vue application. So as a proof of concept, I though I'd just spin up a basic Hello World Vite+Vue project and try to run the web service. The application will be hosted at https://fr-toolkit.toolforge.org/ . Having [19:37:23] followed the instructions here https://wikitech.wikimedia.org/wiki/Help:Toolforge/Node.js#Deploying_a_Vue_JS_Application_using_Node_JS_and_Vite and finally running the webservice, I receive a "502 Bad Gateway" tab title plus a "Webservice is unreachable" message. [19:37:24] Things I have made sure along the way: [19:37:24] 1. Have the entire application reside in directory "www/js" [19:37:25] 2. Have a "start" script inside package.json as "start": "npm install && npm run build && node server.js" [19:37:25] 3. Have "express" as a dependency inside package.json [19:37:26] 3. Created "server.js" inside "www/js" and copied the code from the instructions. [19:37:26] I've currently stopped the webservice. Happy to follow any instructions or pointers you have for me! [19:37:27] Thank you everyone! [19:37:27] Panos [19:48:01] ppenloglou: was there anything in the logs? i suspect you'll have to start the server back up to use the `webservice logs` command [19:53:39] Ah! I hadn't tried "webservice logs", I'd only tried "webservice --backend=kubernetes node18 logs". The first command did come back with an error. [19:53:39] Pastebin: https://phabricator.wikimedia.org/P52658 [19:54:55] `webservice --backend=kubernetes node18 logs` and `webservice logs` are functionally identical, fwiw [19:55:04] 2023-09-26T19:50:33+00:00 [fr-toolkit-866b6dd96c-z255z] ReferenceError: require is not defined in ES module scope, you can use import instead [19:55:31] it seems like something has changed in the world of javascript packaging tools :/ [19:56:26] yeah, if the package.json says `"type": "module"` then you can’t use require() [19:56:59] the express docs still use require().. [19:57:08] ppenloglou: what happens if you swap `const express = require("express");` to `import express from "express";`? [19:59:19] taavi Bingo ! https://fr-toolkit.toolforge.org/ [20:00:07] That was it! Is it worth updating the instructions here https://wikitech.wikimedia.org/wiki/Help:Toolforge/Node.js#Deploying_a_Vue_JS_Application_using_Node_JS_and_Vite or was it a one-off for my case you think? [20:01:36] not sure. how did you create your package.json? [20:05:50] Following the instructions here https://vitejs.dev/guide/#scaffolding-your-first-vite-project and the command "npm create vite@latest". That command starts a terminal wizard with a few options (Vue,React -> Vanilla JS, TS). [20:18:40] yep, seems like that's a feature of the modern vite templates. i updated the docs