-
Notifications
You must be signed in to change notification settings - Fork 2.8k
fix: block downstream components when all routing predecessors produce no output #11057
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
Closed
ArzelaAscoIi
wants to merge
2
commits into
main
from
fix/pip-219-conditional-router-blocks-optional-sockets
+277
−2
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
20 changes: 20 additions & 0 deletions
20
releasenotes/notes/fix-conditional-router-blocks-optional-socket-1664aff58a1bdcbe.yaml
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,20 @@ | ||
| --- | ||
| fixes: | ||
| - | | ||
| Fixed a regression (introduced in 2.26.0 by PR #10793) where a component | ||
| downstream of a ConditionalRouter could run even when the router had taken | ||
| a different path and produced no output for that component's input socket. | ||
|
|
||
| The root cause was that the pipeline scheduler only blocked a component when | ||
| a *mandatory* (no-default) input socket was unfilled. Making | ||
| ``Agent.messages`` optional (``list[ChatMessage] | None = None``) therefore | ||
| allowed the Agent to be scheduled even when the message path had been cut | ||
| off by routing, leading to calls like ``AmazonBedrockChatGenerator`` failing | ||
| with "A conversation must start with a user message." | ||
|
|
||
| The fix adds ``is_any_connected_socket_blocked_by_routing()`` to the | ||
| scheduler (``component_checks.py``). After all senders of a non-variadic | ||
| connected socket have executed, if none of them produced an actual value, | ||
| the downstream component is marked BLOCKED regardless of whether the socket | ||
| has a default value. User-provided values (``pipeline.run(messages=[…])``) | ||
| are still respected and never trigger the block. |
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the part I'm not sure about. I'm not sure the current behavior is "wrong". It would defeat the purpose of indicating an input is optional and would be a big shift in how we treat connections in Pipelines.
Basically we would be saying that if a connection is made to the input that input becomes mandatory no matter if its optional or not.
I'm not necessarily against this change, we just need more time than a patch fix to think about this and whether this would cause other types of pipelines to break.