eternal loop when optionally branching with join component #8059
Labels
2.x
Related to Haystack v2.0
P0
Highest priority, add to the current sprint
topic:pipeline
type:bug
Something isn't working
Describe the bug
Two issues occurred during trying to use a classification pipeline in dC.
The pipeline went silently into an eternal loop -> I think this should never be possible
In dC we need a single component for each output type, so for optional branches we merge the outputs (see pipeline graph)
Though this leads the pipeline to go into an eternal loop, if in the branch which is not executed a join component is present.
The point where it starts another loop is here. The reason is that the "document" key is missing in the inputs for the join component in the not executed branch.
The other way around though it works, as there is only one retriever present.
Error message
eternal loop
Additional context
Add any other context about the problem here, like document types / preprocessing steps / settings of reader etc.
To Reproduce
test_data.zip
cc: @wochinge @sjrl @silvanocerza @shadeMe
The text was updated successfully, but these errors were encountered: