-
Notifications
You must be signed in to change notification settings - Fork 59
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: this is rfc, do not deploy until resolved; details in comments #172
Conversation
Codecov Report
@@ Coverage Diff @@
## master #172 +/- ##
=========================================
Coverage ? 70.28%
=========================================
Files ? 340
Lines ? 6747
Branches ? 1126
=========================================
Hits ? 4742
Misses ? 2005
Partials ? 0 Continue to review full report at Codecov.
|
Signed-off-by: Jason Porter <jason@union.ai>
ecb55bd
to
8955aab
Compare
note: deploying with caution; the believe if that it was incorrect to use meta. Signed-off-by: Jason Porter <jason@union.ai>
@jsonporter I could be wrong, but I believe this is a case of backwards-compatibility. For complex nested workflows, we may end up executing the same node multiple times. Each node execution will have a dynamically-generated id. But it will point to a node in the workflow spec by using |
@jsonporter whats the status on this one? |
## [0.25.1](http://github.com/lyft/flyteconsole/compare/v0.25.0...v0.25.1) (2021-09-13) ### Bug Fixes * show field types on json launch form ([#199](http://github.com/lyft/flyteconsole/issues/199)) ([a42b9f8](http://github.com/lyft/flyteconsole/commit/a42b9f8520fcd24dee752111e606ad9ae9bd88f5)) * this is rfc, do not deploy until resolved; details in comments ([#172](http://github.com/lyft/flyteconsole/issues/172)) ([67dd183](http://github.com/lyft/flyteconsole/commit/67dd18397caf40e350da40e0672e500eaa9f338a))
🎉 This PR is included in version 0.25.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
…172) * fix: this is rfc, do not deploy until resolved; details in comments Signed-off-by: Jason Porter <jason@union.ai> * fix: this is rfc, do not deploy until resolved; details in comments note: deploying with caution; the believe if that it was incorrect to use meta. Signed-off-by: Jason Porter <jason@union.ai>
## [0.25.1](http://github.com/lyft/flyteconsole/compare/v0.25.0...v0.25.1) (2021-09-13) ### Bug Fixes * show field types on json launch form ([#199](http://github.com/lyft/flyteconsole/issues/199)) ([a42b9f8](http://github.com/lyft/flyteconsole/commit/a42b9f8520fcd24dee752111e606ad9ae9bd88f5)) * this is rfc, do not deploy until resolved; details in comments ([#172](http://github.com/lyft/flyteconsole/issues/172)) ([67dd183](http://github.com/lyft/flyteconsole/commit/67dd18397caf40e350da40e0672e500eaa9f338a)) Signed-off-by: Jason Porter <jason@union.ai>
…172) * fix: this is rfc, do not deploy until resolved; details in comments Signed-off-by: Jason Porter <jason@union.ai> * fix: this is rfc, do not deploy until resolved; details in comments note: deploying with caution; the believe if that it was incorrect to use meta. Signed-off-by: Jason Porter <jason@union.ai>
## [0.25.1](http://github.com/lyft/flyteconsole/compare/v0.25.0...v0.25.1) (2021-09-13) ### Bug Fixes * show field types on json launch form ([#199](http://github.com/lyft/flyteconsole/issues/199)) ([a42b9f8](http://github.com/lyft/flyteconsole/commit/a42b9f8520fcd24dee752111e606ad9ae9bd88f5)) * this is rfc, do not deploy until resolved; details in comments ([#172](http://github.com/lyft/flyteconsole/issues/172)) ([67dd183](http://github.com/lyft/flyteconsole/commit/67dd18397caf40e350da40e0672e500eaa9f338a)) Signed-off-by: Jason Porter <jason@union.ai>
* feat: add workflow versions table Signed-off-by: csirius <davidtruong.dev@gmail.com> Signed-off-by: Jason Porter <jason@union.ai> * chore(release): Release 0.25.0 [skip ci] # [0.25.0](http://github.com/lyft/flyteconsole/compare/v0.24.0...v0.25.0) (2021-08-31) ### Features * add workflow versions table ([#193](http://github.com/lyft/flyteconsole/issues/193)) ([6fff87e](http://github.com/lyft/flyteconsole/commit/6fff87e40007fd15faae634eb6402045c067dd2c)) Signed-off-by: Jason Porter <jason@union.ai> * improvement: show proper error message for aborted workflows (#195) * improvement: show proper error message for aborted workflows Signed-off-by: Pianist038801 <steven@union.ai> * improvement: show abort message in the execution list Signed-off-by: Pianist038801 <steven@union.ai> Co-authored-by: Pianist038801 <steven@union.ai> Signed-off-by: Jason Porter <jason@union.ai> * Fix/versions executions gap (#197) * feat: add workflow versions table Signed-off-by: csirius <davidtruong.dev@gmail.com> * fix: space between versions and executions table Signed-off-by: csirius <davidtruong.dev@gmail.com> Signed-off-by: Jason Porter <jason@union.ai> * feat: workflow version details page Signed-off-by: csirius <davidtruong.dev@gmail.com> Signed-off-by: Jason Porter <jason@union.ai> * Pre merge checkin Signed-off-by: Jason Porter <jason@union.ai> * fix: this is rfc, do not deploy until resolved; details in comments (#172) * fix: this is rfc, do not deploy until resolved; details in comments Signed-off-by: Jason Porter <jason@union.ai> * fix: this is rfc, do not deploy until resolved; details in comments note: deploying with caution; the believe if that it was incorrect to use meta. Signed-off-by: Jason Porter <jason@union.ai> * fix: show field types on json launch form (#199) Signed-off-by: Pianist038801 <steven@union.ai> Co-authored-by: Pianist038801 <steven@union.ai> Signed-off-by: Jason Porter <jason@union.ai> * chore(release): Release 0.25.1 [skip ci] ## [0.25.1](http://github.com/lyft/flyteconsole/compare/v0.25.0...v0.25.1) (2021-09-13) ### Bug Fixes * show field types on json launch form ([#199](http://github.com/lyft/flyteconsole/issues/199)) ([a42b9f8](http://github.com/lyft/flyteconsole/commit/a42b9f8520fcd24dee752111e606ad9ae9bd88f5)) * this is rfc, do not deploy until resolved; details in comments ([#172](http://github.com/lyft/flyteconsole/issues/172)) ([67dd183](http://github.com/lyft/flyteconsole/commit/67dd18397caf40e350da40e0672e500eaa9f338a)) Signed-off-by: Jason Porter <jason@union.ai> * Minor fixes Signed-off-by: Jason Porter <jason@union.ai> * Feat/version details (#198) * feat: add workflow versions table Signed-off-by: csirius <davidtruong.dev@gmail.com> * feat: workflow version details page Signed-off-by: csirius <davidtruong.dev@gmail.com> Signed-off-by: Jason Porter <jason@union.ai> * fix: repopulate struct input fields on relaunch form (#201) Signed-off-by: Pianist038801 <steven@union.ai> Co-authored-by: Pianist038801 <steven@union.ai> Signed-off-by: Jason Porter <jason@union.ai> * Graph ux feature add legend (#196) * Checkin and merge to master Signed-off-by: Jason Porter <jason@union.ai> * fixed one more Signed-off-by: Jason Porter <jason@union.ai> * chore(release): Release 0.25.2 [skip ci] ## [0.25.2](http://github.com/lyft/flyteconsole/compare/v0.25.1...v0.25.2) (2021-09-16) ### Bug Fixes * repopulate struct input fields on relaunch form ([#201](http://github.com/lyft/flyteconsole/issues/201)) ([950e080](http://github.com/lyft/flyteconsole/commit/950e080a2c52c6294630f0ffd1410b0e45b50a8d)) Signed-off-by: Jason Porter <jason@union.ai> * final before pr Signed-off-by: Jason Porter <jason@union.ai> * Fixed issues created by bad rebase Signed-off-by: Jason Porter <jason@union.ai> * Fixed more merge issues Signed-off-by: Jason Porter <jason@union.ai> Co-authored-by: csirius <davidtruong.dev@gmail.com> Co-authored-by: flyte bot <admin@flyte.org> Co-authored-by: pianist <26953709+Pianist038801@users.noreply.github.com> Co-authored-by: Pianist038801 <steven@union.ai> Co-authored-by: csirius <85753828+csirius@users.noreply.github.com>
RFC: DO NOT DEPLOY UNTIL RESOLVED
I am working on the fix for flyteorg/flyte#1085 and have identified where the workflow breaks. This change fixes the issue (short version: id's were being used as keys but their values were truncated and thus we had duplicates) however I am new to the code base and unclear on the implications of removing this ternary. Where/why do we use
metadata
rather thanid
?Can someone with more context please take a look and help me understand if there are any edge cases I am missing here?
Type
Are all requirements met?
Tracking Issue
flyteorg/flyte#1085