Jump to content

User talk:Σ

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

EIA errors encountered

[edit]

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)[reply]

(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)[reply]
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)[reply]

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

Redirect handling

[edit]

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)[reply]

(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)[reply]
Why not change it to follow redirects (or fail when the destination is a redirect)? —⁠ ⁠BarrelProof (talk) 20:56, 1 December 2024 (UTC)[reply]
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)[reply]

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

[edit]

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)[reply]

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

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

[edit]

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)[reply]

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