Feedback Request Service is running again. Sohom_Datta fix the problem:

panic: runtime error: index out of range [2] with length 0

goroutine 1 [running]:
main.extractGANom(...)
        /home/curtispf/Yapperbot/FRS/matchers.go:106
main.processCategory(0xc00023e930, 0x77c6e1, 0x1e, 0x0)
        /home/curtispf/Yapperbot/FRS/main.go:196 +0x211f
main.main()
        /home/curtispf/Yapperbot/FRS/main.go:57 +0x15e

$ grep 'panic: runtime error: index out of range' frs.err | wc -l
340
$ grep 'panic: runtime error: index out of range' frs.err -B 1|grep 2024|awk '{print $1}'|uniq -c
      1 2024/06/09
      2 2024/08/22
     24 2024/08/23
     23 2024/08/24
     22 2024/08/25
     21 2024/08/26
     17 2024/08/27

Thanks for the help with the login. I'll see if I can figure out what is causing the errors above.

FYI. It's still not working:
https://en.wikipedia.org/w/index.php?title=User_talk%3AYapperbot&diff=1242503263&oldid=1241904699
I am having trouble getting into Toolforge SSH to investigate. I requested help here:
https://en.wikipedia.org/w/index.php?title=User_talk:Novem_Linguae&oldid=1242502229#Need_help

In T361426#10086510, @bd808 wrote:

In T361426#10086509, @bd808 wrote:

Someone wrote to the page that causes the bot to halt. The edit looks like a vandal: https://en.wikipedia.org/w/index.php?title=User:Yapperbot/kill/FRS&diff=prev&oldid=1228880826

I reverted that edit: https://en.wikipedia.org/w/index.php?title=User:Yapperbot/kill/FRS&diff=prev&oldid=1241738467

I'm going to make this a priority. A user just reported that the Feedback Request Service has been shut down here:
https://en.wikipedia.org/w/index.php?title=User_talk:Yapperbot&oldid=1241596384#Feedback_request_service
I am not sure why it stopped, even though other Yapperbot functions seem to continue. Does anyone know why?

In T361426#10046351, @bd808 wrote:

@DavidTornheim I can turn the tool over to you, but only after breaking it by stopping the jobs and removing the bot password currently stored in $HOME/botpassword. Would you like me to take those actions now?

While you all are deciding what to do with the adoption process, could you please unprotect the code files in yapperbot so that they are readable by me? I would not need to be able to modify them--only read. At this point, I don't need the password. If you are unfamiliar with Go (language)--which is new to me too--I can do my best to explain what any or each of the files and directories are for. The documentation for the code is sparse, and I do plan to add documentation somewhere for future code review.

A number of the directories(folders) and files that run the yapperbot code are protected--at least for me. Try these commands:

cd /data/project/yapperbot
ls -ltR

(The last command is a recursive list of all files starting from the top directory.)
You will see that important directories (and files) are protected from view, e.g. /data/project/yapperbot/frs, which has the most important code.

In researching the above jobs, I looked up the "uncurrenter", originally approved as:

https://en.wikipedia.org/wiki/Wikipedia:Bots/Requests_for_approval/Yapperbot_2

It appears to have been taken over by ProcBot_10:

https://en.wikipedia.org/wiki/Wikipedia:Bots/Requests_for_approval/ProcBot_10

If that is the case, then should the job described above as:

name: uncurrenter
command: bash -c "cd uncurrenter && ./uncurrenter > /dev/null"
image: bookworm
schedule: "0 * * * * 
mem: 950M"

be disabled?