Wikipedia Talk:ReFill

{{lowercase title}}

{{Notice |1=If the tool is stuck displaying "waiting for an available worker" or "Submitting your task...", and you have a Phabricator login, then you can use [https://phabricator.wikimedia.org/maniphest/task/create/?projects=Tool-refill&title=Refill%20tool%20stuck%20%22waiting%20for%20an%20available%20worker%22 this link] to raise a report to get it restarted. Just fill in the Description field and hit the "Create New Task" button.

Maintainers of the code: restart instructions}}

{{archives|bot=lowercase sigmabot III|age=90}}

{{User:MiszaBot/config

| algo = old(100d)

| archive = Wikipedia talk:ReFill/Archive %(counter)d

| counter = 4

| maxarchivesize = 150K

| archiveheader = {{Automatic archive navigator}}

| minthreadstoarchive = 1

| minthreadsleft = 8

}}

Doesn't work

{{tracked|T389775}}

I click on the arrow and literally nothing happens. --Bageense(disc.) 22:08, 23 March 2025 (UTC)

:I am able to reproduce. https://refill.toolforge.org/ng/, article "2023 Nigerian Senate election". In the JavaScript console, I am getting a CORS error and a {{tq|TypeError: Cannot read properties of undefined (reading 'data')}}. [https://imgur.com/a/IREi5o7 Screenshot with more details.] Mentioned in Discord as a possible cause to investigate: phab:T322944. –Novem Linguae (talk) 23:06, 23 March 2025 (UTC)

::Someone on Discord has pointed out that perhaps the CORS error is a distraction and the fundamental problem is actually getting a 504 Gateway Timeout error when trying to load the API https://refill-api.toolforge.org/fixWikipage. The 504 error page would be missing an ACAO CORS header, generating the CORS error, but the fundamental problem is the timeout itself. –Novem Linguae (talk) 04:19, 24 March 2025 (UTC)

:::The API hasn't been serving requests since [https://grafana.wmcloud.org/d/TJuKfnt4z/kubernetes-namespace?orgId=1&var-namespace=tool-refill-api&var-cluster=prometheus-tools&from=1742689246390&to=1742698986682 around 28 hours ago]. Probably needs a restart. Chlod (say hi!) 05:16, 24 March 2025 (UTC)

: I'll add that I've been experiencing an issue for potentially 24 hours where the screen stalls at "Submitting your task..." Significa liberdade (she/her) (talk) 04:17, 24 March 2025 (UTC)

::I'm looking into this. I have done the usual restarts, and it is now stuck at "waiting for an available worker" rather than "Submitting your task..." which is progress, but I haven't got much time to look at it today. Curb Safe Charmer (talk) 10:43, 24 March 2025 (UTC)

::Fixed now, with thanks to {{u|TheresNoTime}}. Curb Safe Charmer (talk) 15:17, 24 March 2025 (UTC)

:::Maybe one of you would be willing to type up the work instruction for how to fix this (restart) and post it on wiki somewhere? If so I'd be happy to try it next time. I think I have enough access, and refill seems to get stuck often enough that it would be useful to have a procedure for this. –Novem Linguae (talk) 17:26, 24 March 2025 (UTC)

::::{{reply|Novem Linguae}} Thanks, good suggestion. Done. See Wikipedia:Refill/restart. Though this didn't work this time, due to code in the restart script that was no longer supported I believe. Curb Safe Charmer (talk) 21:25, 24 March 2025 (UTC)

Using Refill on iOS Safari

I’ve been trying to use Refill for a while, and while I use it heavily on desktop, if I try to use it on my phone it’s not behaving itself. I’ll run the bot on a page, it’ll show a correct preview… but when I go to preview/save the edits on the actual page, none of the changes are carried over and the source editor shows no changes being made. Any suggestions? Danners430 (talk) 18:59, 12 April 2025 (UTC)

deadurl?

Why does refill use the non-existent parameter deadurl=y? Can't someone just change it in the code or something to be url-status=dead instead? Schützenpanzer (Talk) 20:26, 20 April 2025 (UTC)

:See #Error on dead links above. This has been happening since 2019. – Jonesey95 (talk) 21:06, 20 April 2025 (UTC)

Please enable Issues in GitHub repo

Could you please enable Issues in the GitHub repo so that bugs can be reported and tracked properly?

This allows searching them more easily, has one separate discussion for every issue, each with a descriptive title, allows getting an email when people discuss or solve the issue, and many other things. That's why most open source repos have a proper issue tracker and not just some discussion forum page.

For example, would it be possible to also add the language parameter to references based on the url and/or title? (e.g. |language=en). This would be especially useful on German Wikipedia where this parameter is required (currently, one has to edit each refilled ref manually to add that parameter). Also see these proposals. If things turn out to be related to citoid the tool uses then those issues could be simply closed and the user(s) directed to the proper place to report these. {{ping|Curb Safe Charmer}}.
Prototyperspective (talk) 22:55, 28 April 2025 (UTC)

:We disabled GitHub Issues because we are using Phabricator. The tag is Tool-refill. https://phabricator.wikimedia.org/project/view/5013/ –Novem Linguae (talk) 23:53, 28 April 2025 (UTC)

::Thanks; read over that part.

::{{Section resolved|1=Prototyperspective (talk) 11:28, 29 April 2025 (UTC)}}

Is it labs-stable branch?

The page says "Note that the version of refill installed on toolforge uses the labs-stable branch." Is that correct? There has been no development in that branch for 8-10 years. 108.60.227.33 (talk) 12:55, 9 May 2025 (UTC)

:According to some pull requests I made in 2023 when I last looked at this (https://github.com/CurbSafeCharmer/refill/pull/262, https://github.com/CurbSafeCharmer/refill/pull/261), I think labs-rewrite is the old version that we killed off recently when it broke. The new version, refill.toolforge.org/ng, uses the master branch.

:Note that even the refill.toolforge.org/ng / master branch hasn't had a deploy since July 8, 2020, according to the timestamps of the files on Toolforge. This repo is kind of in "only make changes if it breaks" mode since none of the current volunteers understand the code very well. –Novem Linguae (talk) 13:56, 9 May 2025 (UTC)