-
Notifications
You must be signed in to change notification settings - Fork 1
Issues: mpi-sws-rse/datablox
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Want an engage call to shutdown/kill a block and its dependencies
Next milestone
#71
opened May 29, 2012 by
jfischer
Figure out efficient handling of local packages
Current milestone
#70
opened May 28, 2012 by
jfischer
Need a way to pass configuration parameters from datablox topology files to engage
Next milestone
#66
opened May 3, 2012 by
jfischer
Fix gunicorn deployment to listen on preferred network
Current milestone
#65
opened May 3, 2012 by
jfischer
Need to support multiple shards per node when running under Engage
Next milestone
#61
opened Apr 26, 2012 by
jfischer
If an output port has no connections, block should not send messages
#56
opened Apr 20, 2012 by
jfischer
Need better error message when referring to a non-existant block
#55
opened Apr 20, 2012 by
jfischer
Consider using pyzmq's serializers for sending and receiving data
#35
opened Jan 20, 2012 by
t-saideep
ProTip!
no:milestone will show everything without a milestone.