Right now participants can only react to incoming packets. This means a participant that starts sending immediately can't be done in msgflo-python

Needed for https://github.com/c-base/farbgeber

This leaves services hanging

From #1 it seems our tests don't fail when exceptions are raised, significantly reducing their usefulness

In Nodejs or noflo I can register the prticipant under the name. But in python How to register the participant

msgflo-nodejs --name repeater ./node_modules/msgflo-nodejs/examples/Repeat.coffee

Here I registered the participant under the "repeater" name. So I can send message to repeater.IN in mqtt. But how to do that for msgflo-python?

I'm following the example here -> https://github.com/msgflo/msgflo-python

Kindly help me on this. Thanks in advance :)

Currently msgflo-python fails if payloads can't be serialized as JSON:

Traceback (most recent call last):
  File "/home/bergie/.local/lib/python2.7/site-packages/gevent/greenlet.py", line 536, in run
    result = self._run(*self.args, **self.kwargs)
  File "/home/bergie/Projects/c-base/farbgeber/farbgeber.py", line 107, in loop
    self.send_palette(palette)
  File "/home/bergie/Projects/c-base/farbgeber/farbgeber.py", line 128, in send_palette
    self.send('palette', palette)
  File "/home/bergie/.local/lib/python2.7/site-packages/msgflo/msgflo.py", line 54, in send
    self._engine._send(outport, outdata)
  File "/home/bergie/.local/lib/python2.7/site-packages/msgflo/msgflo.py", line 234, in _send
    serialized = json.dumps(data)
  File "/usr/lib/python2.7/json/__init__.py", line 243, in dumps
    return _default_encoder.encode(obj)
  File "/usr/lib/python2.7/json/encoder.py", line 207, in encode
    chunks = self.iterencode(o, _one_shot=True)
  File "/usr/lib/python2.7/json/encoder.py", line 270, in iterencode
    return _iterencode(o, 0)
  File "/usr/lib/python2.7/json/encoder.py", line 184, in default
    raise TypeError(repr(o) + " is not JSON serializable")
TypeError: <Color #cc5d00> is not JSON serializable

Version 0.10.24 of msgflo just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As msgflo is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Right now Engine.add_participant() will overwrite previous reference.

There should also be some convenience for easily setting up multiple participant in same process, at least using the API.

To be useful in real-life deployment scenarios should be on PyPi so one can just pip install msgflo.
Deployment should be done automatically by Travis CI on tags (after passing tests). http://docs.travis-ci.com/user/deployment/pypi/

Not covered by tests now. Especially important is proper ACK/NACK handling, and other things which can cause subsequent messages to fail

Refs #1

Right now only AMQP supported

Just like noflo-runtime-msgflo, would be great to support initial information packets for msgflo-python

msgflo-python doesn't send a discovery message if participant has no inports

gevent 1.1alpha2 apparently supports it. Might need work in Haigha though

Tests must run both Py 2 and Py 3