-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Fix: Fix Pipeline.run() running components with only defaults in the wrong order #7426
Conversation
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.
LGTM (also, we did this in a pair-programming fashion)
Pull Request Test Coverage Report for Build 8438251670Warning: This coverage report may be inaccurate.This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.
Details
💛 - Coveralls |
This broke something 😢 |
…wrong order (#7426) * Fix Pipeline.run() running components with only defaults in the wrong order * Add release notes
Related Issues
Proposed Changes:
Changes the behaviour of
Pipeline.run()
to treat Components that have only default inputs the same way we treat Component with Variadic that are marked as lazy. This is done only when trying to remove Components from the internalwaiting_for_input
queue.How did you test it?
I added a new unit test and verified other weren't breaking.
Notes for the reviewer
N/A
Checklist
fix:
,feat:
,build:
,chore:
,ci:
,docs:
,style:
,refactor:
,perf:
,test:
.