Closed traumschule closed 5 years ago
Add
exclude = find_updates
to your config file (probably ~/.sopel/default.cfg)
That helped, thanks! Fun fact: i can't reproduce it anymore now.
diff --git a/sopel/modules/find_updates.py b/sopel/modules/find_updates.py
index 300571d..f68feb2 100644
--- a/sopel/modules/find_updates.py
+++ b/sopel/modules/find_updates.py
@@ -38,7 +38,11 @@ def startup_version_check(bot, trigger):
@sopel.module.interval(wait_time)
def check_version(bot):
- version = sopel.version_info
+ try
+ version = sopel.version_info
+ except Eception as e:
+ stderr('Error: check_version failed. Add this to the core section of
+~/.sopel/default.cfg:\nexclude = find_updates')
It seems the error has been worked around. Feel free to come back if the issue reoccurs!
For obvious reasons, bugs caused by changes made in a fork—such as "tor-ifying" the bot—can't be considered bugs in Sopel proper, so I'll close this. :smile_cat:
Most likely it was a connection problem to sopel.chat from one of the tor exit nodes
Glad to be your first tor user, it's my first contact to sopel. Always confusing when typical issues are not caught properly and the log spits unclear error. See above patch as welcome present. :)
Hi! I am running a torified version of sopel HEAD on our inspIRCd and get following error:
It joined a channel, ping timeouted and rejoined, so it is working in principle but the error happens after every reconnect. The failing line is