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

[BUG][Flytekit] Calling NamedTuple field on Promise isn't working as expected in Python 3.9 #1153

Closed
samhita-alla opened this issue Jun 16, 2021 · 0 comments
Labels
bug Something isn't working flytekit FlyteKit Python related issue python-3.9+ Capture bugs that affect flytekit for versions greater than python3.9 untriaged This issues has not yet been looked at by the Maintainers

Comments

@samhita-alla
Copy link
Contributor

Describe the bug
The test test_single_named_output_subwf() in tests/flytekit/unit/core/test_composition.py is resulting in an error: AttributeError: 'Promise' object has no attribute 'sub_int'

Expected behavior
No error is expected to pop up.

To Reproduce
Steps to reproduce the behavior:

  1. Define a NamedTuple.
  2. Call NamedTuple field on a Promise object.
@samhita-alla samhita-alla added bug Something isn't working untriaged This issues has not yet been looked at by the Maintainers python-3.9+ Capture bugs that affect flytekit for versions greater than python3.9 labels Jun 16, 2021
@samhita-alla samhita-alla changed the title [Flytekit] Calling NamedTuple field on Promise isn't working as expected in Python 3.9 [BUG][Flytekit] Calling NamedTuple field on Promise isn't working as expected in Python 3.9 Jun 18, 2021
@wild-endeavor wild-endeavor added the flytekit FlyteKit Python related issue label Jul 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working flytekit FlyteKit Python related issue python-3.9+ Capture bugs that affect flytekit for versions greater than python3.9 untriaged This issues has not yet been looked at by the Maintainers
Projects
None yet
Development

No branches or pull requests

2 participants