User talk:Ahecht/Archive 18

Archive 15

Archive 16

Archive 17

Archive 18

ArbCom 2023 Elections voter message

Hello! Voting in the 2023 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 11 December 2023. All eligible users are allowed to vote. Users with alternate accounts may only vote once.

The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.

If you wish to participate in the 2023 election, please review the candidates and submit your choices on the voting page. If you no longer wish to receive these messages, you may add {{NoACEMM}} to your user talk page. MediaWiki message delivery (talk) 00:30, 28 November 2023 (UTC)

New pages patrol January 2024 Backlog drive

New Page Patrol | January 2024 Articles Backlog Drive
On 1 January 2024, a one-month backlog drive for New Page Patrol will begin. Barnstars will be awarded based on the number of articles patrolled. Barnstars will also be granted for re-reviewing articles previously reviewed by other patrollers during the drive. Each review will earn 1 point. Interested in taking part? Sign up here.
You're receiving this message because you are a new page patroller. To opt-out of future mailings, please remove yourself here.

MediaWiki message delivery (talk) 02:09, 20 December 2023 (UTC)

flag icon changes breaking

Your flagicon changes are breaking some instances where a flag icon was deliberately not included, see e.g. Template:Top ten tennis players, where the Russian and Belrussian players don't use their country's flags. Can you please fix these? Iffy★Chat -- 21:00, 22 December 2023 (UTC)

@Iffy That's a very strange error, the module is supposed to return a placeholder image. I'll look into it. --Ahecht (TALK
PAGE) 01:17, 23 December 2023 (UTC)

@Iffy Fixed in Special:Diff/1191360775. If there are any pages with this error still displaying, you may need to do a WP:PURGE. Thanks for pointing it out! --Ahecht (TALK
PAGE) 02:05, 23 December 2023 (UTC)

I am curious

Could you kindly explain the purpose of adding "#ivoke" to {{cite web}}, {{cite news}} (but not {{cite magazine}}) like this? Ippantekina (talk) 12:09, 23 December 2023 (UTC)

@Ippantekina I am trying to reduce the post-expand include size of the article so that the references and navboxes at the bottom display correctly. The post-expand include size is basically the size of the text produced by templates. Since the {{cite web}} and {{cite news}} templates call Module:CS1, the text they produce gets counted twice (once for the template and once for the module). By replacing that with a call to the module directly, it cuts the effective size in half. The vast majority of the citations are {{cite web}} and {{cite news}}, so I only did a find-and-replace on those, which was sufficient (along with the other tweaks that I made) to get that page below the limit. If I needed further reductions in post-expand include size I could've searched for the other 20+ citation templates, but there are very quickly diminishing returns because they're used so infrequently. --Ahecht (TALK
PAGE) 16:27, 23 December 2023 (UTC)

Thank you for participating in AfC November 2023 Backlog Drive

		Here's a brownie for your efforts
		Thank you for your participation in the Articles for Creation's November 2023 Backlog Drive! You made a total of 8 reviews, for a total of 9.5 points. – robertsky (talk) 06:53, 25 December 2023 (UTC)

Happy holidays!

– robertsky (talk) is wishing you Happy Holidays! This greeting (and season) promotes WikiLove and hopefully this note has made your day a little better. Spread the WikiLove by wishing another user Happy Holidays, whether it be someone you have had disagreements with in the past, a good friend, or just some random person. Happy New Year!

Spread the cheer by adding {{subst:Happy holidays}} to their talk page with a friendly message.

– robertsky (talk) 06:53, 25 December 2023 (UTC)

Speedy deletion nomination of Category:Roller coasters planned to open in 2023

A tag has been placed on Category:Roller coasters planned to open in 2023 indicating that it is currently empty, and is not a disambiguation category, a category redirect, a featured topics category, under discussion at Categories for discussion, or a project category that by its nature may become empty on occasion. If it remains empty for seven days or more, it may be deleted under section C1 of the criteria for speedy deletion.

If you think this page should not be deleted for this reason you may contest the nomination by visiting the page and removing the speedy deletion tag. Liz ^{Read! Talk!} 18:25, 26 December 2023 (UTC)

Sounds good to me. Doubt there will be many more coasters opening this year. --Ahecht (TALK
PAGE) 19:14, 26 December 2023 (UTC)

Campaignbox

There are now a bunch of pages in Category:Pages with script errors after your change to Template:Campaignbox. It looks like it's because |name= was being used as |title= before, but now it's being used as the template name? I fixed one like this, which seems to be correct now? Plastikspork _―Œ^(talk) 14:51, 27 December 2023 (UTC)

Okay, I had a bot fix all the script errors in articles. Many of these look like someone cut-and-paste something that should be in a template shared between articles, but I will leave that to someone else to clean up. Thanks! Plastikspork _―Œ^(talk) 15:42, 27 December 2023 (UTC)

@Plastikspork I also fixed it in the module here so that it won't be a problem in the future. --Ahecht (TALK
PAGE) 20:03, 27 December 2023 (UTC)

Kubernetes migration

Hello, Ahecht! Some time ago you've helped me fork you script on my bot. These days the old grid was shut down and every job is to be migrated to Kubernetes. Do you have any quick guide how I can easily migrate that job in there? Maybe some steps that you yourself had to take? I migrated my other jobs on my bot and I'm planning on starting on this one now, which is my final one. - Klein Muçi (talk) 00:08, 26 December 2023 (UTC)

Just for reference, this is our old conversation. - Klein Muçi (talk) 00:47, 26 December 2023 (UTC)

@Klein Muçi I don't see your bot listed at https://grid-deprecation.toolforge.org/ so you may already be running it on Kubernetes. If you log into your tool account and enter toolforge job list, does it show up? If not, you can use crontab -e to comment out the line that runs your script on grid engine (put a # at the start of the line to comment it out), save the crontab file, and then on the command line do toolforge jobs run Smallem-Transclusion --command "$HOME/venv/bin/python3 $HOME/Smallem-Transclusion.py" --image python3.11 --schedule "0 13 1 * *", changing the command and schedule to match what you had on your crontab. This is documented at wikitech:Help:Toolforge/Jobs_framework --Ahecht (TALK
PAGE) 01:04, 26 December 2023 (UTC)

@Klein Muçi You also may need to update to the October 2022 version of the script (User:Ahechtbot/transclusioncount.py or User:Ahechtbot/sandbox/transclusioncount.py) if you haven't already, as there were some changes made to where the information is stored in the databases that the script accesses. --Ahecht (TALK
PAGE) 01:16, 26 December 2023 (UTC)

Hey there and thank you for the fast reply! My bot is not on that list because all its jobs are monthly so it hasn't been running anything on the past week. If I try toolforge job list I only get my other job listed which was migrated to Kubernetes just yesterday, hence why I started dealing with this today.

I tried toolforge jobs run myjob --command "$HOME/venv/bin/python3 ./Smallem-Transclusion.sh" --image python3.11 just to test it out (my script lives on ~/Smallem-Transclusion.sh) and the job fails with this traceback:

Traceback (most recent call last):

File "/data/project/smallem/./Smallem-Transclusion.sh", line 1, in <module>

import toolforge

ModuleNotFoundError: No module named 'toolforge'

I have yet to update the code (I thank you for reminding me of that!). I'll continue with it as soon as I'm able to make the job work on Kubernetes. - Klein Muçi (talk) 10:24, 26 December 2023 (UTC)

@Klein Muçi sounds like either you're not pointing to the correct venv, or it's using the wrong version of Python. Try running through the instructions in the header of the new version of the script to create a new venv in the pyvenv folder and set up a job to use that. --Ahecht (TALK
PAGE) 16:02, 26 December 2023 (UTC)

I created a bootstrap script by copy-pasting the content from the instructions and including the 4 listed packages in the script's header. Then I followed the other instructions to grant the correct permissions and run it. Should I run this later on source pyvenv/bin/activate and then use the command I used above or just use it straight away?

I tried both variants and job fails with the same message in both occasions unfortunately. :/ Klein Muçi (talk) 17:16, 26 December 2023 (UTC)

@Klein Muçi Sorry for the confusion. Once you create the bootstrap script, make sure you add the following lines to the bottom (and that there aren't any #s at the beginning of the lines):

pip install toolforge
pip install pywikibot
pip install "mwparserfromhell>=0.5.0"
pip install "wikitextparser>=0.47.5"

I also just noticed that they updated the instructions to use python 3.11, but I've only tested the script it against 3.9. That means you'll want to run the bootstrap script with toolforge jobs run bootstrap-venv --command "cd $PWD && ./bootstrap_venv.sh" --image python3.9 --wait. You shouldn't ever need to use the source command manually, the only time you need it is when it's included in the bootstrap-venv.sh script. It also looks like they changed the image name from tf-python39 to python3.9, so when you schedule the script you should do it with the equivalent of toolforge-jobs run transclusioncount --command "pyvenv/bin/python scripts/transclusioncount.py" --image python3.9 --schedule "00 12 * * SUN". If you run the bootstrap script with the one image and try to run the script with the another it won't work. --Ahecht (TALK
PAGE) 19:35, 26 December 2023 (UTC)

Yes, I have included those 4 packages.

I tried running toolforge-jobs run transclusioncount --command "pyvenv/bin/python ./Smallem-Transclusion.sh" --image python3.11 while having the same image (python3.11) on the bootstrap script.

Then I tried the same thing changing the image for both cases, downgrading to python3.9 I also tried using pyvenv/bin/python3 instead of pyvenv/bin/python

In all cases I get the same message error:

CRITICAL: Exiting due to uncaught exception NousernameError: Logged in on wikipedia:sq via OAuth as 172.16.2.172, but expect as Smallem

In the traceback there are also some mentions about a module named 'requests_oauthlib' not existing. (Can share the full traceback if you want.) - Klein Muçi (talk) 21:24, 27 December 2023 (UTC)

Maybe I should add pip install requests_oauthlib to the bootstrap script? - Klein Muçi (talk) 21:54, 27 December 2023 (UTC)

I added pip install requests_oauthlib to the bootstrap script and it doesn't show any errors anymore, no matter what image or interpreter I use. The only problem is that no changes are being made. I let it run for 30 minutes and still nothing happened. I will try leaving it on for a longer period of time. - Klein Muçi (talk) 10:36, 28 December 2023 (UTC)

Currently it has been ~6 hours running and still not a single edit was done by my bot. At this point I'm convinced no actual job is being done. Not sure what is going wrong though... - Klein Muçi (talk) 16:09, 28 December 2023 (UTC)

@Klein Muçi I forgot that you were using oauth to log in. My bot isn't, so it didn't need that library. What do your transclusioncount.out and transclusioncount.err files say? The .out file should show when it started trying to fetch the query and if it finished, and the .err file should show you logging in (it will also show writes to wiki, if it gets that far). --Ahecht (TALK
PAGE) 18:24, 28 December 2023 (UTC)

The .out file it's empty while the .err one shows the logging header, a list of packages, a big list of modules and then it gets stuck there, the last line reading:

Found 2 wikipedia:sq processes running, including this one.

This all gets shown in the immediate beginning and then nothing happens anymore. It's been 8 hours now and that is still the last message in there. - Klein Muçi (talk) 18:32, 28 December 2023 (UTC)

After a full day of running and doing nothing, the job was stopped by itself with this error message:

(1054, "Unknown column 'tl_title' in 'field list'")

Dropped throttle(s).

Closing network session.

Network session closed.

Comparing my version of the script with your updated one, changing tl to lt was one of the main changes so maybe it is related to that? I'm updating the script and retrying. - Klein Muçi (talk) 10:43, 29 December 2023 (UTC)

It works!

