1 new commit pushed to

<https://github.com/flyteorg/flyteconsole/tree/master|master>

by jsonporter

<https://github.com/flyteorg/flyteconsole/commit/ce3216e2196edd0370f182447299011edad90ad7|ce3216e2>

- fix: package version to 1.4.2 (#700) flyteorg/flyteconsole

1 new commit pushed to

<https://github.com/flyteorg/flytekit/tree/master|master>

by eapolinario

<https://github.com/flyteorg/flytekit/commit/8ccb5dde044f9dce3e216a8cea58dd464fb3ab6b|8ccb5dde>

- Revert "Make flytekit comply with PEP-561 (#1516)" (#1532) flyteorg/flytekit

#3398 Update swagger.rst Pull request opened by eapolinario Tracking issue #3350 Describe your changes We no longer ship the redoc container in the sandbox, so let's remove mentions to that in the docs. Check all the applicable boxes ☐ I updated the documentation accordingly. ☐ All new and existing tests passed. ☐ All commits are signed-off. Screenshots Note to reviewers flyteorg/flyte ✅ All checks have passed 6/6 successful checks

#1533 windows tests Pull request opened by wild-endeavor wip flyteorg/flytekit GitHub Actions: build-plugins (3.8, flytekit-ray) GitHub Actions: build-plugins (3.8, flytekit-polars) GitHub Actions: build-plugins (3.8, flytekit-papermill) GitHub Actions: build-plugins (3.8, flytekit-pandera) GitHub Actions: build-plugins (3.8, flytekit-onnx-scikitlearn) GitHub Actions: build-plugins (3.8, flytekit-onnx-pytorch) GitHub Actions: build-plugins (3.8, flytekit-modin) GitHub Actions: build-plugins (3.8, flytekit-kf-tensorflow) GitHub Actions: build-plugins (3.8, flytekit-kf-pytorch) GitHub Actions: build-plugins (3.8, flytekit-kf-mpi) GitHub Actions: build-plugins (3.8, flytekit-k8s-pod) GitHub Actions: build-plugins (3.8, flytekit-hive) GitHub Actions: build-plugins (3.8, flytekit-greatexpectations) GitHub Actions: build-plugins (3.8, flytekit-duckdb) GitHub Actions: build-plugins (3.8, flytekit-dolt) GitHub Actions: build-plugins (3.8, flytekit-deck-standard) GitHub Actions: build-plugins (3.8, flytekit-dbt) GitHub Actions: build-plugins (3.8, flytekit-data-fsspec) GitHub Actions: build-plugins (3.8, flytekit-dask) GitHub Actions: build-plugins (3.8, flytekit-bigquery) GitHub Actions: build-plugins (3.8, flytekit-aws-sagemaker) GitHub Actions: build-plugins (3.8, flytekit-aws-batch) GitHub Actions: build-plugins (3.8, flytekit-aws-athena) GitHub Actions: docs GitHub Actions: build (windows-latest, 3.9) GitHub Actions: build (windows-latest, 3.8) GitHub Actions: build (ubuntu-latest, 3.10) GitHub Actions: build (ubuntu-latest, 3.9) GitHub Actions: build (ubuntu-latest, 3.8) GitHub Actions: lint ✅ No checks have passed 0/30 successful checks

#3399 [BUG] Validate update calls for setting task resource attributes Issue created by katrogan Describe the bug Setting the task resource attributes for a project with {"project":"foo","domain":"development","limits":{"cpu":"4096","memory":"8Ti"}} causes flyteadmin to panic on resolving task resource attributes at create execution time We shouldn't accept invalid configs or handle partial task resource attributes overrides gracefully Expected behavior Admin should not panic at create execution time for invalid or partial task resource attributes Additional context to reproduce No response Screenshots No response Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte

#701 fix: project settings dashbboard tests Pull request opened by 4nalog TL;DR • fix: project settings dashboard tests failing on domain settings component Type ☑︎ Bug Fix ☐ Feature ☐ Plugin Are all requirements met? ☑︎ Code completed ☑︎ Smoke tested ☐ Unit tests added ☐ Code documentation added ☐ Any pending items have an associated Issue Tracking Issue NA Follow-up issue NA flyteorg/flyteconsole Codecov: 66.92% (-0.26%) compared to 3c5d6e8 Codecov: 38.18% of diff hit (target 67.18%) GitHub Actions: Build Flyteconsole Image / Push to Github Registry ✅ 5 other checks have passed 5/8 successful checks

1 new commit pushed to

<https://github.com/flyteorg/flyteconsole/tree/master|master>

by jsonporter

<https://github.com/flyteorg/flyteconsole/commit/b15470b74ce27d739decfb559726de90bc37616d|b15470b7>

- fix: project settings dashbboard tests (#701) flyteorg/flyteconsole

#702 fix: revert node version Pull request opened by ursucarina TL;DR Reverts codebase node version Type ☑︎ Bug Fix ☐ Feature ☐ Plugin Are all requirements met? ☑︎ Code completed ☑︎ Smoke tested ☐ Unit tests added ☐ Code documentation added ☐ Any pending items have an associated Issue Complete description Reverts codebase node version flyteorg/flyteconsole ✅ All checks have passed 2/2 successful checks

#703 fix: upgrading node version to 18 Pull request opened by jsonporter Upgrading to node 18 Type ☐ Bug Fix ☐ Feature ☐ Plugin Are all requirements met? ☑︎ Code completed ☑︎ Smoke tested ☐ Unit tests added ☐ Code documentation added ☐ Any pending items have an associated Issue Complete description How did you fix the bug, make the feature etc. Link to any design docs etc Tracking Issue _Remove the '_fixes_' keyword if there will be multiple PRs to fix the linked issue_ fixes https://github.com/flyteorg/flyte/issues/ Follow-up issue NA OR https://github.com/flyteorg/flyte/issues/ flyteorg/flyteconsole GitHub Actions: Build & Push FlyteConsole Image GitHub Actions: Get Release Tag GitHub Actions: Generate Release ✅ 8 other checks have passed 8/11 successful checks

1 new commit pushed to

<https://github.com/flyteorg/flyte/tree/master|master>

by eapolinario

<https://github.com/flyteorg/flyte/commit/86fa407d802476b60a48634465a374cf372e21e1|86fa407d>

- Fix broken links and reorder sections (#3381) flyteorg/flyte

#1528 [not for merging] demo pr Pull request opened by wild-endeavor on <!date^1677687215^{date_short}|2023-03-01T16:13:35Z> This is a demo pr for the pod template container task work. flyteorg/flytekit ✅ All checks have passed 30/30 successful checks

1 new commit pushed to

<https://github.com/flyteorg/flyte/tree/master|master>

by wild-endeavor

<https://github.com/flyteorg/flyte/commit/5016298c09368d055c7524482537c1b0c6583880|5016298c>

- Remove resource defaults for flyte-binary deployment in flyte-binary chart (#3392) flyteorg/flyte

1 new commit pushed to

<https://github.com/flyteorg/flytepropeller/tree/master|master>

by hamersaw

<https://github.com/flyteorg/flytepropeller/commit/5c7a31d368223b0e15e6c898d4132a8c41d22022|5c7a31d3>

- Copy dynamicJobSpec from partially completed DynamicTask on recovery (#518) flyteorg/flytepropeller

#3121 [BUG] Incorrect output data when recovering partially completed dynamic workflows Issue created by hamersaw Describe the bug Dynamic workflows work by compiling a workflow closure defining subnodes which is then subsequently evaluated. In this process, Flyte assigns each subnode an incremental unique node ID which is used to track status, etc. Since these node IDs are incremental values, in scenarios where the dynamic task has some non-deterministic ordering a node ID in one execution of the dynamic workflow may not represent the same subnode as another execution. This is problematic in partially completed dynamic workflows because the recovery mechanisms rely on node IDs to reuse previously completed executions. Under certain circumstances recovery of dynamic tasks will corrupt the result data. Expected behavior Recovery should work in all scenarios for dynamic workflows. One solution is to ensure that the recovered dynamic workflow reuses the previously computed dynamic workflow closure rather than recomputing it. This means that node IDs would be the same for both the original execution and the recovered execution. Additional context to reproduce To reproduce run the following workflow with an input dict:

import time

from flytekit import Resources, dynamic, task, workflow
from typing import Dict

@task(requests=Resources(cpu="500m", mem="400Mi"), limits=Resources(cpu="1", mem="600Mi"))
def echo(a: int) -> int:
    time.sleep(10)
    return a

@task(requests=Resources(cpu="500m", mem="400Mi"), limits=Resources(cpu="1", mem="600Mi"))
def sleep(a: int, b: Dict[str, int]) -> Dict[str, int]:
    time.sleep(a)
    return b

@dynamic(cache=True, cache_version="1.0", requests=Resources(cpu="500m", mem="400Mi"), limits=Resources(cpu="1", mem="600Mi"))
def dynamic_dict(a: Dict[str, int]) -> Dict[str, int]:
    b = {}
    for x, y in a.items():
        b[x] = echo(a=y)

    return b

@workflow
def dynamic_dict_wf(a: Dict[str, int]) -> Dict[str, int]:
    b = dynamic_dict(a=a)
    c = sleep(a=10, b=b)
    return c

Then manually fail of the of the dynamic subnodes by repeatedly deleting the pod in k8s before it completes until Flyte exhausts the number of completions. Then use the 'Recover' button in the UI to start a workflow recovery. Analyze output values of the dynamic task to see incorrect data. Screenshots An example of the reproduce context. Launched the aforementioned workflow with inputs:

{
   "foo": 1,
   "bar": 2,
   "baz": 4,
}

Manually failed the

n0-0-dn1

node to fail the workflow, the result is below: In this execution nodes

n0-0-dn0

and

n0-0-dn2

correspond to the input values

4

and

2

. So this means the

n0-0-dn1

should be responsible for

1

because the python iteration over this

Dict

was orderd

4,1,2

. Then we recover the workflow and allow it to succeed and see that the output values are:

{
   "bar": 2,
   "baz": 2,
   "foo": 4,
}

This is because the dynamic task recompiled the workflow closure which resulted in a different ordering of the

Dict

iteration. The results from

n0-0-dn0

and

n0-0-dn2

were reused - albeit applied to different keys (ie.

bar

&

foo

rather than

baz

and

bar

) and

n0-0-dn1

was executed. Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte

#518 Copy dynamicJobSpec from partially completed DynamicTask on recovery Pull request opened by hamersaw DO NOT MERGE waiting on PRs: flyteorg/flyteadmin#513 TL;DR Since node IDs in dynamic job specs are not computed deterministically between executions recovering partially completed dynamic tasks can result in data corruptions. In this PR we attempt to recover the

DynamicJobSpec

from previous the previous

DynamicTask

execution during node recovery. Type ☑︎ Bug Fix ☐ Feature ☐ Plugin Are all requirements met? ☑︎ Code completed ☑︎ Smoke tested ☑︎ Unit tests added ☑︎ Code documentation added ☐ Any pending items have an associated Issue Complete description ^^^ Tracking Issue fixes flyteorg/flyte#3121 Follow-up issue NA flyteorg/flytepropeller GitHub Actions: Goreleaser GitHub Actions: Build & Push Flytepropeller Image GitHub Actions: Bump Version ✅ 11 other checks have passed 11/14 successful checks

#3401 Update example local dev config file Pull request opened by wild-endeavor The local demo environment writes to the sandbox directory. flyteorg/flyte ✅ All checks have passed 6/6 successful checks

#532 Bump golang.org/x/crypto from 0.0.0-20210921155107-089bfa567519 to 0.1.0 in /boilerplate/flyte/golang_support_tools Pull request opened by dependabot[bot] Bumps golang.org/x/crypto from 0.0.0-20210921155107-089bfa567519 to 0.1.0. Commits • See full diff in compare view Dependabot compatibility score Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting

@dependabot rebase

. * * * Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: •

@dependabot rebase

will rebase this PR •

@dependabot recreate

will recreate this PR, overwriting any edits that have been made to it •

@dependabot merge

will merge this PR after your CI passes on it •

@dependabot squash and merge

will squash and merge this PR after your CI passes on it •

@dependabot cancel merge

will cancel a previously requested merge and block automerging •

@dependabot reopen

will reopen this PR if it is closed •

@dependabot close

will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually •

@dependabot ignore this major version

will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) •

@dependabot ignore this minor version

will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) •

@dependabot ignore this dependency

will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) •

@dependabot use these labels

will set the current labels as the default for future PRs for this repo and language •

@dependabot use these reviewers

will set the current reviewers as the default for future PRs for this repo and language •

@dependabot use these assignees

will set the current assignees as the default for future PRs for this repo and language •

@dependabot use this milestone

will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the Security Alerts page. flyteorg/flytepropeller ✅ All checks have passed 2/2 successful checks

#533 Bump golang.org/x/net from 0.0.0-20211015210444-4f30a5c0130f to 0.7.0 in /boilerplate/flyte/golang_support_tools Pull request opened by dependabot[bot] Bumps golang.org/x/net from 0.0.0-20211015210444-4f30a5c0130f to 0.7.0. Commits • See full diff in compare view Dependabot compatibility score Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting

@dependabot rebase

. * * * Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: •

@dependabot rebase

will rebase this PR •

@dependabot recreate

will recreate this PR, overwriting any edits that have been made to it •

@dependabot merge

will merge this PR after your CI passes on it •

@dependabot squash and merge

will squash and merge this PR after your CI passes on it •

@dependabot cancel merge

will cancel a previously requested merge and block automerging •

@dependabot reopen

will reopen this PR if it is closed •

@dependabot close

will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually •

@dependabot ignore this major version

will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) •

@dependabot ignore this minor version

will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) •

@dependabot ignore this dependency

will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) •

