[06:59:32] !log paws stop remaining old servers to pick up NFS changes - T432583 [06:59:36] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Paws/SAL [06:59:37] T432583: Make sure dumps-nfs mounts are propagated inside PAWS containers - https://phabricator.wikimedia.org/T432583 [11:41:39] !log paws cordon paws-127d-mq2566hee6zs-node-4 - T435587 [11:41:44] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Paws/SAL [11:41:44] T435587: [bug] server won't launch - https://phabricator.wikimedia.org/T435587 [11:47:06] !log paws reboot paws-127d-mq2566hee6zs-node-4 due to high load average - T435587 [11:47:09] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Paws/SAL [11:47:10] T435587: [bug] server won't launch - https://phabricator.wikimedia.org/T435587 [13:59:13] I'm testing use of the Action API in the API sandbox, prop=revisions https://www.mediawiki.org/wiki/API:Revisions *rvsection* [13:59:15] Only retrieve the content of the section with this identifier. The documentation does not define "identifier". I tried using the section header and that did not work, it only returned section "0" i.e. just the text above the first section heading. Then I tried section number (3) and that worked. But making my code figure out the section number is harder to code. Is there a [13:59:15] trick [13:59:16] to make it work with the section title? [14:27:39] OK, I asked ChatGPT—- No. `rvsection`* does not accept the section title itself.* It expects the *section identifier/index* returned by MediaWiki's section parsing machinery. the usual workflow is: [14:27:40] Call `action=parse&prop=sections` to get the sections. [14:27:42] Find the section whose `line`/title matches what you want. [14:27:43] Take its `index`. [14:27:45] Pass that index as `rvsection`. [14:29:05] I shouldn't have to ask ChatGPT, this should be explained by the Action API documentation [14:55:52] !log admin reimaging cloudvirt1042, getting a 100% fresh start for T429387 testing [14:55:59] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Admin/SAL [14:56:00] T429387: cloudceph HEALTH_WARN, multiple OSD(s) experiencing slow operations in BlueStore - https://phabricator.wikimedia.org/T429387 [16:35:58] I don’t know why you bothered to ask ChatGPT, it sounds like you had already figured out that it doesn’t take a section title… but okay: https://gerrit.wikimedia.org/r/c/mediawiki/core/+/1328213 (re @Bill: I shouldn't have to ask ChatGPT, this should be explained by the Action API documentation) [20:12:03] @Bill: I see your frustration, and I'm sorry. Also if an LLM could explain what to do for you it is actually documented somewhere, just not in the places you looked. The chatbot you interacted with does not have the ability to think. It can only summarize information that it has been shown from some external source. [20:13:36] I +2'd the patch by Lucas that will hopefully help folks discover detail of what a "section identifier" is in that context with less frustration. [20:34:39] !log bd808@tools-bastion-14 tools.wheres-my-code-running First! (initialze SAL page) [20:34:41] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.wheres-my-code-running/SAL [21:03:59] 👀 [21:04:49] so, basically a shortcut for `git branch -r --contains` + https://versions.toolforge.org/ ? [21:05:06] (also TIL https://en.wikipedia.org/w/deployment-info.php, is it new? *looks*) [21:06:43] (a bit over a week apparently, interesting https://gerrit.wikimedia.org/r/c/operations/mediawiki-config/+/1324339) [21:15:09] @lucaswerkmeister: yeah all new magic from dancy. swfrench-wmf was dreaming of a way developers could tell where their code was running and Ahmon figured out a pretty neat mechanism. [21:15:30] nice 😍 [21:15:45] and I imagine this will be well useful with pretrain too [21:16:01] seems likely ;) [21:17:08] If we can get Beta Cluster stable enough to answer the deployment-info.php consistently we can report when patches have landed there too. [21:18:09] Yeah, this was inspired by the pretrain work