1 new commit pushed to

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

by github-actions[bot]

<https://github.com/flyteorg/flytekit-java/commit/abe896bccc72df421c66314eef98d82cf39c376b|abe896bc>

- [maven-release-plugin] prepare release 0.4.11 flyteorg/flytekit-java

1 new commit pushed to

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

by github-actions[bot]

<https://github.com/flyteorg/flytekit-java/commit/7212239dfd14680bdb33d3dcb83cc1141d3eb158|7212239d>

- [maven-release-plugin] prepare for next development iteration flyteorg/flytekit-java

#726 fix: release fail Pull request opened by ursucarina TL;DR Upgrading actions to fix hooks error 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 Upgrated to: • actions/checkout@v3 • actions/setup-node@v3 flyteorg/flyteconsole GitHub Actions: Build & Push FlyteConsole Image GitHub Actions: Get Release Tag GitHub Actions: Generate Release ✅ 6 other checks have passed 6/9 successful checks

1 new commit pushed to

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

by ursucarina

<https://github.com/flyteorg/flyteconsole/commit/b3074dc636d20d5682a7f9629830bebb6e91c279|b3074dc6>

- fix: release fail (#726) flyteorg/flyteconsole

1 new commit pushed to

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

by github-actions[bot]

<https://github.com/flyteorg/flytekit-java/commit/99d14bff71d028381c6fcf62ce424b46ca0c7915|99d14bff>

- [maven-release-plugin] prepare release 0.4.12 flyteorg/flytekit-java

1 new commit pushed to

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

by github-actions[bot]

<https://github.com/flyteorg/flytekit-java/commit/ae39aafc77c3e81a3ddfaeb74d8d8512da260aed|ae39aafc>

- [maven-release-plugin] prepare for next development iteration flyteorg/flytekit-java

Release - v1.5.2 New release published by flyte-bot 1.5.2 (2023-03-17) Bug Fixes • backfill index on execution task logs (#725) (426ce41) • release fail (#726) (b3074dc) flyteorg/flyteconsole

#3487 [v1.4.2] Update Flyte components Pull request opened by flyte-bot Updated flyte deployment • Updated GCP Flyte kustomize generated manifest file • Updated EKS Flyte kustomize generated manifest file • Updated Sandbox Flyte kustomize generated manifest file • Updated TEST Flyte kustomize generated manifest file • Updated GCP Flyte helm generated manifest file • Updated EKS Flyte helm generated manifest file • Updated Sandbox Flyte helm generated manifest file • Updated TEST Flyte helm generated manifest file • Auto-generated by [flyte-bot] flyteorg/flyte GitHub Actions: generate_kustomize GitHub Actions: test-bootstrap GitHub Actions: trigger-sandbox-build ✅ 2 other checks have passed 2/5 successful checks

#3488 Update Flyte components Pull request opened by flyte-bot Updated flyte deployment • Updated GCP Flyte kustomize generated manifest file • Updated EKS Flyte kustomize generated manifest file • Updated Sandbox Flyte kustomize generated manifest file • Updated TEST Flyte kustomize generated manifest file • Updated GCP Flyte helm generated manifest file • Updated EKS Flyte helm generated manifest file • Updated Sandbox Flyte helm generated manifest file • Updated TEST Flyte helm generated manifest file • Auto-generated by [flyte-bot] flyteorg/flyte GitHub Actions: trigger-single-binary-build GitHub Actions: trigger-single-binary-build GitHub Actions: generate_helm GitHub Actions: generate_kustomize GitHub Actions: generate_kustomize GitHub Actions: generate_helm GitHub Actions: test-bootstrap GitHub Actions: trigger-sandbox-build GitHub Actions: docs GitHub Actions: compile GitHub Actions: trigger-sandbox-lite-build GitHub Actions: trigger-sandbox-build GitHub Actions: Functional test GitHub Actions: docs GitHub Actions: trigger-sandbox-lite-build GitHub Actions: compile GitHub Actions: Functional test DCO: DCO ✅ 2 other checks have passed 2/20 successful checks

#3316 Execution Details Performance Refactor Issue created by cosmicBboy This issue is a duplicate of unionai/cloud#1646, just creating this issue for tracking under Flyte OSS project flyteorg/flyte

#2322 [Core Feature] Add project level API to return the global settings Issue created by pmahindrakar-oss Describe the issue With this issue #2070 Project domain settings have been added for execution config and which will be shown in the UI on the domain landing page. We also need Project level global settings which the user can view What if we do not do this? User wont be aware of global config which can get used in the absence of project-domain settings Related component(s) No response Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte

1 new commit pushed to

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

by wild-endeavor

<https://github.com/flyteorg/flyte/commit/b6b0da712d138cb887cc107429fa42846ed9b8d9|b6b0da71>

- Revert "starting controller runtime manager (#3471)" (#3489) flyteorg/flyte

1 new commit pushed to

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

by wild-endeavor

<https://github.com/flyteorg/flyte/commit/9bef5ffc16f5aafc4ff07a64bce86d0b55dddd8a|9bef5ffc>

- [v1.4.2] Update Flyte components (#3487) flyteorg/flyte

Release - Flyte v1.4.2 milestone release New release published by flyte-bot Flyte 1.4.2 release This patch release pulls in flyteorg/flyteconsole#721 flyteorg/flyte

Deployment to github-pages by flyte-bot flyteorg/flyte

Release - Flyte v1.4.2 milestone release New release published by flyte-bot Flyte 1.4.2 release This patch release pulls in flyteorg/flyteconsole#721 flyteorg/flyte

Deployment to github-pages by flyte-bot flyteorg/flyte

#973 Comment out schema_compatibility_df workflow temporarily Pull request opened by eapolinario This should have been done as part of #972. flyteorg/flytesnacks GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/kubernetes/kfmpi) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/case_studies/ml_training/spark_horovod) ✅ 28 other checks have passed 28/30 successful checks

1 new commit pushed to

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

by eapolinario

<https://github.com/flyteorg/flytesnacks/commit/81b71ec26344d3e6c9e63c98c90020f9c6e62b07|81b71ec2>

- Comment out schema_compatibility_df workflow temporarily (#973) flyteorg/flytesnacks

Release - flytesnacks v0.3.185 New release published by flyte-bot Changelog • 81b71ec Comment out schema_compatibility_df workflow temporarily (#973) flyteorg/flytesnacks

#3492 [Core feature] Add the support for defining/declaring tasks in classes Issue created by XinEDprob Motivation: Why do you think this is important? I wanted to build a Flyte pipeline for an existing project and I noticed that there are lots of classes in this project. If the Flyte can not support the code like the following:

from flytekit import workflow, task


class MyClass:

    @task
    def t1(self):
        return 'hello world'


@workflow
def wf():
    MyClass().t1()

there will be lots of work for us as we need to convert all the classes to functions so that these functions can be decorated as tasks. I believe this feature is important for the following reasons: • Encourage people to build more Flyte pipelines for the existing projects • The code will be more organized and concise Goal: What should the final outcome look like, ideally? In the end, I hope Flyte can support something like the following

from flytekit import workflow, task


class MyClass:

    @task
    def t1(self):
        return 'hello world'


@workflow
def wf():
    MyClass().t1()

That is to define tasks within classes Describe alternatives you've considered I don't think I have any alternative for this issue. Propose: Link/Inline OR Additional context No response Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte

1 new commit pushed to

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

by eapolinario

<https://github.com/flyteorg/flyteadmin/commit/8cf8b4aba63cda8426da806e689534e1d374bd1b|8cf8b4ab>

- Upgrade flytepropeller (#541) flyteorg/flyteadmin

Release - v1.1.83 New release published by flyte-bot Changelog • 8cf8b4a Upgrade flytepropeller (#541) flyteorg/flyteadmin

#1554 Update the pypi wait Pull request opened by wild-endeavor TL;DR Lately we've been seeing that waiting for three minutes is not enough, bumping it up to ten minutes and failing explicitly Type ☑︎ Bug Fix ☐ Feature ☐ Plugin flyteorg/flytekit ✅ All checks have passed 2/2 successful checks

#3493 [Housekeeping] Functional tests should use the demo sandbox Issue created by eapolinario Describe the issue We currently run functional tests in component (flyteadmin, flytepropeller, etc) PRs using the legacy sandbox. Note that this allows us for replacing the version of components quite easily. We need to invest in a way to have a tight feedback in the new sandbox (demo) as well. This includes a way to replace the component versions. What if we do not do this? This blocks the deprecation of legacy sandbox. Also, the new sandbox is substantially faster to come up, so tests would also run 2-3x faster. Related component(s) sandbox Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte

#3494 [BUG] Flyteconsole: launch form validation not working correctly when removing k/v Issue created by jsonporter Describe the bug User reported that when specifying a map<string, struct> input in launch form and deleting a k/v from the map, the "Launch" button becomes grayed out as if the input is invalid, even though the other entries are formatted correctly. This is a bug involving the validation logic on the form see: Expected behavior Both adding and removing keys should be respected by the validation logic on the launch form. Additional context to reproduce No response Screenshots Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte

#1555 Pyflyte build imageSpec Pull request opened by pingsutw TL;DR RFC We add a new arg

imageSpec

, user can specify it in the either

@task

or

@workflow

, then flytekit will build the image at registration time. 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 Example:

from flytekit import task, workflow
from flytekit.image_spec.image_spec import ImageSpec


@task
def t2() -> str:
    print("hello")
    return "hello"


@task(image_spec=ImageSpec(packages=["pandas", "numpy"], registry="pingsutw"))
def t1() -> str:
    print("hello")
    print("hello")
    return "hello"


@workflow(image_spec=ImageSpec(
    packages=["git+<https://github.com/flyteorg/flytekit@4834ba03470b66f2f7c800c6b08e77062f2442b6%22|https://github.com/flyteorg/flytekit@4834ba03470b66f2f7c800c6b08e77062f2442b6">],
    apt_packages=["git"],
    registry="pingsutw")
)
def wf():
    t1()
    t2()


if __name__ == '__main__':
    wf()

image.lock:

{
  "pingsutw": [
    "9zGai7ij01MWkewVim1cxg..",
    "2mvWPRSd8LMbtyhyanIO5Q..",
    "48b32eb8bbd164cbcf021f4c944c3aed",
    "b91e0d14186edfef00d7ffafd642ffa2",
    "dba9147b996c9d40a8a612fb34dc5ce7",
    "850d8a35b44ba2694019256e560d2770",
    "dff95b42bf5c3273942dd8cf2f7dbbaa",
    "613633db1f727f3645621a5b7b9e9b9f",
    "05db5f898e1a5ccdc2796ebea33a4454"
  ]
}

Tracking Issue https://github.com/flyteorg/flyte/issues/ Follow-up issue TODO: 1. Docs 2. pyflyte build --remote flyteorg/flytekit ✅ All checks have passed 30/30 successful checks

#3496 [Docs] Add a multi images example that uses different modules Issue created by samhita-alla Description The example we currently have in our docs doesn't capture importing different dependencies in tasks.

@task(container_image="")
def foo():
  import my_module1
  <http://my_module1.xyz|my_module1.xyz>()
  ...

@task(container_image="")
def foo2():
   import my_module2
   my_module2.abc():
   ...

We need to add an example that imports libraries within tasks. This is helpful when tasks import different dependencies. Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte

Release - 0.4.12 New release published by narape What's Changed • Add factory method for remote task with fixed version by @sonjaer in #210 • Support Scala

Unit

when checking "null" inputs by @narape in #206 • Fix dynamic workflows serialization by @narape in #212 • [Snyk] Upgrade com.google.api.grpc:proto-google-common-protos from 2.14.0 to 2.14.1 by @snyk-bot in #207 • Add registerLaunchPlan with action to SimpleSdkLaunchPlanRegistry by @pablocasares in #211 Full Changelog: 0.4.6...0.4.7 flyteorg/flytekit-java

#3497 [Docs] Create flytesnacks docs for external web API plugins in flytekit Issue created by cosmicBboy flyteorg/flyte