1 new commit pushed to

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

by hamersaw

<https://github.com/flyteorg/flytepropeller/commit/6af4de20b50d85c288d1aca3190b8a4bf03564e0|6af4de20>

- bumped flyteplugins (#549) flyteorg/flytepropeller

Release - v1.1.76 New release published by flyte-bot Changelog • 6af4de2 bumped flyteplugins (#549) flyteorg/flytepropeller

#3563 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: generate_helm GitHub Actions: trigger-sandbox-lite-build GitHub Actions: compile GitHub Actions: trigger-sandbox-build GitHub Actions: test-bootstrap GitHub Actions: docs ✅ 2 other checks have passed 2/9 successful checks

1 new commit pushed to

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

by eapolinario

<https://github.com/flyteorg/flyte/commit/08f69593d9d6fc04f3772f4bf80e87252bb497b5|08f69593>

- Update Flyte components (#3563) flyteorg/flyte

Release - v1.5.0-a0 New release published by eapolinario What's Changed • Add support for updating flytecopilot image in flyte-binary helm chart by @jeevb in #3526 • auto-update contributors by @flyte-bot in #2524 • Fix typo for enabling tensorflow plugin doc by @yubofredwang in #3539 • Update RFC process by @davidmirror-ops in #3460 • Render flyte-sandbox manifests to pick up any changes to flyte-binary chart during automation by @jeevb in #3561 • Split flyte-binary services into http and grpc, and some cleanups by @jeevb in #3518 • Update Flyte components by @flyte-bot in #3563 New Contributors • @yubofredwang made their first contribution in #3539 Full Changelog: v1.4.3...v1.5.0-a0 flyteorg/flyte

#3564 test special console build Pull request opened by wild-endeavor Tracking issue Describe your changes 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 GitHub Actions: compile GitHub Actions: docs GitHub Actions: generate_kustomize GitHub Actions: test-bootstrap GitHub Actions: generate_helm ✅ 2 other checks have passed 2/7 successful checks

Release - Flyte v1.5.0-a0 milestone release New release published by flyte-bot Flyte v1.5.0-a0 Changelog • This is an alpha release to help test changes internally before the official release. * • Noop migrations (flyteorg/flyteadmin#542) • Tracking reasons time-series (flyteorg/flyteadmin#540) • Fix fast-cache bug on first node event (flyteorg/flyteadmin#483) • Bug fix: Branch operator not taking dependencies into account (#3512) • Persist k8s plugin state between evaluations (flyteorg/flytepropeller#540) • Add support for GCP Secret Manager (flyteorg/flytepropeller#547) • Reject button on gate nodes (flyteorg/flyteconsole#733) • Better error message in casea of invalid json in launch form (flyteorg/flyteconsole#693) • Split flyte-binary services into http and grpc (#3518) flyteorg/flyte

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

#1573 [wip] Hack fix Pull request opened by kumare3 This is a quick fix that fixes the problem of duplicate map-task entities getting created in the following example

from flytekit import task, workflow, map_task

@task
def t(a: int) -> str:
    print(f"{a}")
    return str(a)

@workflow
def wf(name: str):
    map_task(t)(a=[1])
    map_task(t)(a=[1, 2])

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 https://github.com/flyteorg/flyte/issues/ Follow-up issue NA OR https://github.com/flyteorg/flyte/issues/ flyteorg/flytekit ✅ All checks have passed 30/30 successful checks

#739 feat: show launch plan information in workflow's schedules Pull request opened by pradithya TL;DR Add information of launch plan name and version to the workflow's schedule. 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 When there are multiple scheduled launchplan bound to a workflow, it is hard to understand which schedule correspond to which launchplan. This PR add additional information in the workflow's schedule to include the launch plan name and version. Additionally, when users clicked the launch plan name it will open the launchplan details page. Before After Transition Tracking Issue fixes flyteorg/flyte#3554 Follow-up issue NA flyteorg/flyteconsole GitHub Actions: Build & Push FlyteConsole Image GitHub Actions: Get Release Tag GitHub Actions: Generate Release GitHub Actions: Build Flyteconsole Image / Push to Github Registry GitHub Actions: unit_tests_with_coverage ✅ 4 other checks have passed 4/9 successful checks

#73 Login to GitHub registry only when push is enabled Pull request opened by pingsutw Publish workflow will try to run docker login first. However, this task will fail if people create a pr from fork repo. Here is an example. Login to GitHub registry if needed. I've tested here. flyteorg/flyteconsole@606d54e flyteorg/flytetools ✅ All checks have passed 2/2 successful checks

#1574 Automatically remove unused import Pull request opened by pingsutw TL;DR Add

autoflake

to

make fmt

, it can remove unused import. https://pypi.org/project/autoflake/ 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 GitHub Actions: build-plugins (3.11, flytekit-sqlalchemy) GitHub Actions: build-plugins (3.11, flytekit-snowflake) GitHub Actions: build-plugins (3.11, flytekit-polars) GitHub Actions: build-plugins (3.11, flytekit-papermill) GitHub Actions: build-plugins (3.11, flytekit-pandera) GitHub Actions: build-plugins (3.11, flytekit-kf-tensorflow) GitHub Actions: build-plugins (3.11, flytekit-kf-pytorch) GitHub Actions: build-plugins (3.11, flytekit-kf-mpi) GitHub Actions: build-plugins (3.11, flytekit-k8s-pod) GitHub Actions: build-plugins (3.11, flytekit-hive) GitHub Actions: build-plugins (3.11, flytekit-duckdb) GitHub Actions: build-plugins (3.11, flytekit-dolt) GitHub Actions: build-plugins (3.11, flytekit-deck-standard) GitHub Actions: build-plugins (3.11, flytekit-dbt) GitHub Actions: build-plugins (3.11, flytekit-data-fsspec) GitHub Actions: build-plugins (3.11, flytekit-dask) GitHub Actions: build-plugins (3.11, flytekit-bigquery) GitHub Actions: build-plugins (3.11, flytekit-aws-sagemaker) GitHub Actions: build-plugins (3.11, flytekit-aws-batch) GitHub Actions: build-plugins (3.11, flytekit-aws-athena) GitHub Actions: build-plugins (3.10, flytekit-vaex) GitHub Actions: build-plugins (3.10, flytekit-sqlalchemy) GitHub Actions: build-plugins (3.10, flytekit-snowflake) GitHub Actions: build-plugins (3.10, flytekit-papermill) ✅ 6 other checks have passed 6/30 successful checks

#3566 [Core feature] Add user id to security context Issue created by ByronHsu Motivation: Why do you think this is important? Currently, we do not have user id in the security context. Therefore, the developers are unable to decorate the task with user id on flytepropeller side. Goal: What should the final outcome look like, ideally? Add userid to security context protobuf and change related repo accordingly. Describe alternatives you've considered None 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

#388 Add userid to security context Pull request opened by ByronHsu TL;DR Add execution userid to security context Type ☐ Bug Fix ☑︎ Feature ☐ Plugin Tests Did an e2e test with flyteorg/flyteadmin#549

user_identifier

was successfully injected to flyteCRD.

securityContext:
  run_as:
    user_identifier: byhsu

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_ flyteorg/flyte#3566 flyteorg/flyteidl ✅ All checks have passed 13/13 successful checks

#549 Inject user id to security context Pull request opened by ByronHsu TL;DR Inject user id to security context TODO: move injection logic to middleware cc @Yee 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 flyteorg/flyte#3566 flyteorg/flyteadmin GitHub Actions: Goreleaser GitHub Actions: Build & Push Flyteadmin Image GitHub Actions: Build & Push Flytescheduler Image GitHub Actions: Bump Version GitHub Actions: Integration Test GitHub Actions: End2End Test GitHub Actions: Lint / Run Lint GitHub Actions: Unit Tests / Run Unit Test GitHub Actions: Docker Build Images / Build Docker Image ✅ 3 other checks have passed 3/12 successful checks

#3567 [Core feature] Support horovod in mpi task Issue created by ByronHsu Motivation: Why do you think this is important? Horovod is a special kind of tasks in mpi, it uses horovodrun to launch distributed training and ssh to communicate between launchers and workers. 1. Horovod is not implemented in flytekit mpi task. 2. Flyteplugins also need change to adjust to horovod. Goal: What should the final outcome look like, ideally? Able to run horovod on flyte Describe alternatives you've considered N/A 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

#340 [BUG] The primaryContainerName of podtemplate tasks is not overrode with kubeflow specific name Pull request opened by ByronHsu TL;DR Please replace this text with a description of what this PR accomplishes. The primaryContainerName of podtemplate tasks is not overrode with kubeflow specific name 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 In the previous implementation, we assumed all tasks are container task, so we used

taskCtx.TaskExecutionMetadata().GetTaskExecutionID().GetGeneratedName()

to get the primary container name. However, in the case of pod template, the primary container name can vary. The solution is to expose primaryContainerName from

ToK8sPodSpec

and pass to

OverridePrimaryContainerName

(which was named

OverrideDefaultContainerName)

. Tracking Issue flyteorg/flyte#3567 flyteorg/flyteplugins ✅ All checks have passed 6/6 successful checks

#341 Pass `worker_spec_command` to mpi plugin to support horovod Pull request opened by ByronHsu TL;DR Pass

worker_spec_command

to mpi plugin to support horovod task 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 In this pr in flytekit, we pass

worker_spec_command

to backend to be run on worker pod. Tracking Issue flyteorg/flyte#3567 flyteorg/flyteplugins Codecov: 50.00% of diff hit (target 62.66%) Codecov: 62.64% (-0.02%) compared to 38e8a07 GitHub Actions: Run tests and lint DCO: DCO ✅ 2 other checks have passed 2/6 successful checks

#1575 Implement horovod task in mpi plugin Pull request opened by ByronHsu TL;DR Please replace this text with a description of what this PR accomplishes. Implement horovod task in mpi plugin 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 flyteorg/flyte#3567 flyteorg/flytekit DCO: DCO ✅ 1 other check has passed 1/2 successful checks

#3568 [UI Feature] Show all important launch plan properties in the launch plan details page Issue created by pradithya Motivation: Why do you think this is important? As of now, the launch plan details page only contains the input configuration of a launch plan. Other launch plan's properties such as their schedule, the linked workflow, and notifications are not visible in the UI. Goal: What should the final outcome look like, ideally? Show all important launch plan properties in the launch plan details page.: • Linked workflow / task • Schedule • Notification • State (Active/Inactive) 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

#3570 [BUG] flytekit-java workflow test may accidentally run real task Issue created by honnix Describe the bug If a workflow task is not mocked correctly, a workflow test may accidentally run the real task, which for some cases might result a rather bad consequence. Expected behavior Users should have more control of the desired behaviour and being more explicit about running real task. Additional context to reproduce When mocking a task in workflow test, making the input values unmatched will result in running real task. Screenshots No response Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte

#740 Paused State on timeline view Pull request opened by james-union Paused gate nodes were showing as running on timeline view. This PR fixes this. 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 Need to use getFrontNodePhase to get proper state of a gate node flyteorg/flyteconsole GitHub Actions: Build & Push FlyteConsole Image GitHub Actions: Get Release Tag GitHub Actions: Generate Release GitHub Actions: Build Flyteconsole Image / Push to Github Registry ✅ 5 other checks have passed 5/9 successful checks

#3571 auto-update contributors Pull request opened by flyte-bot Automated changes by create-pull-request GitHub action flyteorg/flyte GitHub Actions: compile GitHub Actions: generate_helm GitHub Actions: docs ✅ 2 other checks have passed 2/5 successful checks

#218 Explicitly fall back to real test execution when testing Pull request opened by honnix TL;DR More or less make #217 complete. 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 • If a task is not mocked via input matching • If lambda is not null, we run the lambda (lambda being either the real thing or provided) • Otherwise we throw • If a task is mocked • If inputs match, we return output • If it is mocked with a provided lambda, we run the lambda • Otherwise, we throw Tracking Issue flyteorg/flyte#3522 Follow-up issue NA flyteorg/flytekit-java GitHub Actions: build-snapshot ✅ 2 other checks have passed 2/3 successful checks

#979 Improve documentation consistency and remove @task Pull request opened by tjKairos Different function names were being used for the hash function, so I fixed those. Further, the @task on the hash_pandas_dataframe_function would actually cause an error if it was added to the hash function. Beyond being generally incorrect behavior, it would cause an error due to the parameter being implicitly passed as a positional argument even though tasks only accept keyword arguments. flyteorg/flytesnacks GitHub Actions: Mark github pre-release as Release GitHub Actions: Publish artifacts to github release GitHub Actions: Create Prerelease GitHub Actions: Bump Version ✅ 26 other checks have passed 26/30 successful checks

#221 some tests around workflow mocking Pull request opened by bergman TL;DR Some additional test cases for #218 to document current behaviour 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 GitHub Actions: build-snapshot DCO: DCO ✅ 1 other check has passed 1/3 successful checks

1 new commit pushed to

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

by cosmicBboy

<https://github.com/flyteorg/flytesnacks/commit/0f4e45813c117842e5a9a3735817f881892ca552|0f4e4581>

- Improve documentation consistency and remove @task (#979) flyteorg/flytesnacks

Release - flytesnacks v0.3.188 New release published by flyte-bot Changelog • 0f4e458 Improve documentation consistency and remove @task (#979) • ae05aaa Exclude auto-generated style tag from sphinx-prompt (#978) flyteorg/flytesnacks

1 new commit pushed to

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

by honnix

<https://github.com/flyteorg/flytekit-java/commit/aa6440ed61f33e32cf9dc8852fe1192987e2dd09|aa6440ed>

- Explicitly fall back to real test execution when testing (#218) flyteorg/flytekit-java

#217 No spying behaviour for testing Pull request opened by honnix on <!date^1679657303^{date_short}|2023-03-24T11:28:23Z> TL;DR Remove the spying behaviour for workflow testing. Alternative to #214 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 Mocking in workflow testing has been a spying behaviour, meaning if inputs don't match, we fall back to the real task execution if the task is not remote. This behaviour is rather a surprising to users because they would not expect real thing to be executed if they explicitly mock it. This changes the behaviour to the following: • If there is no mocking, and the task is not remote, we execute the real task • If there is no mocking, and the task is remote, we return default output (empty map, effectively

void

), so the workflow test may or may not fail depending on whether the output is used in the following tasks • If there is mocking and the inputs match, we return the mocked outputs • If there is mocking but the inputs don't match, we return default output (empty map, effectively

void

), so the workflow test may or may not fail depending on whether the output is used in the following tasks Tracking Issue flyteorg/flyte#3522 Follow-up issue NA flyteorg/flytekit-java GitHub Actions: build-snapshot ✅ 2 other checks have passed 2/3 successful checks