Repository navigation
Conversation
Contributor
Author
|
Just a clarification. The above currently prints: where it should print: |
Contributor
Author
|
I have this crazy thought... Would this problem persist if the whole noflo is implemented asynchronously? Say: In the current implementation, 'SomeInitial' is sent to A and then sent to B immediately. If data flow is async, wouldn't B setting up be run before 'SomeInitial' is passed to it, making the ports to be available for attachment between A and B? |
Contributor
Author
|
See #42 |
Member
|
Thanks for the PR! I'm mostly offline this week in Istanbul, so I'll be able to look at these in details next week |
Member
|
@kenhkan sorry about taking my time with these. This pull req doesn't apply cleanly any longer, unfortunately. Can you rebase and push so it gets updated? |
8000
Contributor
Author
AsherBond
pushed a commit
to AsherBond/noflo
that referenced
this pull request
Oct 12, 2026
Update cli-color to version 1.1.0 🚀
bergie
added a commit
that referenced
this pull request
Nov 7, 2026
toDOT and graph --format dot (work document #41 item 1)
AsherBond
pushed a commit
to AsherBond/noflo
that referenced
this pull request
Nov 11, 2026
@noflo/graph gains toDOT(): renders the canonical graph document as a deterministic Graphviz digraph — nodes labeled with their components, port-to-port edge labels, IIPs as note-shaped nodes, exports as dashed boundary nodes, groups as clusters, quotes and backslashes escaped. The fbp-client CLI's graph command accepts --format dot. The stored- trace retrieval item stays gated: the 0x34/0x35 vocabulary does not exist in @noflo/fbp-protocol yet.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When sending to a subgraph, the same IP is sent to the subgraph the same number of times as how many processes are attached to an open ArrayPort. Something like:
subgraph.fbp:
main_graph.fbp:
The above should print:
This seems to be due to using ArrayPort-to-ArrayPort attachment to make a link between the graph and the subgraph. Sending the IP only to the first socket solves the problem as all the sockets point to the same process in the subgraph anyway.