-
Notifications
You must be signed in to change notification settings - Fork 299
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 Flyte Types Upload Issues in Default Input #2907
Conversation
Signed-off-by: Future-Outlier <[email protected]>
Signed-off-by: Future-Outlier <[email protected]>
Signed-off-by: Future-Outlier <[email protected]>
Signed-off-by: Future-Outlier <[email protected]>
Signed-off-by: Future-Outlier <[email protected]>
Signed-off-by: Future-Outlier <[email protected]>
Signed-off-by: Future-Outlier <[email protected]> Co-authored-by: pingsutw <[email protected]>
Signed-off-by: Future-Outlier <[email protected]>
Signed-off-by: Future-Outlier <[email protected]>
Signed-off-by: Future-Outlier <[email protected]>
Signed-off-by: Future-Outlier <[email protected]>
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.
integration tests are failing
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #2907 +/- ##
==========================================
+ Coverage 72.80% 74.92% +2.11%
==========================================
Files 199 199
Lines 20820 20774 -46
Branches 2676 2680 +4
==========================================
+ Hits 15159 15565 +406
+ Misses 4932 4446 -486
- Partials 729 763 +34 ☔ View full report in Codecov by Sentry. |
Signed-off-by: Future-Outlier <[email protected]>
Signed-off-by: Future-Outlier <[email protected]>
Signed-off-by: Future-Outlier <[email protected]>
Signed-off-by: Future-Outlier <[email protected]>
Signed-off-by: Future-Outlier <[email protected]>
Signed-off-by: Future-Outlier <[email protected]>
Signed-off-by: Future-Outlier <[email protected]>
Signed-off-by: Future-Outlier <[email protected]>
Signed-off-by: Future-Outlier <[email protected]>
Signed-off-by: Future-Outlier <[email protected]>
Signed-off-by: Future-Outlier <[email protected]>
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.
Why we need 2 files in the test folder?
if we use pyflyte register
to the workflow file and use pyflyte run --remote
, it will trigger plan with different structure already exists.
Since the Protobuf struct one is MAP
in golang, and msgpack IDL one is Bytes
in golang.
Should we change backend code in flyte or make thie behavior the same now?
why we should?
for better user experience
Reproduce the error
- pyflyte register file.py
- pyflyte run --remote file.py wf
- FLYTE_USE_OLD_DC_FORMAT=true pyflyte run --remote file.py wf
cc @eapolinario
Let's chat about this in the next 10 hours
Signed-off-by: Future-Outlier <[email protected]>
* Fix Flyte Types Upload Issues in Default Input Signed-off-by: Future-Outlier <[email protected]> * TODO: ADD SD CASES, and flyteschema cases and run it in remote Signed-off-by: Future-Outlier <[email protected]> * nit Signed-off-by: Future-Outlier <[email protected]> * nit Signed-off-by: Future-Outlier <[email protected]> * update Signed-off-by: Future-Outlier <[email protected]> * update Signed-off-by: Future-Outlier <[email protected]> * update kevin's advice Signed-off-by: Future-Outlier <[email protected]> Co-authored-by: pingsutw <[email protected]> * lint Signed-off-by: Future-Outlier <[email protected]> * lint Signed-off-by: Future-Outlier <[email protected]> * add test_flytetypes Signed-off-by: Future-Outlier <[email protected]> * better-api Signed-off-by: Future-Outlier <[email protected]> --------- Signed-off-by: Future-Outlier <[email protected]> Co-authored-by: pingsutw <[email protected]> Signed-off-by: Katrina Rogan <[email protected]>
* Fix Flyte Types Upload Issues in Default Input Signed-off-by: Future-Outlier <[email protected]> * TODO: ADD SD CASES, and flyteschema cases and run it in remote Signed-off-by: Future-Outlier <[email protected]> * nit Signed-off-by: Future-Outlier <[email protected]> * nit Signed-off-by: Future-Outlier <[email protected]> * update Signed-off-by: Future-Outlier <[email protected]> * update Signed-off-by: Future-Outlier <[email protected]> * update kevin's advice Signed-off-by: Future-Outlier <[email protected]> Co-authored-by: pingsutw <[email protected]> * lint Signed-off-by: Future-Outlier <[email protected]> * lint Signed-off-by: Future-Outlier <[email protected]> * add test_flytetypes Signed-off-by: Future-Outlier <[email protected]> * better-api Signed-off-by: Future-Outlier <[email protected]> --------- Signed-off-by: Future-Outlier <[email protected]> Co-authored-by: pingsutw <[email protected]> Signed-off-by: 400Ping <[email protected]>
Tracking issue
flyteorg/flyte#5318
Why are the changes needed?
Before:
if we use flyte types in a dataclass as a workflow or task default inputs, it will fail to upload to remote (s3) storage.
After:
It should work.
What changes were proposed in this pull request?
push a new context (with remote access=True) to context stack in flytekit, so that when flyte types try to upload data, it will upload to remote.
Note:
How was this patch tested?
remote execution and integration test.
Setup process
Screenshots
Check all the applicable boxes
Related PRs
Docs link