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

Allow download of Inputs / Outputs #58

Closed
georgesnelling opened this issue Nov 19, 2019 · 3 comments
Closed

Allow download of Inputs / Outputs #58

georgesnelling opened this issue Nov 19, 2019 · 3 comments
Labels
ui Admin console user interface

Comments

@georgesnelling
Copy link
Contributor

georgesnelling commented Nov 19, 2019

It's unclear exactly what format things should be in, but for I/O types like CSV/Blob/Schema we should be able to provide a download link for the user.

Options:

  1. Convert it to a signed S3 link. This is probably not the right move because we need to verify the identity of a user before allowing them to download
  2. Convert the s3:// protocol to an actual s3 link. It would be up to the user to ensure they are assuming the correct role to be able to download the file.

Likely it will be option 2.

For things like CSV list, we have to consider how to display a list of these items.

@kumare3
Copy link
Contributor

kumare3 commented Jul 6, 2020

@schottra I think there are a lot of tasks assigned to you. Can you go over them once and let me know where you can use help. Also having a UX link for most of them would be great

@schottra
Copy link
Contributor

schottra commented Jul 6, 2020

@kumare3 This item doesn't have any UX design or mocks other than the thoughts listed in the description. I'm open to ideas for a good experience.

Pretty much anything that others want to pick up is fine with me. The things marked "pri1" would need discussion first, since those are mostly major feature efforts.

@schottra schottra added ui Admin console user interface and removed pri3 labels Jul 6, 2020
@schottra schottra removed their assignment Jul 6, 2020
@EngHabu
Copy link
Contributor

EngHabu commented Jan 29, 2021

Bug bankruptcy.

@EngHabu EngHabu closed this as completed Jan 29, 2021
eapolinario pushed a commit to eapolinario/flyte that referenced this issue Dec 6, 2022
* test

* .

* new rm

* increment attempt after finalize, just before marking it running again

* test

* updating dependencies
eapolinario pushed a commit to eapolinario/flyte that referenced this issue Dec 20, 2022
AWS Batch Plugin can determine that a task has failed if it detects it can no longer satisfy the failure ratio requirement. When this happens the array task node will be terminated then retried (if there are retry count available). This should trigger a cancellation to the AWS Job as well. 

It was originally written this way to match the old version of this code that, upon discussion, has been deemed a bad design. 

- [X] Need to ensure the cancellation API is idempotent (or add error check/ignore if it's not)
         Validated by running a Workflow and waiting for it to kick off an AWS Job then aborting it. That ended up calling Abort() then Finalize() and the second call was no-op
eapolinario pushed a commit to eapolinario/flyte that referenced this issue Dec 20, 2022
eapolinario pushed a commit to eapolinario/flyte that referenced this issue Dec 20, 2022
eapolinario pushed a commit to eapolinario/flyte that referenced this issue Dec 20, 2022
eapolinario pushed a commit to eapolinario/flyte that referenced this issue Aug 9, 2023
* test

* .

* new rm

* increment attempt after finalize, just before marking it running again

* test

* updating dependencies
eapolinario pushed a commit to eapolinario/flyte that referenced this issue Aug 21, 2023
AWS Batch Plugin can determine that a task has failed if it detects it can no longer satisfy the failure ratio requirement. When this happens the array task node will be terminated then retried (if there are retry count available). This should trigger a cancellation to the AWS Job as well. 

It was originally written this way to match the old version of this code that, upon discussion, has been deemed a bad design. 

- [X] Need to ensure the cancellation API is idempotent (or add error check/ignore if it's not)
         Validated by running a Workflow and waiting for it to kick off an AWS Job then aborting it. That ended up calling Abort() then Finalize() and the second call was no-op
eapolinario pushed a commit to eapolinario/flyte that referenced this issue Aug 21, 2023
eapolinario pushed a commit to eapolinario/flyte that referenced this issue Aug 21, 2023
eapolinario pushed a commit to eapolinario/flyte that referenced this issue Aug 21, 2023
eapolinario pushed a commit that referenced this issue Sep 7, 2023
pmahindrakar-oss pushed a commit that referenced this issue Feb 5, 2024
eapolinario pushed a commit to eapolinario/flyte that referenced this issue Apr 30, 2024
austin362667 pushed a commit to austin362667/flyte that referenced this issue May 7, 2024
robert-ulbrich-mercedes-benz pushed a commit to robert-ulbrich-mercedes-benz/flyte that referenced this issue Jul 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ui Admin console user interface
Projects
None yet
Development

No branches or pull requests

4 participants