-
Notifications
You must be signed in to change notification settings - Fork 57
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
feat: Fetch Node Executions directly if possible #109
Conversation
Codecov Report
@@ Coverage Diff @@
## master #109 +/- ##
==========================================
+ Coverage 69.37% 70.04% +0.67%
==========================================
Files 383 383
Lines 6299 6337 +38
Branches 986 997 +11
==========================================
+ Hits 4370 4439 +69
+ Misses 1929 1898 -31
Continue to review full report at Codecov.
|
# [0.14.0](http://github.com/lyft/flyteconsole/compare/v0.13.2...v0.14.0) (2020-10-20) ### Features * Fetch Node Executions directly if possible ([#109](http://github.com/lyft/flyteconsole/issues/109)) ([c740b83](http://github.com/lyft/flyteconsole/commit/c740b83c08b0d9da94c3b54d88481fb5817cd71c))
🎉 This PR is included in version 0.14.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
flyteorg/flyte#438
This builds on the work from flyteorg/flyteadmin#111 to directly query NodeExecution children for NodeExecutions which use the new
isParent
flag. Most of the work was in theuseChildNodeExecutions
anduseExecutionDataCache
hooks to use the right logic for building a query for the node_executions endpoint.