User talk:Σ/Archive/2024/February

Race condition deleted comment

Number 57 made this comment at 15:38:43. At 15:38:51, Lowercase sigmabot III archived AN, and in the process deleted Number 57's comment. If this were something where the race condition spanned only a few milliseconds, I might not say anything, but 8 seconds is a pretty long window to run into this sort of issue. Could some post-archiving double-check be run, maybe? -- Tamzin^{[cetacean needed]} (they|xe|she) 19:27, 6 January 2024 (UTC)

Archiving in the context of a page that uses level-one headings as dividers

 Courtesy link: WT:Help desk § Proposal to change archiving at Help Desk to stale + <interval>
 Related info: User_talk:Scsbot § Hasty_archiving

Hi, Σ. I have a proposal outstanding at the WP:Help desk requesting that the archiving method be changed there in order to archive discussions only after they have gone stale. (Current method: archive a discussion N days after it began, using Scsbot.) Normally, this is something easily done by Sigmabot, however a possible complicating factor is that the Help desk page groups discussions using level-one headers of the form, =January 9= with all discussions begun on January 9 appearing as level-two headings under it.

My understanding of Sigmabot workings is limited to pages that have level-two headings as the highest level, such as article talk pages and project pages like ANI; on those pages the level-two discussion is highest and considered atomic, so that subsections (level-three and beyond) are not separated from their main topic when archived, and either the entire level-two discussion is archived, or none of it is, and this is, of course, the desired behavior. But I'm not sure if Sigmabot can handle level-one headers differently, such as used at Help desk. Is there an ability to basically ignore level one currently, or could you add a new param to either ignore level one specifically, or maybe ignore whatever the top level is? Or how about something like, param |atomic=2 which defines an archivable unit as the level-two heading, with the default being '2' if not otherwise specified? That would default pretty much everywhere to current behavior, and cause an instant "fix" to any talk page that uses dates or other things as level-one dividers or containers that hold separately archivable discussions. (As a side-benefit, |atomic=3, for example, would allow them to have level one=year, level two=month, with archivable discussions starting at level three.) Thanks, Mathglot (talk) 19:46, 9 January 2024 (UTC)

Error with

Hello from France. I like your tool but it doesn't work anymore... Here's what it gives me (currrent url : https://sigma.toolforge.org/created.py?name=Sg7438&server=frwiki&max=500&startdate=&ns=%2C+%2C&redirects=none) + text => Traceback (most recent call last):

 File "/workspace/app.py", line 33, in inner
   return func(*a, **kw)
          ^^^^^^^^^^^^^^
 File "/workspace/app.py", line 63, in created_py
   return tpl.render(store=store)
          ^^^^^^^^^^^^^^^^^^^^^^^
 File "/layers/heroku_python/dependencies/lib/python3.12/site-packages/mako/template.py", line 462, in render
   return runtime._render(self, self.callable_, args, data)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 File "/layers/heroku_python/dependencies/lib/python3.12/site-packages/mako/runtime.py", line 837, in _render
   _render_context(template, callable_, context, *args,
 File "/layers/heroku_python/dependencies/lib/python3.12/site-packages/mako/runtime.py", line 873, in _render_context
   _exec_template(inherit, lclcontext, args=args, kwargs=kwargs)
 File "/layers/heroku_python/dependencies/lib/python3.12/site-packages/mako/runtime.py", line 899, in _exec_template
   callable_(context, *args, **kwargs)
 File "created_query_mako", line 49, in render_body
 File "/workspace/created.py", line 135, in fix_results
   urls, ts, stamp, diffword, histword, sizetag, minor, page, summ, top = self.contrib_line(args)
                                                                          ^^^^^^^^^^^^^^^^^^^^^^^
 File "/workspace/tool.py", line 102, in contrib_line
   stamp = ch_locale(store.lang, ts.strftime, [fmt])
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 File "/workspace/localeshit.py", line 38, in ch_locale
   raise err

locale.Error: unsupported locale setting

Would you have a solution ? (I use your tool to easily find articles created with the description heading)... Thank you! Sg7438 (talk) 15:40, 11 January 2024 (UTC)

Hello, same error here (which shows if needed be that this tool is invaluable :-)). Here's the URL & text, just in case: https://sigma.toolforge.org/created.py?name=LmaltierBot&server=frwiktionary&max=500&startdate=&ns=,+,&redirects=none

and text:

Text of the error reported by Automatik

Traceback (most recent call last): File "/workspace/app.py", line 33, in inner return func(*a, **kw) ^^^^^^^^^^^^^^ File "/workspace/app.py", line 63, in created_py return tpl.render(store=store) ^^^^^^^^^^^^^^^^^^^^^^^ File "/layers/heroku_python/dependencies/lib/python3.12/site-packages/mako/template.py", line 462, in render return runtime._render(self, self.callable_, args, data) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/layers/heroku_python/dependencies/lib/python3.12/site-packages/mako/runtime.py", line 837, in _render _render_context(template, callable_, context, *args, File "/layers/heroku_python/dependencies/lib/python3.12/site-packages/mako/runtime.py", line 873, in _render_context _exec_template(inherit, lclcontext, args=args, kwargs=kwargs) File "/layers/heroku_python/dependencies/lib/python3.12/site-packages/mako/runtime.py", line 899, in _exec_template callable_(context, *args, **kwargs) File "created_query_mako", line 49, in render_body File "/workspace/created.py", line 135, in fix_results urls, ts, stamp, diffword, histword, sizetag, minor, page, summ, top = self.contrib_line(args) ^^^^^^^^^^^^^^^^^^^^^^^ File "/workspace/tool.py", line 102, in contrib_line stamp = ch_locale(store.lang, ts.strftime, [fmt]) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/workspace/localeshit.py", line 38, in ch_locale raise err locale.Error: unsupported locale setting

Automatik (talk) 17:16, 12 January 2024 (UTC)

Hi Sg7438 and Automatik, this issue should be fixed now. — The Earwig (talk) 04:36, 15 January 2024 (UTC)

Yes, many thanks for the repair: this tool is very useful to me... It allows me to easily find a created article among my 232551 created...

have a nice day! Sg7438 (talk) 10:47, 15 January 2024 (UTC)

Archiving comment on the page sensitivity analysis

Hi Maybe I am doing something wrong - why are you removing my comment from the page talk of sensitivity analysis? I think it is a genuine suggestion of improvement. Please help. Andrea Saltelli Saltean (talk) 17:22, 12 January 2024 (UTC)

Archiving my comment on the page Sensitivity analysis

Dear Σ, since you archived again my comment, could you kindly explain me what was wrong with my comment on the sensitivity analysis page? Did I violate some rule or was my comment inappropriate? Thanks for your help. Andrea Saltelli Saltean (talk) 17:28, 12 January 2024 (UTC)

(talk page watcher) @Saltean: You refer, presumably, to Talk:Sensitivity analysis. Please note that when querying edits, whether made by a human or by a bot, you must always state which page(s) are involved, and ideally, which edits are problematic.

Σ has not edited that page. However, their bot, which is lowercase sigmabot III (talk · contribs), has done so, with two recent edits: (i) and (ii). These were perfectly legitimate archiving edits, the thread being moved to Talk:Sensitivity analysis/Archive 1 in accordance with the archiving instructions at the top of the page (put simply, threads older than sixty days may be archived). You undid those two edits, but did not touch the archives - if you restore an archived thread to the main talk page, you *must* also remove it from the archive, otherwise you get duplicate threads.

Bots (such as lowercase sigmabot III) do not archive threads based upon whether they were "inappropriate" or not - they are incapable of making such judgement. The selection for archiving is based purely upon the most recent timestamp found in the thread, which in this case was 10:20, 25 August 2020 (UTC) - so the thread is effectively much more than sixty days old.

The root of the problem is that this edit adds two section headings but only one section ends with a signature. I am going to attempt to fix up the mess that you have caused, please do not blame Σ for something that is not at all their fault. --Redrose64 🌹 (talk) 23:39, 12 January 2024 (UTC)

Reply from Andrea Saltelli Thanks a lot User:Redrose64, please accept my apologies for the extra work, and in any case no blame whatsoever from my side, only my confusion due to my inexperience. I still do not understand why there is an old timestamp on the comment I inserted a few days ago, hope to learn to do better along the way. Saltean (talk) 07:01, 13 January 2024 (UTC)

A barnstar for you!

	The Technical Barnstar
	Thank you for your service Elvisisalive95 (talk) 21:07, 31 January 2024 (UTC)

Why?

Why does your bot archive this issue? The user has not addressed the issue caused by his bot and the issue hasn't been solved!!! --Sb008 (talk) 20:16, 15 February 2024 (UTC)

(talk page watcher) @Sb008: User talk:Cyberpower678 has

{{User:MiszaBot/config|archiveheader={{Talk archive navigation}}{{User:Cyberpower678/Layout}}|maxarchivesize=70K|counter=82|minthreadsleft=0|minthreadstoarchive=1|algo=old(3d)|archive=User talk:Cyberpower678/Archive %(counter)d
}}

near the top; these are the archiving instructions for lowercase sigmabot III. Here, the |algo=old(3d) instructs the bot to archive any thread which has not been posted to for more than three days, counted from the most recent timestamp in the thread. Lowercase sigmabot III does not know (and indeed cannot know) whether an issue has been addressed or not; it goes solely by timestamps. In this case the most recent timestamp was 10:42, 12 February 2024 (UTC); three days on from that is 10:42, 15 February 2024 (UTC), and archiving occurred at 18:22, 15 February 2024 (UTC) - more than seven hours after it became eligible for archiving. The bot is working as designed. --Redrose64 🌹 (talk) 08:50, 16 February 2024 (UTC)