Originally posted by Scragly:
In the cogs
extension module, there's a try: except ClientException
. The reason for the error is hardcoded, assuming that it raises only when a setup function does not exist.
Click here to view the relevant code.
Unfortunately, the same exception will also raise down the stack in bot.add_cog
when a command within the cog has a name that's already existing in commands, conflicting and raising the exception.
To avoid incorrect errors being reported/logged, and to prevent confusion during debugging, it might be best to simply remove the except ClientException
block and let it fall down into the catchall except Exception as e
block which prints the exception details as given.
Feel free to comment better suggestions, of course.
This will be something for after the migration over to GitHub, hence why it's an Issue, rather than a quick MR.