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: don't skip legacy children check when isParentNode=false #111

Merged
merged 1 commit into from
Oct 22, 2020

Conversation

schottra
Copy link
Contributor

flyteorg/flyte#438

In implementing the original changes to use the isParentNode flag, I had assumed that the flag would be completely absent. But due to the way protobuf is deserialized, when the metadata object is present, isParentNode will default to false. This will cause us to incorrectly skip checking for children on legacy node executions by querying the child TaskExecutions first.

So, the logic is now to query directly for child node executions if the flag is true, and fall back to the legacy check otherwise.

Copy link
Contributor

@EngHabu EngHabu left a comment

Choose a reason for hiding this comment

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

Thank you!

@service-github-lyft-semantic-release
Copy link
Contributor

🎉 This PR is included in version 0.15.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

@schottra schottra deleted the fix-parent-node-issue branch December 4, 2020 20:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants