User talk:Σ

I do not check my talk page. If you need to reach me, leave a message here AND send a copy to me via email.

---

The lowercase sigmabots and my Toolforge services are still running, but are unmaintained. In the event of crashes/outages/errors, note that aside from myself, User:0xDeadbeef, User:The Earwig, and User:APerson also have administrative access and can troubleshoot.

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.

Learn how to type "Σ".

Archives (Index)

2009/June 2011/April 2011/March 2011/May 2011/June 2011/July 2011/August 2011/September 2011/October 2011/November 2011/December 2012/January 2012/February 2012/March 2012/April 2012/May 2012/June 2012/July 2012/August 2012/September 2012/October 2012/November 2012/December 2013/January 2013/February 2013/March 2013/April 2013/May 2013/June 2013/July 2013/August 2013/September 2013/October 2013/November 2013/December 2014/January 2014/February 2014/March 2014/April 2014/May 2014/June 2014/July 2014/August 2014/September 2014/October 2014/November 2014/December 2015/January 2015/February 2015/March 2015/April 2015/May 2015/June 2015/July 2015/August 2015/September 2015/October 2015/November 2015/December 2016/January 2016/February 2016/April 2016/May 2016/June 2016/July 2016/August 2016/September 2016/October 2016/November 2016/December 2017/January 2017/February 2017/March 2017/April 2017/May 2017/June 2017/July 2017/August 2017/October 2017/November 2017/December 2018/January 2018/February 2018/March 2018/April 2018/May 2018/June 2018/July 2018/August 2018/September 2018/October 2018/November 2018/December 2019/January 2019/February 2019/March 2019/April 2019/May 2019/June 2019/July 2019/August 2019/September 2019/October 2019/November 2019/December 2020/January 2020/February 2020/March 2020/April 2020/May 2020/June 2020/July 2020/August 2020/September 2020/October 2020/November 2020/December 2021/January 2021/February 2021/March 2021/April 2021/May 2021/June 2021/July 2021/August 2021/September 2021/October 2021/November 2021/December 2022/January 2022/February 2022/March 2022/April 2022/May 2022/June 2022/July 2022/August 2022/September 2022/October 2022/November 2022/December 2023/January 2023/February 2023/March 2023/April 2023/May 2023/June 2023/July 2023/August 2023/September 2023/October 2023/November 2023/December 2024/January 2024/February 2024/March 2024/April 2024/May 2024/June 2024/July 2024/August 2024/September 2024/October 2024/November 2024/December

This page is archived by ClueBot III.

EIA errors encountered

See below:

Traceback (most recent call last):
 File "/layers/heroku_python/dependencies/lib/python3.12/site-packages/aiomysql/connection.py", line 527, in _connect
   self._reader, self._writer = await \
                                ^^^^^^^
 File "/layers/heroku_python/python/lib/python3.12/asyncio/tasks.py", line 520, in wait_for
   return await fut
          ^^^^^^^^^
 File "/layers/heroku_python/dependencies/lib/python3.12/site-packages/aiomysql/connection.py", line 88, in _open_connection
   transport, _ = await loop.create_connection(
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 File "/layers/heroku_python/python/lib/python3.12/asyncio/base_events.py", line 1077, in create_connection
   infos = await self._ensure_resolved(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 File "/layers/heroku_python/python/lib/python3.12/asyncio/base_events.py", line 1453, in _ensure_resolved
   return await loop.getaddrinfo(host, port, family=family, type=type,
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 File "/layers/heroku_python/python/lib/python3.12/asyncio/base_events.py", line 898, in getaddrinfo
   return await self.run_in_executor(
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^
 File "/layers/heroku_python/python/lib/python3.12/concurrent/futures/thread.py", line 58, in run
   result = self.fn(*self.args, **self.kwargs)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 File "/layers/heroku_python/python/lib/python3.12/socket.py", line 963, in getaddrinfo
   for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
socket.gaierror: [Errno -3] Temporary failure in name resolution

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
 File "/workspace/app.py", line 33, in inner
   return func(*a, **kw)
          ^^^^^^^^^^^^^^
 File "/workspace/app.py", line 71, in editorinteract_py
   tpl, store = EditorInteract(params)()
                ^^^^^^^^^^^^^^^^^^^^^^^^
 File "/workspace/editorinteract.py", line 28, in __call__
   loop.run_until_complete(self.do_query(store.server, store.query))
 File "/layers/heroku_python/python/lib/python3.12/asyncio/base_events.py", line 684, in run_until_complete
   return future.result()
          ^^^^^^^^^^^^^^^
 File "/workspace/editorinteract.py", line 157, in do_query
   user_edits = dict(zip(query.users, await asyncio.gather(*[get_user_edits(u, pool) for u in query.users])))
                                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 File "/workspace/editorinteract.py", line 151, in get_user_edits
   async with p.acquire() as conn:
 File "/layers/heroku_python/dependencies/lib/python3.12/site-packages/aiomysql/utils.py", line 134, in __aenter__
   self._conn = await self._coro
                ^^^^^^^^^^^^^^^^
 File "/layers/heroku_python/dependencies/lib/python3.12/site-packages/aiomysql/pool.py", line 142, in _acquire
   await self._fill_free_pool(True)
 File "/layers/heroku_python/dependencies/lib/python3.12/site-packages/aiomysql/pool.py", line 195, in _fill_free_pool
   conn = await connect(echo=self._echo, loop=self._loop,
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 File "/layers/heroku_python/dependencies/lib/python3.12/site-packages/aiomysql/connection.py", line 75, in _connect
   await conn._connect()
 File "/layers/heroku_python/dependencies/lib/python3.12/site-packages/aiomysql/connection.py", line 563, in _connect
   raise OperationalError(
pymysql.err.OperationalError: (2003, "Can't connect to MySQL server on 'enwiki.analytics.db.svc.wikimedia.cloud'") 

The Kip ^(contribs) 08:04, 26 November 2024 (UTC)

(talk page watcher) @The Kip: This is probably related to ongoing problems with Toolforge. See e.g. phab:T380827. --Redrose64 🌹 (talk) 08:29, 26 November 2024 (UTC)

Another Editor Interaction Error

URL that produced the error

The text in the report

500 You shouldn't be seeing this page. Please report this to User:Σ on enwp. Include the current URL and the text below in your report. If you do not include this information, then there is nothing I can do to help. Traceback (most recent call last): File "/layers/heroku_python/dependencies/lib/python3.12/site-packages/aiomysql/connection.py", line 527, in _connect self._reader, self._writer = await \ ^^^^^^^ File "/layers/heroku_python/python/lib/python3.12/asyncio/tasks.py", line 520, in wait_for return await fut ^^^^^^^^^ File "/layers/heroku_python/dependencies/lib/python3.12/site-packages/aiomysql/connection.py", line 88, in _open_connection transport, _ = await loop.create_connection( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/layers/heroku_python/python/lib/python3.12/asyncio/base_events.py", line 1077, in create_connection infos = await self._ensure_resolved( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/layers/heroku_python/python/lib/python3.12/asyncio/base_events.py", line 1453, in _ensure_resolved return await loop.getaddrinfo(host, port, family=family, type=type, ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/layers/heroku_python/python/lib/python3.12/asyncio/base_events.py", line 898, in getaddrinfo return await self.run_in_executor( ^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/layers/heroku_python/python/lib/python3.12/concurrent/futures/thread.py", line 58, in run result = self.fn(*self.args, **self.kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/layers/heroku_python/python/lib/python3.12/socket.py", line 963, in getaddrinfo for res in _socket.getaddrinfo(host, port, family, type, proto, flags): ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ socket.gaierror: [Errno -3] Temporary failure in name resolution The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/workspace/app.py", line 33, in inner return func(*a, **kw) ^^^^^^^^^^^^^^ File "/workspace/app.py", line 71, in editorinteract_py tpl, store = EditorInteract(params)() ^^^^^^^^^^^^^^^^^^^^^^^^ File "/workspace/editorinteract.py", line 28, in __call__ loop.run_until_complete(self.do_query(store.server, store.query)) File "/layers/heroku_python/python/lib/python3.12/asyncio/base_events.py", line 684, in run_until_complete return future.result() ^^^^^^^^^^^^^^^ File "/workspace/editorinteract.py", line 140, in do_query async with sql.connect(**connect_info(server)) as conn: File "/layers/heroku_python/dependencies/lib/python3.12/site-packages/aiomysql/utils.py", line 74, in __aenter__ self._obj = await self._coro ^^^^^^^^^^^^^^^^ File "/layers/heroku_python/dependencies/lib/python3.12/site-packages/aiomysql/connection.py", line 75, in _connect await conn._connect() File "/layers/heroku_python/dependencies/lib/python3.12/site-packages/aiomysql/connection.py", line 563, in _connect raise OperationalError( pymysql.err.OperationalError: (2003, "Can't connect to MySQL server on 'enwiki.analytics.db.svc.wikimedia.cloud'")

-- Toddy1 (talk) 09:13, 26 November 2024 (UTC)

The URL is now working with no errors.-- Toddy1 (talk) 12:22, 26 November 2024 (UTC)

Redirect handling

There seems to be a bug (or let's say an interesting behavior) in the way the bot handles the situation when the archive destination is a redirect. See the discussion at Talk:Assisted suicide § Archive mix-up and the edit history of Talk:Assisted suicide/Archive 2. In that case, the archive destination name was a redirect, but the bot has been appending discussions below the redirect instead of following the redirect and appending the discussions to its destination. This created a situation in which the archived discussions became basically invisible to readers since anyone trying to look at what was in the archive was summarily redirected somewhere else. —⁠ ⁠BarrelProof (talk) 19:38, 1 December 2024 (UTC)

(talk page watcher) @BarrelProof: Ever since lowercase sigmabot III took over archiving from the MiszaBots (and possibly before that), it has been the case that the value of the |archive= parameter is taken literally, apart from the replacement of variables - redirects have never been followed. This is indirectly addressed at User:Lowercase sigmabot III/Archive HowTo#Parameters explained, which says the target page must be a subpage of the current page. This is one of the reasons why it is important to move subpages along with the main page. --Redrose64 🌹 (talk) 20:48, 1 December 2024 (UTC)

Why not change it to follow redirects (or fail when the destination is a redirect)? —⁠ ⁠BarrelProof (talk) 20:56, 1 December 2024 (UTC)

I can't answer that question for Σ, but judging by Special:Contributions/Σ they are unlikely to answer any time soon, and even less likely to do anything to alter how the bot operates. But I would imagine that it's some kind of safeguard, against the malicious conversion of a valid archive into a redirect to somewhere totally other. --Redrose64 🌹 (talk) 22:52, 1 December 2024 (UTC)

More guidance on how to install a bot like this one using Forge

I tried my best (a few days ago) and after about an hour of trying to get all of this setup I couldn't manage. Any help? :) L.E. Rainer 18:41, 11 December 2024 (UTC)

You don't state which page this was on. --Redrose64 🌹 (talk) 22:06, 11 December 2024 (UTC)

Searchable archive banner not appearing on some article talk pages with MiszaBot

Some article talk pages with recently archived content via MiszaBot are not displaying the searchable archive banner that is displayed on most other talk pages. Here is a talk page without the archive displayed. What formatting will enable the archive banner to appear on the talk page? Thanks. Llll5032 (talk) 20:23, 18 December 2024 (UTC)

Redrose64, would you know the answer? Llll5032 (talk) 20:25, 19 December 2024 (UTC)

Finding when the template is set too aggressive

I have seen that sometimes people will set the minimum number of threads to leave as "0" (zero). When this happens it will tag sigma bot's edit as "Manual revert" and the talk page will usually be blank. These edits can be found by searching the bot's edits in the Talk space and adding the tag for manual reverts.[1]

This is also a good predictor for cases when some of the other bot settings are out of proportion. Wizmut (talk) 14:24, 24 December 2024 (UTC)