25bb86d2d0
The refactoring that we did a couple weeks ago to make the zephyr mirror script restart itself automatically (by splitting it into zephyr_mirror.py and zephyr_mirror_backend.py) had a poor interaction with our code for killing old zephyr_mirror processes (to prevent double-mirroring). If you manually ran two copies of the outer mirroring script (zephyr_mirror.py), then the second one would on startup kill the first one's zephyr_mirror_backend.py children (for being duplicate zephyr_mirror_backend.py processes that would result in double-mirroring). However, importantly, it did not kill the first mirroring script's zephyr_mirror.py parent process, so the first mirroring script would then proceed to startup up new children. The process then repeats, with the two scripts' roles reversed. This issue didn't affect the sharded mirroring case, where I had been doing the testing of the kill code with that refactoring, because we don't have a version of the outer zephyr_mirror.py loop for that situation (a consequence of it being hard to restart the threads properly with the run_parallel API that we're using to spawn all the children). (imported from commit d4886ac77312a6b0ebd0d612f6fb084970bf23a2) |
||
---|---|---|
bin | ||
bots | ||
examples | ||
__init__.py | ||
humbug.py | ||
README |
#### Dependencies The Humbug API Python bindings require the following Python libraries: * simplejson * requests (version >= 0.12) #### Using the API For now, the only fully supported API operation is sending a message. The other API queries work, but are under active development, so please make sure we know you're using them so that we can notify you as we make any changes to them. The easiest way to use these API bindings is to base your tools off of the example tools under api/examples in this distribution. If you place your API key in `~/.humbugrc` the Python API bindings will automatically read it in. The format of the config file is as follows: [api] key=<api key from the web interface> email=<your email address> You can obtain your Humbug API key from the Humbug settings page. A typical simple bot sending API messages will look as follows: At the top of the file: # Make sure the Humbug API distribution's root directory is in sys.path, then: import humbug humbug_client = humbug.Client(email="your_email@example.com") When you want to send a message: message = { "type": "stream", "to": ["support"], "subject": "your subject", "content": "your content", } humbug_client.send_message(message) Additional examples: client.send_message({'type': 'stream', 'content': 'Humbug rules!', 'subject': 'feedback', 'to': ['support']}) client.send_message({'type': 'private', 'content': 'Humbug rules!', 'to': ['user1@example.com', 'user2@example.com']}) send_message() returns a dict guaranteed to contain the following keys: msg, result. For successful calls, result will be "success" and msg will be the empty string. On error, result will be "error" and msg will describe what went wrong. #### Sending messages You can use the included `api/bin/humbug-send` script to send messages via the API directly from existing scripts. humbug-send hamlet@example.com cordelia@example.com -m \ "Conscience doth make cowards of us all."