User talk:Σ/Archive/2020/June
 | This is an archive of past discussions with User:Σ. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Please stop archiving my posts
There was no reason to archive my question, please stop. Henryguide (talk) 18:32, 25 May 2020 (UTC) — Preceding unsigned comment added by Henryguide (talk • contribs) 18:10, 25 May 2020 (UTC)
I just realized that I was redirected to this talk page. Another contributor stated that it is up to lowercase sigmabot III and it is configured to archive threads after 40 days of inactivity. But I notice some of my questions on this thread https://en.wiki.x.io/wiki/Template_talk:Exchange_rate gets archived very quickly, why? Thank you! Henryguide (talk) 18:43, 25 May 2020 (UTC)
- I have explained this twice now, this will make a third time. Template talk:Exchange rate has its archiving configured so that Lowercase sigmabot III will archive threads that are at least 40 days old, measured from the most recent timestamp. This means that if 40 days elapses since the last time that somebody has posted to a thread, that thread becomes due for archiving. So, it was archived entirely properly. --Redrose64 🌹 (talk) 23:04, 25 May 2020 (UTC)
500 error
Traceback (most recent call last):
File "/data/project/sigma/www/python/venv/lib/python3.5/site-packages/aiomysql/connection.py", line 503, in _connect
await self._request_authentication()
File "/data/project/sigma/www/python/venv/lib/python3.5/site-packages/aiomysql/connection.py", line 785, in _request_authentication
auth_packet = await self._read_packet()
File "/data/project/sigma/www/python/venv/lib/python3.5/site-packages/aiomysql/connection.py", line 593, in _read_packet
packet.check_error()
File "/data/project/sigma/www/python/venv/lib/python3.5/site-packages/pymysql/protocol.py", line 220, in check_error
err.raise_mysql_exception(self._data)
File "/data/project/sigma/www/python/venv/lib/python3.5/site-packages/pymysql/err.py", line 109, in raise_mysql_exception
raise errorclass(errno, errval)
pymysql.err.InternalError: (1226, "User 's51469' has exceeded the 'max_user_connections' resource (current value: 10)")
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "./app.py", line 33, in inner
return func(*a, **kw)
File "./app.py", line 71, in editorinteract_py
tpl, store = EditorInteract(params)()
File "./editorinteract.py", line 28, in __call__
loop.run_until_complete(self.do_query(store.server, store.query))
File "/usr/lib/python3.5/asyncio/base_events.py", line 466, in run_until_complete
return future.result()
File "/usr/lib/python3.5/asyncio/futures.py", line 293, in result
raise self._exception
File "/usr/lib/python3.5/asyncio/tasks.py", line 241, in _step
result = coro.throw(exc)
File "./editorinteract.py", line 158, in do_query
user_edits = dict(zip(query.users, await asyncio.gather(*[get_user_edits(u) for u in query.users])))
File "/usr/lib/python3.5/asyncio/futures.py", line 380, in __iter__
yield self # This tells Task to wait for completion.
File "/usr/lib/python3.5/asyncio/tasks.py", line 304, in _wakeup
future.result()
File "/usr/lib/python3.5/asyncio/futures.py", line 293, in result
raise self._exception
File "/usr/lib/python3.5/asyncio/tasks.py", line 239, in _step
result = coro.send(None)
File "./editorinteract.py", line 154, in get_user_edits
async with sql.connect(**connect_info(server)) as conn:
File "/data/project/sigma/www/python/venv/lib/python3.5/site-packages/aiomysql/utils.py", line 48, in __aenter__
self._obj = await self._coro
File "/data/project/sigma/www/python/venv/lib/python3.5/site-packages/aiomysql/connection.py", line 75, in _connect
await conn._connect()
File "/data/project/sigma/www/python/venv/lib/python3.5/site-packages/aiomysql/connection.py", line 523, in _connect
self._host) from e
pymysql.err.OperationalError: (2003, "Can't connect to MySQL server on 'enwiki.labsdb'")
500 error
Hi Sigma, although it's working now, I'd like to bring this to your attention. Traceback (most recent call last):
File "/data/project/sigma/www/python/venv/lib/python3.5/site-packages/aiomysql/connection.py", line 503, in _connect await self._request_authentication() File "/data/project/sigma/www/python/venv/lib/python3.5/site-packages/aiomysql/connection.py", line 785, in _request_authentication auth_packet = await self._read_packet() File "/data/project/sigma/www/python/venv/lib/python3.5/site-packages/aiomysql/connection.py", line 593, in _read_packet packet.check_error() File "/data/project/sigma/www/python/venv/lib/python3.5/site-packages/pymysql/protocol.py", line 220, in check_error err.raise_mysql_exception(self._data) File "/data/project/sigma/www/python/venv/lib/python3.5/site-packages/pymysql/err.py", line 109, in raise_mysql_exception raise errorclass(errno, errval)
pymysql.err.InternalError: (1226, "User 's51469' has exceeded the 'max_user_connections' resource (current value: 10)")
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "./app.py", line 33, in inner return func(*a, **kw) File "./app.py", line 80, in usersearch_py tpl, store = UserSearch(params)() File "./usersearch.py", line 27, in __call__ loop.run_until_complete(self.do_query(store.server, store.query)) File "/usr/lib/python3.5/asyncio/base_events.py", line 466, in run_until_complete return future.result() File "/usr/lib/python3.5/asyncio/futures.py", line 293, in result raise self._exception File "/usr/lib/python3.5/asyncio/tasks.py", line 239, in _step result = coro.send(None) File "./usersearch.py", line 113, in do_query async with sql.connect(**connect_info(server)) as conn3: File "/data/project/sigma/www/python/venv/lib/python3.5/site-packages/aiomysql/utils.py", line 48, in __aenter__ self._obj = await self._coro File "/data/project/sigma/www/python/venv/lib/python3.5/site-packages/aiomysql/connection.py", line 75, in _connect await conn._connect() File "/data/project/sigma/www/python/venv/lib/python3.5/site-packages/aiomysql/connection.py", line 523, in _connect self._host) from e
pymysql.err.OperationalError: (2003, "Can't connect to MySQL server on 'enwiki.labsdb'")
Also I really appreciate your making this tool! It's been really helpful for me many times! Best, PrussianOwl (talk) 02:26, 30 May 2020 (UTC)
User:Σ/Testing facility/Archiver — sub-section selection is still broken
I've recently reported a bug. Today, the same issue manifested itself on Wikipedia talk:Glossary. I've tried archiving mostly threads from before 2010–2011, and a subsection from nowhere near where I was clicking got archived. So I had to undo it: Special:Diff/960607801. —andrybak (talk) 22:05, 3 June 2020 (UTC)
- @Andrybak: https://en.wiki.x.io/w/index.php?title=User:%CE%A3/Testing_facility/Archiver.js&diff=961742967&oldid=961742306 silly me. thank you for reporting. →Σσς. (Sigma) 04:55, 10 June 2020 (UTC)
Notification of discussion on the Admin Noticeboard
There is currently a discussion at Wikipedia:Administrators' noticeboard/Incidents regarding an issue with which you may have been involved. YborCityJohn (talk) 05:08, 11 June 2020 (UTC)
- It's just a user unfamiliar with WP:ARCHIVE and went for discuss first instead of WP:BRD. {{reply to|Can I Log In}}'s talk page! 05:37, 11 June 2020 (UTC)
- The number of times I've seen a user complain that the bot archived a thread which was still awaiting a response, when all the time the bot has been acting exactly per its design. And now, somebody took it to ANI? Really? All I can say is: RTFM - and F doesn't stand for "friendly" this time. --Redrose64 🌹 (talk) 20:13, 11 June 2020 (UTC)
Feedback request: Politics, government, and law request for comment
| Your feedback is requested at Talk:Sonia Gandhi on a request for comment. Thank you for helping out! You were randomly selected to receive this invitation from the list of subscribers. If you'd like not to receive these messages any more, you can opt out at any time by removing your name. |  |
Message delivered to you with love by Yapperbot :) Is this wrong? Contact my bot operator. Sent at 08:02, 16 June 2020 (UTC)