Skip to content
This repository has been archived by the owner on Oct 3, 2024. It is now read-only.

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

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

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

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

Comments

@reteprelief
Copy link
Contributor

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
@reteprelief
Fixes issue #60
5c390f1 
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

fixed

lwrage pushed a commit that referenced this issue Dec 22, 2016
@reteprelief @lwrage
Fixes issue #60
aaabcea 
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 subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@reteprelief reteprelief

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@reteprelief