This repository has been archived by the owner on Oct 9, 2023. It is now read-only.
Releases: flyteorg/flyteplugins
Releases · flyteorg/flyteplugins
Add missing log links for AWS Batch
Add missing sub-task log links (#62) * Add missing sub-task log links * PR Comments * Update deps * Only update stdlib * Unit tests
Fetch whether task is interruptible from taskMetaData
This flag will enable usage of spot instances in k8s clusters.
Replace lower-cased sidecar gpu resource with nvidia one
v0.3.11 Replace lower-cased sidecar gpu resource with nvidia one (#65)
Spark plugin: Scala Support
Merge pull request #63 from lyft/spark-scala-class Bug: Scala Requires Both MainApplicationFile and MainClass to be Set
Fairness V0 in resource manager: adding support for project-level and namespace-level cap
Merge pull request #56 from lyft/fairness-namespace-cap Fairness in resource manager: adding support for project-level and namespace-level cap
bumping up the flyteidl version
v0.3.8 bumping up the flyteidl version (#61)
Distinguish system failures from user
Use system failure for node deletion or infra level issues (#59) * Use system failure for node deletion or infra level issues * using version * removing PhaseSystemRetryableFailure * code review feedback * fixing a test * idl version * reverting tests
Fix AWS Batch CPU Scale
Fix AWS Batch CPU Scale (#60) * Fix AWS Batch CPU Scale * PR Comments
Abort AWS Jobs on Finalize()
Abort AWS Batch Job on Finalize (#58) 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
Fix for Batch timeouts
v0.3.4 Fix empty timeout (#57)