User talk:Σ
 | I do not check this page regularly. If you have a message that requires my attention, write it both here and in an email. |
 | I cannot help with issues about archiving your own talk page. If you have read the documentation carefully and are still having problems, a prompt and friendly answer can usually be found by asking at the teahouse. |
 |
|
sigmabot III creating duplicate archive sections[edit]
See Wikipedia talk:Administrators' noticeboard § Duplicated sections in AN archives. Bot is creating duplicated messages in noticeboard archives. — AP 499D25 (talk) 07:55, 9 March 2024 (UTC)
- Per Primefac's reply there, this looks like the bot is behaving as expected. — The Earwig (talk) 05:59, 17 March 2024 (UTC)
The Dispute Resolution Noticeboard has not been archived since 13 March 2024, and closed cases are cluttering it. I see that the bot is archiving article talk pages and user talk pages, so that the bot is not down, but has stopped archiving DRN. Is there something that I should do to restart archiving, or is the bot taking a vacation, or what? Robert McClenon (talk) 04:02, 19 March 2024 (UTC)
- The bot is definitely running in WP space, so it's something specific to that page. Most obvious: are there threads eligible for archiving? I presume yes. Is there something unusual about the format of a thread that means that the page cannot be processed? --Redrose64 🌹 (talk) 09:07, 19 March 2024 (UTC)
- User:Redrose64 - Thank you for the comment. Yes, I see that it is archiving other noticeboards. One thing that happened on 14 March 2024 is that I unarchived a thread to DRN, and put a Do Not Archive Until tag in the recovered thread. I have done that before, and I don't recall it confusing the bot or stopping the archival process, but there are always details involved. Is there some way to determine which of the threads is the one that is confusing the bot? Robert McClenon (talk) 19:56, 19 March 2024 (UTC)
- It's archived 11 DRN threads today. --Redrose64 🌹 (talk) 21:54, 19 March 2024 (UTC)
- User:Redrose64 - Yes. I tweaked one of the dates in one of the closed cases, and it started working again. Robert McClenon (talk) 15:49, 25 March 2024 (UTC)
- It's archived 11 DRN threads today. --Redrose64 🌹 (talk) 21:54, 19 March 2024 (UTC)
- User:Redrose64 - Thank you for the comment. Yes, I see that it is archiving other noticeboards. One thing that happened on 14 March 2024 is that I unarchived a thread to DRN, and put a Do Not Archive Until tag in the recovered thread. I have done that before, and I don't recall it confusing the bot or stopping the archival process, but there are always details involved. Is there some way to determine which of the threads is the one that is confusing the bot? Robert McClenon (talk) 19:56, 19 March 2024 (UTC)
"7.9" listed at Redirects for discussion[edit]
The redirect 7.9 has been listed at redirects for discussion to determine whether its use and function meets the redirect guidelines. Anyone, including you, is welcome to comment on this redirect at Wikipedia:Redirects for discussion/Log/2024 March 29 § 7.9 until a consensus is reached. Trovatore (talk) 16:31, 29 March 2024 (UTC)
Edit summary search[edit]
I found the tool works and will be very useful in reporting work done by my bot at WP:URLREQ. Thank you for making and maintaining it.
I noticed it is a little fiddly on date ranges. Specifying the same date for start and end does not work: 20240411-20240411. Nor does a two-date range: 20240410-20240411. It only works when setting a 3 date range: 20240410-20240412, even though local time is April 11 UTC at the time of the search, and all the edits were made on the 11. I suspect this might be because when no hour/min/sec is specified it defaults to the earliest, the first minute/sec of the day ie. midnight. It would be more intuitive if it defaulted to the start of the day when in the start date field, and defaults to the end of the day in the end date field. That way users don't need to worry about entering minutes and seconds, only need to think in terms of days. Of course if they want more granularity they can enter minutes/sec to override the default. -- GreenC 16:22, 11 April 2024 (UTC)
- (talk page watcher) @GreenC: If you start the tool without pre-filled date information, you'll see that the two input boxes for dates contain the placeholder text "YYYYMMDDHHMMSS". This indicates that they allow timestamps down to one second; in the absence of a time, the HHMMSS part defaults to 000000 (midnight). Therefore,
&enddate=20240411&startdate=20240411is shorthand for&enddate=20240411000000&startdate=20240411000000and since the two times are the same, it's extremely unlikely to pick up anything at all - it's uncommon that an edit occurs at precisely midnight. Try 20240411000000-20240411235959 although this might not pick up edits made in the last second before midnight. --Redrose64 🌹 (talk) 17:45, 11 April 2024 (UTC)