I'm running it on python3.11 and it works perfectly fine so you might want to update your documentation. Also while doing that you might also include the mention of pip install requests_oauthlib because many users might be in my situation. Finally I believe there is a typo in this line:

When creating the bootstrap_venv.sh file as described above, include the following four lines (without the ""s at the start of each line)

Check the part in parentheses.

Thank you again for your help! - Klein Muçi (talk) 12:01, 29 December 2023 (UTC)

@Klein Muçi Glad you got it working! Looks like pywikibot wants the whole requests library, so I added that to the documentation. --Ahecht (TALK
PAGE) 06:03, 31 December 2023 (UTC)

You are now an afdstats maintainer!

Sup! I saw your recent PR at afdstats. Legoktm advised me that with that sort of dedication you might as well be a maintainer, and I thought that was a solid point and made it so, so you are now listed as a maintainer for afdstats. Go wild! Enterprisey (talk!) 00:58, 5 January 2024 (UTC)

@Enterprisey Sorry for not responding sooner, but I've been off wiki for a couple of weeks. Thanks for that, although I hope to not have to use it! --Ahecht (TALK
PAGE) 08:04, 17 January 2024 (UTC)

Rugby World Cup

Thanks for noticing that I mistyped the LST on 2023 Rugby World Cup. Out of curiosity, now that that's been sorted, do the pool stages really need to have the {{cite web}} etc use the #invoke call directly or can those edits be reverted? Primefac (talk) 08:51, 19 January 2024 (UTC)

@Primefac I was in the middle of reverting that when my internet went out yesterday. I agree that there's no need for those more drastic measures any more. --Ahecht (TALK
PAGE) 21:56, 19 January 2024 (UTC)

Spiffy. Primefac (talk) 22:05, 19 January 2024 (UTC)

Module idea

Someone's requested a {{page-range}} template for putting in pages that should be separated by an en dash, for people who aren't too handy with getting at that character. I think it would have rather limited use, and should be flagged as an always-substitute template so bots replace it, but would have some use, and as module could maybe even be invoked from inside some other templates to normalize poor-quality input, if what I suggested below were to be done with a clever module. I was cobbling together something to just take {{page-range|23|31}} and output 23–31, but then I remembered your tweaking of the module beind Module:Section link to parse the first parameter for # and auto-handle what follows as if it had been {{{2}}}, and this suggested to me that we could have a template that would accept the above two-page-numbers-as-separate-parameters input, but also parse {{page-range|23-31}} or {{page-rage|23 - 31}} or {{page-rage|23–31}} or {{page-range|23—31}} or whatever and always produce the same result. But I can't Lua my way out of a paper bag (more of a bash and JS and perl and php nerd).  — SMcCandlish ☏ ¢ [😼  07:49, 24 January 2024 (UTC)

