User talk:Legobot
Not all RFCs work very well with the vagarities of formatting that are needed to avoid breaking the list pages. I suggest you make it so that something like {{rfc|topic|summary=Some text goes here.}} has the bot use the "Some text goes here." as the summary in the list rather than trying to copy up to the first timestamp, so we don't have to have editors who care more about the list than the RFC itself reformatting things in ways that make the RFC formatting worse. Anomie⚔ 23:49, 10 July 2024 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"20240710234900","author":"Anomie","type":"comment","level":1,"id":"c-Anomie-20240710234900-Feature_request:_Allow_supplying_a_custom_summary_for_when_the_bot_copying_the_f","replies":["c-Anomie-20240711010100-Anomie-20240710234900"]}}-->
- Ha, I found a workaround after looking at the bot's code. The bot takes everything between the
{{rfc}} and the first timestamp, lightly munges it, and dumps it into {{rfcquote|text=}} . One thing it doesn't do is escape pipes, so something like this {{rfc|topic|rfcid=XYZ}}
<div style="display:none">|text=
This text is hidden on the RFC page, but is shown on the listing. 00:00 11 July 2024 (UTC)
</div>
results in the listing page having this:{{rfcquote|text=
<div style="display:none">|text=
This text is hidden on the RFC page, but is shown on the listing. 00:00 11 July 2024 (UTC)}}
The second |text= parameter overrides the first, effectively removing the div so the text displays properly on the listing page. Anomie⚔ 01:01, 11 July 2024 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"20240711010100","author":"Anomie","type":"comment","level":2,"id":"c-Anomie-20240711010100-Anomie-20240710234900","replies":[]}}-->
Hi Legoktm. Doesn't look like the bot has run at WP:MFD since the 17th—maybe you could have a look? Extraordinary Writ (talk) 20:26, 26 July 2024 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"20240726202600","author":"Extraordinary Writ","type":"comment","level":1,"id":"c-Extraordinary_Writ-20240726202600-Task_33_stopped","replies":["c-Extraordinary_Writ-20240730034700-Extraordinary_Writ-20240726202600","c-Legoktm-20240730050200-Extraordinary_Writ-20240726202600"]}}-->
- Now working again. Extraordinary Writ (talk) 03:47, 30 July 2024 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"20240730034700","author":"Extraordinary Writ","type":"comment","level":2,"id":"c-Extraordinary_Writ-20240730034700-Extraordinary_Writ-20240726202600","replies":[]}}-->
- So it had gotten stuck...
tools.legobot@tools-bastion-13:~$ kubectl get pods
NAME READY STATUS RESTARTS AGE
mfd-rs-28686902-62fkh 1/1 Running 0 11d
- I fixed that.
- And then when I ran it manually, it was hitting some error with Wikipedia:Miscellany for deletion/User:Valjean/Archive 32, and I didn't have time to finish investigating (I suspect the notavote template threw it off somehow?)...but I guess it fixed itself? Yay? Legoktm (talk) 05:02, 30 July 2024 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"20240730050200","author":"Legoktm","type":"comment","level":2,"id":"c-Legoktm-20240730050200-Extraordinary_Writ-20240726202600","replies":[]}}-->
I relisted Wikipedia:Miscellany for deletion/User:TalkSubject a couple days ago, but the bot has not moved it to the new day (based on the technical timestamp, e.g. {{mfdr}}). Does the bot still perform this function? — Godsy (TALKCONT) 21:51, 7 August 2024 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"20240807215100","author":"Godsy","type":"comment","level":1,"id":"c-Godsy-20240807215100-Miscellany_for_Deletion_relisting","replies":[]}}-->
I am thrilled to see Legobot fixing Linter errors again! I have fixed Linter errors in many thousands of pages with the edit summary "Leaving obsolete tags for bots" when the font tags were too intricate for my regex skills. I am sure that the bot will be able to fix many of my leave-behinds.
There is a very common (maybe 300,000 instances) missing div tag that the bot may be able to fix. If you go to Wikipedia:Linter/Signature submissions and look for "WelcomeMenu", you will see a description of the condition. – Jonesey95 (talk) 13:20, 1 October 2024 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"20241001132000","author":"Jonesey95","type":"comment","level":1,"id":"c-Jonesey95-20241001132000-Thrilled","replies":["c-Legoktm-20241004163100-Jonesey95-20241001132000"]}}-->
- :) Yay! I've set it up to run once a week, so it should regularly pick up new pages to fix. I'll take a look at that page after WikiConference North America finishes. Legoktm (talk) 16:31, 4 October 2024 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"20241004163100","author":"Legoktm","type":"comment","level":2,"id":"c-Legoktm-20241004163100-Jonesey95-20241001132000","replies":[]}}-->
@Legoktm: User:Legobot added the same RFC ID to two different RFCs at Talk:Conservative Party of British Columbia (see [1] and [2]), posted only one of the two RFCs on the same article talk page at Wikipedia:Requests for comment/Politics, government, and law (see [3]), and listed only one of the two RFCs at Wikipedia:Dashboard/Requests for comment (see [4]). Would deeply appreciate it if you could fix this. PoliticalPoint (talk) 06:01, 17 October 2024 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"20241017060100","author":"PoliticalPoint","type":"comment","level":1,"id":"c-PoliticalPoint-20241017060100-Issues_with_two_requests_for_comment_on_the_same_article_talk_page","replies":["c-Redrose64-20241017084100-PoliticalPoint-20241017060100"]}}-->
- (talk page watcher) @PoliticalPoint: This is covered by WP:RFC#Multiple simultaneous RfCs on one page and I partially fixed it like this; you need to wait until Legobot next visits at around 09:00 (UTC) for the rest of the fix. --Redrose64 🌹 (talk) 08:41, 17 October 2024 (UTC)[reply]__DTELLIPSISBUTTON__{"threadItem":{"timestamp":"20241017084100","author":"Redrose64","type":"comment","level":2,"id":"c-Redrose64-20241017084100-PoliticalPoint-20241017060100","replies":[]}}-->
|
|