-
Notifications
You must be signed in to change notification settings - Fork 672
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
Comments
@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 |
@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. |
Bug bankruptcy. |
* test * . * new rm * increment attempt after finalize, just before marking it running again * test * updating dependencies
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
Signed-off-by: Yee Hing Tong <[email protected]>
Signed-off-by: yuvraj <[email protected]>
* test * . * new rm * increment attempt after finalize, just before marking it running again * test * updating dependencies
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
Signed-off-by: Yee Hing Tong <[email protected]>
Signed-off-by: Haytham Abuelfutuh <[email protected]>
Signed-off-by: Yee Hing Tong <[email protected]>
Signed-off-by: Andrew Dye <[email protected]>
Signed-off-by: yuvraj <[email protected]>
Signed-off-by: yuvraj <[email protected]>
Signed-off-by: yuvraj <[email protected]>
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:
Likely it will be option 2.
For things like CSV list, we have to consider how to display a list of these items.
The text was updated successfully, but these errors were encountered: