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

FTA includes undeveloped in propagation event when type is not propagated #1913

Closed
reteprelief opened this issue Jul 23, 2019 · 0 comments · Fixed by #1914

Comments

@reteprelief
Copy link
Contributor

commented Jul 23, 2019

An incoming error propagation may list several error types. Only a subset may be propagated from a particular source.
When FTA does a backward trace it not should include an undeveloped event for an error type that is included in the incoming propagation (willing to accept an error type) but not in the out going propagation (the type is not propagated). The undeveloped event intends to indicate that there is no connection (propagation path), which is not the case in this scenario.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.