• @SMcCandlish: You could do it with {{safesubst:#if:{{{2|}}}|{{{1|}}}–{{{2}}}|{{safesubst:#invoke:string|replace|{{{1|}}}|%s*[-–—]%s*|–|plain=false}}}}, which makes use of the existing Module:string. --Ahecht (TALK
  PAGE) 15:27, 24 January 2024 (UTC)

  Ah yes! I was sure you'd have the answer. I implemented a fancified version at Template:Page range. Just to be sure, this Lua-internal variant of regex [...] doesn't requiring escaping anything like -?  — SMcCandlish ☏ ¢ 😼  00:51, 25 January 2024 (UTC)

  @SMcCandlish Lua patterns, at least in the current implementation, are smart enough to know that that a dash as the first item in a set is a literal dash and not a quantifier or indicating a range, but if you want belt-and-suspenders, you can replace [-–—] with [%-–—] (Lua patterns uses % as the escape character instead of \). --Ahecht (TALK
  PAGE) 04:08, 25 January 2024 (UTC)

  Got it. Would it need that escape char if the hyphen were in the middle of that stuff?  — SMcCandlish ☏ ¢ 😼  04:10, 25 January 2024 (UTC)

  @SMcCandlish Yeah, it would interpret [–-—] as all the ascii characters between – and —. In this case, since they are adjacent, it would just match those two, but if they weren't adjacent it would also accept anything in between. If you wanted to be really tricky you could use [‐-―] which would match ‐, ‐, –, —, and ― since they're ASCII codes 8208 - 8213, but that's the sort of thing you'd do in code golf, not in real life. --Ahecht (TALK
  PAGE) 04:26, 25 January 2024 (UTC)

  I put the escape char in just in case someone puts some other character in front of the hyphen-minus not realizing that would convert it into a range indicator in the expression. Better safe than sorry!  — SMcCandlish ☏ ¢ 😼  04:54, 25 January 2024 (UTC)

"you can't reference an anchor that starts with a #"

re this edit, you actually can: compare Help:Template limits##invoke syntax and Help:Template limits#invoke syntax. ;) 「ディノ奴千？！」^{☎ Dinoguy1000} 07:30, 2 February 2024 (UTC)

@Dinoguy1000 must be browser dependent, as neither of those worked for me before adding the manual anchor. --Ahecht (TALK
PAGE) 13:15, 2 February 2024 (UTC)

I'm using Firefox, though I assumed this worked in all browsers considering it's the typical way to link to the ParserFunction documentation on MW.org: mw:Help:Extension:ParserFunctions##if for example. If this is indeed browser-dependent, that page (and probably some others) needs some anchors added. 「ディノ奴千？！」^{☎ Dinoguy1000} 22:30, 2 February 2024 (UTC)

JWB fyi...

From your JWB run doing WP:PEIS edits on Feb 7, the following edit broke the last table on the page: [1]. Seems the change of |dontclose=y which added a template close did not account for the existing template close of {{Episode table}}. I'm not sure if the JWB regex/script you're running there is one you use regularly, or if it was just a one-off run, but you may want to review this to improve/adjust your script for future use. ButlerBlog (talk) 20:14, 15 February 2024 (UTC)

@Butlerblog Thanks for the heads up. The RegEx I'm using is pretty crude so I have to search for those sorts of edge cases manually on each page before saving. Looks like I missed one. The good news is that the flurry of edits that I did adding |dontclose=y were because an update to the module behind {{episode table}} caused a bunch of TV show pages to exceed the limit, so hopefully I shouldn't have to do any more of those particular edits in the future. --Ahecht (TALK
PAGE) 20:31, 15 February 2024 (UTC)

Edits broke templates

The names of the senators are no longer showing after this edit. Please fix or revert. There are a lot of them. – Jonesey95 (talk) 05:15, 29 February 2024 (UTC)

@Jonesey95 Thanks, don't know why I didn't catch that. They're all set now. --Ahecht (TALK
PAGE) 06:40, 29 February 2024 (UTC)

Thanks for the quick fixes. – Jonesey95 (talk) 17:19, 29 February 2024 (UTC)

RFA2024 update: no longer accepting new proposals in phase I

Hey there! This is to let you know that phase I of the 2024 requests for adminship (RfA) review is now no longer accepting new proposals. Lots of proposals remain open for discussion, and the current round of review looks to be on a good track towards making significant progress towards improving RfA's structure and environment. I'd like to give my heartfelt thanks to everyone who has given us their idea for change to make RfA better, and the same to everyone who has given the necessary feedback to improve those ideas. The following proposals remain open for discussion:

