Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
[flytepropeller][flyteadmin] Streaming Decks V2 #6053
[flytepropeller][flyteadmin] Streaming Decks V2 #6053
Changes from 13 commits
54aa165
9ed6b6e
4b4f6bd
dd774cb
0bb8e91
25fea29
4e24e91
8d1d0e4
31853bb
4068043
65b6efe
137579f
04f7fbc
aa56d64
a16851f
7314455
19498f5
74f595f
3bd3336
f6d8493
4b56e52
db4b19e
2737251
564dc5f
69ba94e
c992eae
0b91b5c
1d18265
96500c1
dd9dbaa
f51ff8c
bd5e682
561a43c
a33ba09
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Check warning on line 88 in flytepropeller/pkg/controller/nodes/task/handler.go
Codecov / codecov/patch
flytepropeller/pkg/controller/nodes/task/handler.go#L81-L88
Check warning on line 90 in flytepropeller/pkg/controller/nodes/task/handler.go
Codecov / codecov/patch
flytepropeller/pkg/controller/nodes/task/handler.go#L90
Check warning on line 98 in flytepropeller/pkg/controller/nodes/task/handler.go
Codecov / codecov/patch
flytepropeller/pkg/controller/nodes/task/handler.go#L96-L98
Check warning on line 104 in flytepropeller/pkg/controller/nodes/task/handler.go
Codecov / codecov/patch
flytepropeller/pkg/controller/nodes/task/handler.go#L102-L104
Check warning on line 113 in flytepropeller/pkg/controller/nodes/task/handler.go
Codecov / codecov/patch
flytepropeller/pkg/controller/nodes/task/handler.go#L111-L113
Check warning on line 118 in flytepropeller/pkg/controller/nodes/task/handler.go
Codecov / codecov/patch
flytepropeller/pkg/controller/nodes/task/handler.go#L118
Check warning on line 121 in flytepropeller/pkg/controller/nodes/task/handler.go
Codecov / codecov/patch
flytepropeller/pkg/controller/nodes/task/handler.go#L121
Check warning on line 195 in flytepropeller/pkg/controller/nodes/task/handler.go
Codecov / codecov/patch
flytepropeller/pkg/controller/nodes/task/handler.go#L193-L195
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Better comments!
cc @wild-endeavor
Check warning on line 448 in flytepropeller/pkg/controller/nodes/task/handler.go
Codecov / codecov/patch
flytepropeller/pkg/controller/nodes/task/handler.go#L447-L448
Check warning on line 452 in flytepropeller/pkg/controller/nodes/task/handler.go
Codecov / codecov/patch
flytepropeller/pkg/controller/nodes/task/handler.go#L451-L452
Check warning on line 548 in flytepropeller/pkg/controller/nodes/task/handler.go
Codecov / codecov/patch
flytepropeller/pkg/controller/nodes/task/handler.go#L547-L548
Check warning on line 551 in flytepropeller/pkg/controller/nodes/task/handler.go
Codecov / codecov/patch
flytepropeller/pkg/controller/nodes/task/handler.go#L550-L551
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't we always check if the file exists in the terminal state? if flytekit fails to generate a deck for some reasons, we should not add deck_uri to the output info, right
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What are the concerns with having a
deck_uri
set in the event?flyteconsole
will still make the call to ensure that the file exists before showing the final deck, no?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi, @eapolinario
Yes, but FlyteConsole currently needs to make an additional call to check if the task is in a terminal phase.
I think it's better to handle all the logic in Propeller, as this would make maintenance easier. It would also simplify FlyteConsole's implementation.
In summary:
We should keep as much backend logic in the backend as possible. This approach reduces the maintenance burden on FlyteConsole and improves the readability of the backend code.
Check warning on line 560 in flytepropeller/pkg/controller/nodes/task/handler.go
Codecov / codecov/patch
flytepropeller/pkg/controller/nodes/task/handler.go#L559-L560
Check warning on line 610 in flytepropeller/pkg/controller/nodes/task/handler.go
Codecov / codecov/patch
flytepropeller/pkg/controller/nodes/task/handler.go#L604-L610