User talk:Legobot

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search

Legobot Legobot II Legobot III Hockeybot ArticleAlertbot TFA Protector

No longer receiving RFC notices[edit]

Can anyone watching this page try and figure out why I've stopped receiving RFC notices from this bot? I haven't changed the FRS list, and ClueBot III's archiving is still working fine, so I have no idea why this is happening. Here is a diff from Legobot's last edit to the current version of my talk page. Thanks for any assistance. IffyChat -- 09:14, 22 November 2018 (UTC)

The task apparently ran normally this morning: this was the last FRS post by Legobot, less than five hours before Iffy (talk · contribs) posted above. --Redrose64 🌹 (talk) 20:38, 22 November 2018 (UTC)
@Iffy and Redrose64: I haven't received anything since October 25th, and I used to get stuff regularly. If it's because there aren't a lot of open Rfc's and Legobot is all caught up, then that's great. But if that's the case, what's the explanation for this: there's an Rfc at Talk:Anatolia with only one responder since it opened on Nov. 25, and that user has no FRS notice, so nobody has responded through a notice. Is there a way to look at whether Legobot has paged anyone to that Rfc? And if not, why not? Is there someplace we can go to view an English description of the algorithm Legobot uses, or view the code directly? Mathglot (talk) 23:30, 5 December 2018 (UTC)
Short answer: Legobot has not used FRS to inform anybody about the RfC at Talk:Anatolia.
To see which FRS subscribers Legobot has informed, go to its contributions (they're linked in the left margin of this page), and restrict to User talk: space, which yields this list. Then search for "Please comment on Talk:Anatolia: new section". You need not go back earlier than 00:01, 26 November 2018 (UTC) because Legobot begins sending out FRS notifications at midnight each day, and that RfC was initiated on 25 November 2018. If you like, you can expand to 250 or 500 edits rather than 50. Of course, this method would fail if there was more than one open RfC at Talk:Anatolia, but there isn't.
I don't know where the bot's code (source or algorithm) may be viewed. --Redrose64 🌹 (talk) 23:39, 5 December 2018 (UTC)
Thanks, that's very useful information. I wonder what other people's experience is? Mathglot (talk) 01:00, 6 December 2018 (UTC)
@Mathglot and Redrose64: The source code for this Legobot task is available at and (as is indirectly linked on the bot's userpage). {{3x|p}}ery (talk) 00:52, 13 March 2019 (UTC)
Thanks for checking into this. I haven't received a notice since October 25. Usually I'm getting them every 1-2 weeks. petrarchan47คุ 09:32, 6 December 2018 (UTC)
I also have received any RfC notices since around the same date (October 24 for me) after previously receiving them every few days prior to this date. Something must be going on with this bot surely, if at least three editors have experienced this around the same time -- Whats new?(talk) 03:01, 9 December 2018 (UTC)
Me too. Nothing since the 24th Oct. Cesdeva (talk) 22:05, 30 December 2018 (UTC)
I first signed up on 26 Oct, and haven't gotten a single notice... --DannyS712 (talk) 10:27, 5 January 2019 (UTC)
@Legoktm Any ideas? I know I'm in Legobots' bad books for being inactive, could that be why? Thanks, Cesdeva (talk) 20:20, 7 January 2019 (UTC)
...still haven't gotten one. --DannyS712 (talk) 04:45, 14 February 2019 (UTC)

I suspect this is being caused by phab:T213475. Legoktm (talk) 05:34, 6 February 2019 (UTC)

@Iffy, Mathglot, Petrarchan47, Whats new?, and Cesdeva:: I believe the problem should be fixed now. Please let me know if you think it's still not working... Legoktm (talk) 17:45, 13 February 2019 (UTC)
Thanks, I'll monitor and let you know. To date: last notice: Oct. 25. Mathglot (talk) 18:02, 13 February 2019 (UTC)
Aaand, expect spotty behavior (actually I'd expect no notices to go out) while toolsdb is down. Stay tuned. Legoktm (talk) 07:50, 17 February 2019 (UTC)
@Legoktm:, okay; is there a Phab ticket or other repot I can subscribe to, to follow along? Mathglot (talk) 11:54, 18 February 2019 (UTC)
@Legoktm: It's been months since I've gotten any notices. TimTempleton (talk) (cont) 21:13, 28 February 2019 (UTC)
@Legoktm: Today I received my first notice since October. Hope it continues normally from here. Thanks, Mathglot (talk) 09:06, 14 March 2019 (UTC)
@Cesdeva, Iffy, Petrarchan47, Timtempleton, and Whats new?: In addition to DannyS712 and Mathglot, you have all received FRS messages today. Hopefully this will continue. --Redrose64 🌹 (talk) 11:35, 14 March 2019 (UTC)
I haven't received a notice since 2016 (and I just noticed it right now, so that's kind of impressive not). --qedk (t c) 19:18, 28 April 2019 (UTC)
@Redrose64: Sorry to annoy you but could you shed some light on my stupidity somewhere ^ --qedk (t c) 19:58, 16 May 2019 (UTC)
I don't know why your name isn't being selected. I've fixed up some unusual entries that may have had a knock-on effect. --Redrose64 🌹 (talk) 12:14, 17 May 2019 (UTC)
Let's see if that works. Face-smile.svg --qedk (t c) 13:45, 17 May 2019 (UTC)

RfC notices[edit]

Hi. I posted this above, but got no response, as part of the section on not receiving notices. That issue seems to have been resolved, but I have not yet received a single RfC notice. Did I add myself incorrectly or something? Thanks, --DannyS712 (talk) 00:55, 13 March 2019 (UTC)

There is evidence that Legobot has been sending the messages to various users pretty much every day, going back several months - apart from a brief interval in mid February 2019, see contributions in user space and search for "Please comment on". It might be that it works its way through a list and for some reason is not reaching the end of the list. Perhaps one of the entries at WP:FRS#Requests for comment is malformed; it doesn't necessarily have to be yours. What we need to do is prepare a list of known successes from those contribs, and compare this against the FRS list to see who has never been informed. One of those people is probably the culprit. --Redrose64 🌹 (talk) 12:06, 13 March 2019 (UTC)
@Redrose64: I made this edit to try to clean up the page - hopefully that solves it --DannyS712 (talk) 19:46, 13 March 2019 (UTC)
It's worth a try. --Redrose64 🌹 (talk) 23:12, 13 March 2019 (UTC)
If the page is malformed, wouldn't the breaking edit have to have been performed in October when the notices stopped? {{3x|p}}ery (talk) 23:15, 13 March 2019 (UTC)
@Pppery and Redrose64: It worked!!! Special:Diff/887683065. Thank you both for the help --DannyS712 (talk) 04:41, 14 March 2019 (UTC)
Going by Peppery's theory of October, and the apparent success of the blank-line removal (see previous post and subsection), I looked at the edits for October - and found only one where blank lines were added, it was this one by L3X1 (talk · contribs). We need to document that somewhere (along with all the other Legobot quirks): Thou shalt not introduce blank lines. Not only does it violate WP:LISTGAP, it also causes users to be skipped. --Redrose64 🌹 (talk) 09:57, 14 March 2019 (UTC)
Mea culpa everybody. Thanks,L3X1 ◊distænt write◊ 13:47, 14 March 2019 (UTC)

Please add GA icon to Ānanda[edit]

Thanks.--Farang Rak Tham (Talk) 15:20, 3 April 2019 (UTC)

 Done, as a manual job - I have found that Legobot has difficulties with pages that have certain diacritics in their names, including the macron. --Redrose64 🌹 (talk) 23:05, 3 April 2019 (UTC)

MFD glitch[edit]

[1]. The bot seems to think that the discussion at Wikipedia:Miscellany for deletion/Portal:Carnatic music dates from 1970, presumably the start of Unix time. --BrownHairedGirl (talk) • (contribs) 03:43, 23 April 2019 (UTC)

The bot has been repeatedly doing this. Here is the latest[2]. --BrownHairedGirl (talk) • (contribs) 05:24, 23 April 2019 (UTC)
I have blocked the bot for 48 hours to prevent any recurrence. Any admin who believes the problem has been resolved, please unblock. --BrownHairedGirl (talk) • (contribs) 05:27, 23 April 2019 (UTC)
Note: the problem appears to have been with the Miscellany for deletion nomination itself: the timestamp was malformed, which doubtless caused Legobot to choke on the bad data. I've fixed the nomination page; hopefully, some admin will come along and unblock this. This has been reported at Wikipedia:Administrators' noticeboard/Incidents#Legobot blocked. With any luck, an admin will unblock Legobot soon, so it can go back to its many tasks, including generating updated WP:GAN pages. BlueMoonset (talk) 06:38, 23 April 2019 (UTC)
 Done. AGK ■ 06:52, 23 April 2019 (UTC)
@BrownHairedGirl, BlueMoonset, and AGK: It has been known for a long time that the only timestamps recognised by Legobot are those that are in the same format as would be produced by signing with four or five tildes. Anything else will simply be treated as plain text and not be processed as a timestamp; in such a situation, Legobot will continue searching until it finds a valid timestamp, and if none is found, it uses 00:00, 1 January 1970 (UTC) which is indeed the start of Unix time. This was the right action; blocking the bot was the wrong action (see WP:BLOCK#Blocking bots, there is no evidence that the bot was not operating as intended). Other bots and scripts behave similarly: GIGO applies here. --Redrose64 🌹 (talk) 18:36, 23 April 2019 (UTC)
@Redrose64, I blocked the bot because it was malfunctioning. It is no part of the bot's purpose to move a just-open MFD to the backlog space. I was not aware of the cause of the malfunction, and the block was a way of making sure that the problem stopped while diagnosis was made and fixes applied. Once the problem was identified and fixed, unblocking was of course the proper next step. --BrownHairedGirl (talk) • (contribs) 19:07, 23 April 2019 (UTC)
It was not malfunctioning, it was working as intended. It couldn't find a valid timestamp. Timestamps that are not in the same format as those produced by a normal four-tilde signature are invalid. --Redrose64 🌹 (talk) 19:27, 23 April 2019 (UTC)
Are you deliberately missing the point?
It was malfunctioning by moving a just-open MFD to the backlog space. Whether the cause is in code or data, that is a malfunction.
I couldn't find the cause, so I stopped the machine pending diagnosis and repair. If I had known what the fix was, I'd have implemented it. There's no need to repeat the description of the problem with the data: BlueMoonset explained that 15 hours ago, and your repetition adds nothing. -BrownHairedGirl (talk) • (contribs) 20:07, 23 April 2019 (UTC)
I am not missing the point. The point is that if a valid timestamp is absent, you must expect that to cause difficulties. Do you deny that you removed a perfectly valid timestamp, and that Legobot only moved the nom after that edit was made? You state I couldn't find the cause - it's clear that you blocked the bot because you don't understand how it operates. That is a very bad policy. If I went around blocking people because I didn't understand why they had made their edits - or even worse, blocked somebody else because of a mistake that I had made myself, I'd be hauled up to explain my actions with the possibility of sanctions including desysop. --Redrose64 🌹 (talk) 20:49, 23 April 2019 (UTC)
Sorry, but which part of this is unclear to you: I couldn't find the cause, so I stopped the machine pending diagnosis and repair. If I had known what the fix was, I'd have implemented it.
I did NOT "block somebody". I blocked a bot, because it kept on causing the same problem. And, no, the problem was not caused by my edit. It was because another editor made a trivial formatting variation after a minor omission by me, both of which which I was unaare of.
I am not obliged to know how a bot is coded. As an admin, my responsibility was to intervene because its actions were producing undesired effects.
If it was a human editor, we would have been on the BRD cycle, discussing it. However, bots only do the B, not the RD. That's why the policy on blocking bots is different to that on blocking editors. (see WP:Blocking policy#Blocking_bots)
Anyway, if you want to call for me to be reprimanded or desysopped over this, WP:ANI is thataway. Otherwise, your stubborn missing of the point looks like a petty determination to find fault, and it is just wasting both our time.
Enough already. One more round of this, and i will open a complaint about your petty harassment.--BrownHairedGirl (talk) • (contribs) 21:43, 23 April 2019 (UTC)
The principle is GIGO. If you create a malformed MFD nomination, expect the bot that processes MFD to entirely mishandle it. No doubt, Legobot could handle it better by yelling at the people who created the malformed MFD nomination, but all the bots are in maintenance mode and lack anyone willing to make code changes that aren't unbreak nows. Legoktm (talk) 21:56, 23 April 2019 (UTC)
Once the error was detected and fixed, all was OK.
But the input was not garbage, and the MFD was not malformed. It was just formatted in a common date fmt by a editor who added it in good faith after I inadvertently omitted one "~". Neither of us had any reason to know that it would upset a bot, or that the bot would handle the non-recognition so inelegantly.
Fine, the code is as it is. But so long as it remains like that and it quirks are not advertised, then anyone in the situation I faced has to act on the information in front of them. --BrownHairedGirl (talk) • (contribs) 22:13, 23 April 2019 (UTC)

Further blank listing entries[edit]

Hi Legoktm, further to User talk:Legobot/2019#Delistings, March 2019, more of those have happened since then, the most recent being one hour ago. There's a current list at Template talk:Rfc#This is not a real RfC, it is a test. --Redrose64 🌹 (talk) 10:01, 28 April 2019 (UTC)

Broken RfC listing[edit]

@Legoktm: any idea why Talk:Anti-German sentiment#RfC: Rota is broken? Legbot does: diff - placing it on the bottom and not on top, and without any text.Icewhiz (talk) 13:21, 30 April 2019 (UTC)

Well - diff (removing any open/close tag - blockquote + ref tags) seemed to get it to copy over. Icewhiz (talk) 14:07, 30 April 2019 (UTC)

Bot creates no index[edit]

@Legoktm: I have added the following line to my talk page: {{User:HBC Archive Indexerbot/OptIn|target=User talk:MrClog/Archive index|mask=User talk:MrClog/Archive <#>|leading_zeros=0|indexhere=yes}} and created an index page with the required text (<!-- Legobot can blank this -->), but Legobot didn't create an index last time it ran. Anyone know why? Thanks. --MrClog (talk) 09:45, 30 April 2019 (UTC)

@MrClog: That bot task is mostly broken. In any case, I've created User talk:MrClog/Archive index using an alternate method that does not depend on the bot. * Pppery * survives 15:42, 11 May 2019 (UTC)

Weird posting[edit]

For example, when I placed on hold the review for Taiyō-class escort carrier it created this message for the nominator [3], indicating it had failed, which is not the case. Is it the diacritics that is causing this, as I have seen it with other articles with diacritics? Peacemaker67 (click to talk to me) 10:00, 5 May 2019 (UTC)

This is a known problem, see for example #Please add GA icon to Ānanda above. --Redrose64 🌹 (talk) 10:55, 5 May 2019 (UTC)