User talk:Σ/Archive/2024/August

Editor interaction bug report

At [1] I got the following error message, which I am sharing with you because it told me to:

Extended content

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 "/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 540, in _connect await self._request_authentication() File "/layers/heroku_python/dependencies/lib/python3.12/site-packages/aiomysql/connection.py", line 844, in _request_authentication auth_packet = await self._read_packet() ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/layers/heroku_python/dependencies/lib/python3.12/site-packages/aiomysql/connection.py", line 652, in _read_packet packet.raise_for_error() File "/layers/heroku_python/dependencies/lib/python3.12/site-packages/pymysql/protocol.py", line 221, in raise_for_error err.raise_mysql_exception(self._data) File "/layers/heroku_python/dependencies/lib/python3.12/site-packages/pymysql/err.py", line 143, in raise_mysql_exception raise errorclass(errno, errval) pymysql.err.OperationalError: (1226, "User 's51469' has exceeded the 'max_user_connections' resource (current value: 10)")

JBL (talk) 00:42, 29 July 2024 (UTC)

Not archiving as it should

The bot is only archiving certain important pages, and seems to be only operating between 12:00 and 13:00 (UTC). ~~ AirshipJungleman29 (talk) 13:07, 3 August 2024 (UTC)

@AirshipJungleman29: lowercase sigmabot III has never operated continuously, it only runs at certain times of day. I notice that it has archived at least 24 pages after 13:00 (UTC) today. But which pages do you think should have been archived, but weren't? Examples always help: it might be a simple case of there being no threads that are eligible for archiving. --Redrose64 🌹 (talk) 13:43, 3 August 2024 (UTC)

Seems to have fixed itself, or maybe TheEarwig gave it a kick, but some sections have not been archived on my talk that should have been according to the parameters. ~~ AirshipJungleman29 (talk) 14:25, 3 August 2024 (UTC)

There are four threads where the most recent timestamp is more than 10 days ago:

• User talk:AirshipJungleman29#GA-related discussion – 18:41, 22 July 2024 (UTC)
• User talk:AirshipJungleman29#About that recent addition to DYKG – 23:51, 22 July 2024 (UTC)
• User talk:AirshipJungleman29#Prep 3 Image – 18:02, 23 July 2024 (UTC)
• User talk:AirshipJungleman29#Siege of Baghdad – 01:14, 24 July 2024 (UTC)

The oldest of these became eligible at 18:41, 1 August 2024 (UTC). lowercase sigmabot III has not visited your talk page since 20:22, 31 July 2024 (UTC), at which point none of those threads were eligible. Next time that it visits, those four threads should be archived. --Redrose64 🌹 (talk) 15:00, 3 August 2024 (UTC)

The point was that it only archived 26 pages on 2 August, when at least two of the above threads and untold others on other pages were eligible to be archived. ~~ AirshipJungleman29 (talk) 16:14, 3 August 2024 (UTC)

@AirshipJungleman29: Well, they're archived now, plus one more. Case closed, I think. --Redrose64 🌹 (talk) 21:59, 4 August 2024 (UTC)

Moving archived talks

Bumping a discussion from elsewhere which touches on sigmabot. Tule-hog (talk) 20:10, 3 August 2024 (UTC)