Skip to content

Issues: flowbased/fbp-protocol

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.

Sign up for GitHub

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

12 Open 17 Closed
12 Open 17 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Migrate schema to AsyncAPI
#88 opened Oct 1, 2020 by bergie
Runtime protocol: send list of supported component languages enhancement
#57 opened Mar 29, 2018 by bergie 0.8
Runner doesn't work on Windows bug
#29 opened Jan 10, 2017 by bergie
Feature request: Add generic metadata field to components enhancement
#26 opened Oct 23, 2016 by jomeier
Feature Request: Add a graph:list command enhancement
#25 opened Oct 15, 2016 by jomeier
3
Ensure existing clients/runtime are in compliance with schemas
#22 opened Jun 22, 2016 by jonnor
2 of 8 tasks
Support for embedded subgraphs enhancement
#20 opened Jun 18, 2016 by chadrik
6
tests: use schemas to validate messages enhancement
#14 opened May 24, 2016 by chadrik
1
Protocol: "network output" and "network error" messages does not contain graph bug
#9 opened May 18, 2016 by bergie
FBP protocol for values on port should allow human readable names enhancement
#8 opened May 18, 2016 by bergie
1
component:getsource should have testslanguage enhancement
#6 opened Jan 6, 2016 by jonnor 0.8
fbp-test: node/edge metadata should be optional bug
#3 opened Apr 15, 2015 by jonnor
1
ProTip! Follow long discussions with comments:>50.