Skip to content
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

flow latency skips components if ETEF points to component without flow #60

Closed
reteprelief opened this issue Nov 19, 2016 · 1 comment
Closed
Assignees

Comments

@reteprelief
Copy link
Contributor

@reteprelief reteprelief commented Nov 19, 2016

t1.fsrc -> conn1 -> t2 -> conn2 -> t3.fsnk
t2 does not get processed.

@reteprelief reteprelief self-assigned this Nov 19, 2016
reteprelief added a commit that referenced this issue Nov 19, 2016
When traversing ETEF we did not call on the processing method for
componentInstances if the reference was not to a flowinstance.
The processing method was already able to handle both a flow instanvce
and a component instance.
@reteprelief
Copy link
Contributor Author

@reteprelief reteprelief commented Nov 19, 2016

fixed

lwrage added a commit that referenced this issue Dec 22, 2016
When traversing ETEF we did not call on the processing method for
componentInstances if the reference was not to a flowinstance.
The processing method was already able to handle both a flow instanvce
and a component instance.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.