• Proposal 2, initiated by HouseBlaster, provides for the addition of a text box at Wikipedia:Requests for adminship reminding all editors of our policies and enforcement mechanisms around decorum.
• Proposals 3 and 3b, initiated by Barkeep49 and Usedtobecool, respectively, provide for trials of discussion-only periods at RfA. The first would add three extra discussion-only days to the beginning, while the second would convert the first two days to discussion-only.
• Proposal 5, initiated by SilkTork, provides for a trial of RfAs without threaded discussion in the voting sections.
• Proposals 6c and 6d, initiated by BilledMammal, provide for allowing users to be selected as provisional admins for a limited time through various concrete selection criteria and smaller-scale vetting.
• Proposal 7, initiated by Lee Vilenski, provides for the "General discussion" section being broken up with section headings.
• Proposal 9b, initiated by Reaper Eternal, provides for the requirement that allegations of policy violation be substantiated with appropriate links to where the alleged misconduct occured.
• Proposals 12c, 21, and 21b, initiated by City of Silver, Ritchie333, and HouseBlaster, respectively, provide for reducing the discretionary zone, which currently extends from 65% to 75%. The first would reduce it 65%–70%, the second would reduce it to 50%–66%, and the third would reduce it to 60%–70%.
• Proposal 13, initiated by Novem Lingaue, provides for periodic, privately balloted admin elections.
• Proposal 14, initiated by Kusma, provides for the creation of some minimum suffrage requirements to cast a vote.
• Proposals 16 and 16c, initiated by Thebiguglyalien and Soni, respectively, provide for community-based admin desysop procedures. 16 would desysop where consensus is established in favor at the administrators' noticeboard; 16c would allow a petition to force reconfirmation.
• Proposal 16e, initiated by BilledMammal, would extend the recall procedures of 16 to bureaucrats.
• Proposal 17, initiated by SchroCat, provides for "on-call" admins and 'crats to monitor RfAs for decorum.
• Proposal 18, initiated by theleekycauldron, provides for lowering the RfB target from 85% to 75%.
• Proposal 24, initiated by SportingFlyer, provides for a more robust alternate version of the optional candidate poll.
• Proposal 25, initiated by Femke, provides for the requirement that nominees be extended-confirmed in addition to their nominators.
• Proposal 27, initiated by WereSpielChequers, provides for the creation of a training course for admin hopefuls, as well as periodic retraining to keep admins from drifting out of sync with community norms.
• Proposal 28, initiated by HouseBlaster, tightens restrictions on multi-part questions.

To read proposals that were closed as unsuccessful, please see Wikipedia:Requests for adminship/2024 review/Phase I/Closed proposals. You are cordially invited once again to participate in the open discussions; when phase I ends, phase II will review the outcomes of trial proposals and refine the implementation details of other proposals. Another notification will be sent out when this phase begins, likely with the first successful close of a major proposal. Happy editing! theleekycauldron (talk • she/her), via:

MediaWiki message delivery (talk) 10:52, 14 March 2024 (UTC)

Infobox Election is broken again.

See, e.g. this page, please fix ASAP https://en.wikipedia.org/wiki/1976_United_States_presidential_election_in_Nebraska. DemocraticLuntz (talk) 18:01, 15 March 2024 (UTC)

Every single election page is broken, please revert or fix ASAP!! ~ Eejit43 (talk) 18:04, 15 March 2024 (UTC)

@DemocraticLuntz@Eejit43 All fixed. I had tested it and had it working in my sandbox, but it looks like I pasted in the wrong version. --Ahecht (TALK
PAGE) 18:06, 15 March 2024 (UTC)

Thanks! :) ~ Eejit43 (talk) 18:07, 15 March 2024 (UTC)

Also, in this code:

{{#invoke:Math|max|

the final "|" should be removed. It gets a duplicate "1" parm error. Davemck (talk) 18:21, 15 March 2024 (UTC)

@Davemck Strange, I didn't see any errors pop up in my testing, but you're absolutely right, that pipe shouldn't be there. --Ahecht (TALK
PAGE) 18:23, 15 March 2024 (UTC)

Hello, Ahecht—the alliance parameter is still going wonky (unless it is some other bad input)—please see the image I uploaded to the right. Also, please refer to Template talk:Infobox election; there is more discussion over there. — 3PPYB6 ^{(T / C / L)} — 18:55, 15 March 2024 (UTC)

@3PPYB6 should be fixed (and there is now a test case in place to catch that error). --Ahecht (TALK
PAGE) 22:04, 15 March 2024 (UTC)