@dependabot use these labels

will set the current labels as the default for future PRs for this repo and language •

@dependabot use these reviewers

will set the current reviewers as the default for future PRs for this repo and language •

@dependabot use these assignees

will set the current assignees as the default for future PRs for this repo and language •

@dependabot use this milestone

will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the Security Alerts page. flyteorg/flytepropeller GitHub Actions: Build & Push Flytepropeller Image GitHub Actions: Goreleaser GitHub Actions: Bump Version GitHub Actions: Check Go Generate / Go Generate ✅ 10 other checks have passed 10/14 successful checks

#534 Bump k8s.io/client-go from 0.0.0-20210217172142-7279fc64d847 to 0.20.0-alpha.2 in /boilerplate/flyte/golang_support_tools Pull request opened by dependabot[bot] Bumps k8s.io/client-go from 0.0.0-20210217172142-7279fc64d847 to 0.20.0-alpha.2. Commits • See full diff in compare view Dependabot compatibility score Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting

@dependabot rebase

. * * * Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: •

@dependabot rebase

will rebase this PR •

@dependabot recreate

will recreate this PR, overwriting any edits that have been made to it •

@dependabot merge

will merge this PR after your CI passes on it •

@dependabot squash and merge

will squash and merge this PR after your CI passes on it •

@dependabot cancel merge

will cancel a previously requested merge and block automerging •

@dependabot reopen

will reopen this PR if it is closed •

@dependabot close

will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually •

@dependabot ignore this major version

will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) •

@dependabot ignore this minor version

will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) •

@dependabot ignore this dependency

will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) •

@dependabot use these labels

will set the current labels as the default for future PRs for this repo and language •

@dependabot use these reviewers

will set the current reviewers as the default for future PRs for this repo and language •

@dependabot use these assignees

will set the current assignees as the default for future PRs for this repo and language •

@dependabot use this milestone

will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the Security Alerts page. flyteorg/flytepropeller GitHub Actions: Lint / Run Lint GitHub Actions: Check Go Generate / Go Generate GitHub Actions: Docker Build Images / Build Docker Image GitHub Actions: Unit Tests / Run Unit Test GitHub Actions: Analyze (go) ✅ 2 other checks have passed 2/7 successful checks

#535 Extend pod webhook self-signed certs expiration date to 99 years in the future Pull request opened by eapolinario TL;DR 1 year self-signed certs are not enough Type ☐ Bug Fix ☐ Feature ☐ Plugin Are all requirements met? ☐ Code completed ☐ Smoke tested ☐ Unit tests added ☐ Code documentation added ☐ Any pending items have an associated Issue Complete description Tracking Issue fixes flyteorg/flyte#2871 Follow-up issue NA flyteorg/flytepropeller GitHub Actions: Goreleaser GitHub Actions: Build & Push Flytepropeller Image GitHub Actions: Bump Version ✅ 11 other checks have passed 11/14 successful checks

1 new commit pushed to

<https://github.com/flyteorg/flyteconsole/tree/master|master>

by ursucarina

<https://github.com/flyteorg/flyteconsole/commit/e5f9a8b00ac54cf370f0ccb07d6a8677066d33e0|e5f9a8b0>

- fix: upgrading node version to 18 (#703) flyteorg/flyteconsole

#3394 Add support prepending or appending paths to flyte-binary ingresses Pull request opened by jeevb flyteorg/flyte ✅ All checks have passed 12/12 successful checks

1 new commit pushed to

<https://github.com/flyteorg/flyte/tree/master|master>

by jeevb

<https://github.com/flyteorg/flyte/commit/ba423f6e40d81d0aac867b14d4b0f0431bc128a6|ba423f6e>

- Add support prepending or appending paths to flyte-binary ingresses (#3394) flyteorg/flyte

1 new commit pushed to

<https://github.com/flyteorg/flyteadmin/tree/master|master>

by pingsutw

<https://github.com/flyteorg/flyteadmin/commit/950883321ba4fa8aad7d50a190582f812f3b2c8b|95088332>

- Improve error message (#532) flyteorg/flyteadmin

Release - v1.1.76 New release published by flyte-bot Changelog • 9508833 Improve error message (#532) • efe5b0c Remove duplicate logic of resolveSecurityCtx in execution_manager (#531) flyteorg/flyteadmin

#327 Remove chief!=0 or ps!=0 assertion in tensorflow Pull request opened by ByronHsu TL;DR Remove chief!=0 or ps!=0 assertion in tensorflow Type ☑︎ Bug Fix ☐ Feature ☐ Plugin Test ``` byhsu@byhsu-ld1 ~/local-repo/flyte/flyteplugins gh-master* 14s ❯ make test_unit Makefile11 warning: overriding recipe for target `generate' boilerplate/flyte/golang_test_targets/Makefile13 warning: ignoring old recipe for target `generate' go test -cover ./... -race ok github.com/flyteorg/flyteplugins/go/tasks (cached) coverage: [no statements] ok github.com/flyteorg/flyteplugins/go/tasks/aws (cached) coverage: 36.5% of statements ? github.com/flyteorg/flyteplugins/go/tasks/config [no test files] ? github.com/flyteorg/flyteplugins/go/tasks/errors [no test files] ok github.com/flyteorg/flyteplugins/go/tasks/logs (cached) coverage: 71.2% of statements ? github.com/flyteorg/flyteplugins/go/tasks/pluginmachinery [no test files] ok github.com/flyteorg/flyteplugins/go/tasks/pluginmachinery/bundle (cached) coverage: 83.3% of statements ok github.com/flyteorg/flyteplugins/go/tasks/pluginmachinery/catalog (cached) coverage: 39.0% of statements ? github.com/flyteorg/flyteplugins/go/tasks/pluginmachinery/catalog/mocks [no test files] ok github.com/flyteorg/flyteplugins/go/tasks/pluginmachinery/core (cached) coverage: 28.0% of statements ? github.com/flyteorg/flyteplugins/go/tasks/pluginmachinery/core/mocks [no test files] ok github.com/flyteorg/flyteplugins/go/tasks/pluginmachinery/core/template (cached) coverage: 81.9% of statements ok github.com/flyteorg/flyteplugins/go/tasks/pluginmachinery/encoding (cached) coverage: 100.0% of statements ok github.com/flyteorg/flyteplugins/go/tasks/pluginmachinery/flytek8s (cached) coverage: 86.6% of statements ok github.com/flyteorg/flyteplugins/go/tasks/pluginmachinery/flytek8s/config (cached) coverage: 54.3% of statements ? github.com/flyteorg/flyteplugins/go/tasks/pluginmachinery/google [no test files] ok github.com/flyteorg/flyteplugins/go/tasks/pluginmachinery/internal/webapi (cached) coverage: 55.5% of statements ? github.com/flyteorg/flyteplugins/go/tasks/pluginmachinery/internal/webapi/mocks [no test files] ? github.com/flyteorg/flyteplugins/go/tasks/pluginmachinery/io [no test files] ? github.com/flyteorg/flyteplugins/go/tasks/pluginmachinery/io/mocks [no test files] ok github.com/flyteorg/flyteplugins/go/tasks/pluginmachinery/ioutils (cached) coverage: 49.7% of statements ? github.com/flyteorg/flyteplugins/go/tasks/pluginmachinery/k8s [no test files] ? github.com/flyteorg/flyteplugins/go/tasks/pluginmachinery/k8s/mocks [no test files] ok github.com/flyteorg/flyteplugins/go/tasks/pluginmachinery/tasklog (cached) coverage: 94.4% of statements ok github.com/flyteorg/flyteplugins/go/tasks/pluginmachinery/utils (cached) coverage: 62.3% of statements ok github.com/flyteorg/flyteplugins/go/tasks/pluginmachinery/utils/secrets (cached) coverage: 83.3% of statements ok github.com/flyteorg/flyteplugins/go/tasks/pluginmachinery/webapi (cached) coverage: 40.0% of statements ok github.com/flyteorg/flyteplugins/go/tasks/pluginmachinery/webapi/example (cached) coverage: 33.3% of statements ? github.com/flyteorg/flyteplugins/go/tasks/pluginmachinery/webapi/mocks [no test files] ok github.com/flyteorg/flyteplugins/go/tasks/pluginmachinery/workqueue (cached) coverage: 80.6% of statements ? github.com/flyteorg/flyteplugins/go/tasks/pluginmachinery/workqueue/mocks [no test files] ok github.com/flyteorg/flyteplugins/go/tasks/plugins/array (cached) coverage: 58.7% of statements ok github.com/flyteorg/flyteplugins/go/tasks/plugins/array/arraystatus (cached) coverage: 93.9% of statements ok github.com/flyteorg/flyteplugins/go/tasks/plugins/array/awsbatch (cached) coverage: 71.3% of statements ok github.com/flyteorg/flyteplugins/go/tasks/plugins/array/awsbatch/config (cached) coverage: 59.0% of statements ok github.com/flyteorg/flyteplugins/go/tasks/plugins/array/awsbatch/definition (cached) coverage: 53.3% of statements ? github.com/flyteorg/flyteplugins/go/tasks/plugins/array/awsbatch/mocks [no test files] ok github.com/flyteorg/flyteplugins/go/tasks/plugins/array/core (cached) coverage: 68.1% of statements ok github.com/flyteorg/flyteplugins/go/tasks/plugins/array/errorcollector (cached) coverage: 96.2% of statements ok github.com/flyteorg/flyteplugins/go/tasks/plugins/array/k8s (cached) coverage: 52.8% of statements ? github.com/flyteorg/flyteplugins/go/tasks/plugins/awsutils [no test files] ok <htt… flyteorg/flyteplugins Codecov: 62.86% (-0.09%) compared to 07bc0a9 GitHub Actions: Run tests and lint ✅ 4 other checks have passed 4/6 successful checks

#536 Structured Dataset with generic format should be castable to Flyte Schema Pull request opened by pingsutw TL;DR we set default structured dataset format to empty ("") in this commit. This workflow is unable to be registered because compiler expects downstream task format to be parquet, but in this case, it is generic. Type ☑︎ Bug Fix ☐ Feature ☐ Plugin Are all requirements met? ☑︎ Code completed ☑︎ Smoke tested ☑︎ Unit tests added ☐ Code documentation added ☐ Any pending items have an associated Issue Complete description ^^^ Tracking Issue NA Follow-up issue NA flyteorg/flytepropeller GitHub Actions: End2End Test / End to End tests GitHub Actions: Integration Test / Integration tests GitHub Actions: Check Go Generate / Go Generate GitHub Actions: Analyze (go) ✅ 5 other checks have passed 5/9 successful checks

#1534 Failed to initialize FlyteInvalidInputException Pull request opened by pingsutw TL;DR Failed to initialize FlyteInvalidInputException. should not use

self

in

super()

Type ☑︎ Bug Fix ☐ Feature ☐ Plugin Are all requirements met? ☑︎ Code completed ☑︎ Smoke tested ☐ Unit tests added ☐ Code documentation added ☐ Any pending items have an associated Issue Complete description ^^^ Tracking Issue NA Follow-up issue NA flyteorg/flytekit Codecov: 0.00% of diff hit (target 69.26%) GitHub Actions: build-plugins (3.10, flytekit-vaex) GitHub Actions: build-plugins (3.9, flytekit-whylogs) GitHub Actions: build-plugins (3.9, flytekit-vaex) GitHub Actions: build-plugins (3.9, flytekit-sqlalchemy) GitHub Actions: build-plugins (3.9, flytekit-spark) GitHub Actions: build-plugins (3.9, flytekit-snowflake) ✅ 23 other checks have passed 23/30 successful checks

1 new commit pushed to

<https://github.com/flyteorg/flytekit-java/tree/master|master>

by narape

<https://github.com/flyteorg/flytekit-java/commit/3e50b96a399d8d706eacef125e07635f3443dfee|3e50b96a>

- fix: upgrade com.google.api.grpc:proto-google-common-protos from 2.10… (#204) flyteorg/flytekit-java

#127 jib build Pull request opened by ckiosidis Signed-off-by: Babis Kiosidis ckiosidis@gmail.com jib does not publish the docker image TL;DR Please replace this text with a description of what this PR accomplishes. Type ☐ Bug Fix ☐ Feature ☐ Plugin Are all requirements met? ☐ Code completed ☐ Smoke tested ☐ Unit tests added ☐ Code documentation added ☐ Any pending items have an associated Issue Complete description How did you fix the bug, make the feature etc. Link to any design docs etc Tracking Issue _Remove the '_fixes_' keyword if there will be multiple PRs to fix the linked issue_ fixes https://github.com/flyteorg/flyte/issues/ Follow-up issue NA OR https://github.com/flyteorg/flyte/issues/ flyteorg/flytekit-java ✅ All checks have passed 3/3 successful checks