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

fix(sdk): fix NamedTuple output with Dict/List bug #8316

Merged

Conversation

connor-mccarthy
Copy link
Member

Description of your changes:
Fixes a bug where a component with a NamedTuple output with a Dict
data type would fail to compile.

Checklist:

@google-oss-prow
Copy link

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@connor-mccarthy connor-mccarthy changed the title fix(sdk): fix NamedTuple output with struct bug fix(sdk): fix NamedTuple output with Dict/List bug Sep 27, 2022
@connor-mccarthy connor-mccarthy force-pushed the fix-namedtuple-output-bug branch from fa60711 to 7b4393d Compare September 27, 2022 23:04
@connor-mccarthy connor-mccarthy marked this pull request as ready for review September 27, 2022 23:05
@connor-mccarthy
Copy link
Member Author

/retest

return {text: text}

# TODO: ideally should be the canonical type string, rather than the specific annotation as string, but both work
self.assertEqual(comp.component_spec.outputs['Output'].type,
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

NIT: Should it be comp.component_spec.output instead of comp.component_spec.outputs['Output']?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In this case it should not be.

This is different than the data passing syntax used within a pipeline definition. This is checking the in-memory representation of the component, wherein all outputs (OutputSpecs) are included in the dictionary .outputs, irrespective of how many outputs there are.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Got it, thank you for the explanation!

@zijianjoy
Copy link
Collaborator

/lgtm

@zijianjoy
Copy link
Collaborator

/approve

@google-oss-prow
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: zijianjoy

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@google-oss-prow google-oss-prow bot merged commit 26f1fe4 into kubeflow:master Sep 28, 2022
jlyaoyuli pushed a commit to jlyaoyuli/pipelines that referenced this pull request Jan 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants