errbot | Errbot is a chatbot , a daemon | Chat library

It means that:

1. Somewhere in your code you have an except ... statement where the exception ... (or one of the exceptions in the sequence ...) is not a subclass of BaseException, and
2. An exception is being thrown that is caught by that except ... statement.

The TypeError can be raised only when an exception is actually thrown because the names you give to except ... must be evaluated for their current values at that time; just because TypeError referenced a particular class at one point in the program's execution doesn't mean it won't be changed later to reference another object (though that would be admittedly perverse).

The Python interpreter should be giving you a full traceback of the exception; the first thing you need to do is find this. It could be occurring in one of two situations. (This is for single-threaded programs; I'm assuming your program is not multithreaded.)

1. During the execution of your program, in which case the program will be terminated by the exception, or
2. During finalization of objects (in their __del__(self) functions) in which case the error will be printed to stderr.

In both cases there should be a stack trace, not just the error message; I've confirmed that at least on Python ≥3.4 a stack trace is printed out for case 2.

You then need to follow this stack trace to see where the problem lies. Remember that the names you give to except ... are variables (even things like TypeError) that can be reassigned, so that you could conceivably be dealing with a (perverse) situation like:

You need to send the config command with the json config, here errbot just tells you what you need to do to configure it.

send_card does not return to you the message it sends which means you will have to do something to get the message info of the card you sent.

One option would be to trigger a callback for all messages in your plugin, inspect the message, and add your reaction there:

Another option could be to use the slack backend api call method to search for your message and add the reaction that way.

My solution feels a bit hacky but it works. If anyone has a more elegant solution please share. I'll accept my own answer after awhile if there are no additional responses.

So I've come across this before but I guess I still wasn't familiar enough with how patching works in Python with knowing where to patch. After reading the "Where to patch" documentation ( again :) ) I have a work-around given the dynamic imports with errbot.

An errbot project folder will look something

subprocess.call does not return the output of the command, but returns returncode of the process. You need to use other functions like subprocess.check_output:

rejected by strategy 'SpecificBackendLocator' is a misleading warning from yapsy saying that a plugin is not what it is looking at the moment while looping over all the plugins, it is a normal behavior.

The entry you are getting for core is {}, empty. Simply your Errbot instance has not store anything yet there.

For example check out this session:

The source of this error happens in the verify function which verifies the certificate is valid in terms of hostname and validity date.

The value of XMPP_CA_CERT_FILE set in errbot's config is eventually passed to ca_certs in the XMLStream class where it's used to influence the cert_policy. That sets ssl.CERT_NONE but even so, it still calls verify.

That means currently you can have a (possible self-signed) certificate without a valid trust root, but you will still have to ensure the hostname you're connecting to matches the hostname (CN) of the certificate. (This is something which SleekXMPP, the underlying XMPP library used by errbot imposes on us and not directly something from errbot itself).

Be sure that your system is configured for UTF-8.

If you run under Linux for example, try the command locale to check your current encoding.