You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 30, 2024. It is now read-only.
It would be nice if, when a module load fails, kitnbot replied with the reason attached to the ImportError. (I can write this myself, just posting an issue since I'm not going to get around to it right now.)
The text was updated successfully, but these errors were encountered:
Hm. I think the current behavior (correct me if I'm wrong) is to output the error to the log, but not say anything in any channels? The reasoning being that we don't want to leak details of bot code to the general public, so the log is a "better" place for that - debugging details belong there, not in IRC channels.
That said, it wouldn't be all that hard to add an option e.g. to the admintools module which code could toggle to have it spit out module log failures into IRC somewhere.
Oh hm, no - upon further examination of the code, it looks like we swallow the ImportError even in the logs right now. Yeah, that can probably be changed. ImportErrors are sometimes notoriously misleading, but even some info is better than none.
It would be nice if, when a module load fails, kitnbot replied with the reason attached to the ImportError. (I can write this myself, just posting an issue since I'm not going to get around to it right now.)
The text was updated successfully, but these errors were encountered: