1 new commit pushed to

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

by wild-endeavor

<https://github.com/flyteorg/flyte/commit/268d167372d2ec1ef03150604c39026a74d95dc9|268d1673>

- Run functional tests against sandbox-bundled (#3581) flyteorg/flyte

#391 Data addresses #minor Pull request opened by wild-endeavor TL;DR Add a new endpoint to return friendlier names for Literal Map inputs and outputs. 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/flyteidl ✅ All checks have passed 22/22 successful checks

1 new commit pushed to

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

by hamersaw

<https://github.com/flyteorg/flytepropeller/commit/ef164c5b7088510a88056c2a2f3a08af4295e026|ef164c5b>

- Remove resource injection on the node for container task (#544) flyteorg/flytepropeller

#342 Feat: Add elastic training to pytorch plugin Pull request opened by fg91 on <!date^1680544051^{date_short}|2023-04-03T17:47:31Z> Read then delete this section WIP early prototype - Make sure to use a concise title for the pull-request. _- Use #patch, #minor or #major in the pull-request title to bump the corresponding version. Otherwise, the patch version will be bumped. More details_ 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/flyteplugins DCO: DCO ✅ 1 other check has passed 1/2 successful checks

#3582 [BUG] Potential race condition in Flyte Propeller Issue created by pablocasares Describe the bug I am monitoring multiple workflows containing subworkflows running in parallel. I'm using Propeller v1.1.70. Some of the executions fail with this error.

CausedByError: Failed to propagate Abort for workflow. Error: 0: [SystemError] system error, caused by: rpc error: code = PermissionDenied desc = Cannot abort an already terminate workflow execution

. One of the subworkflows is intented to fail under certain conditions. When this workflow fails, Propeller tries to abort the rest of the running subworkflows. Sometimes the rest of the subworkflows are properly aborted but other times Propeller receives that PermissionDenied error from Flyte Admin. It seems to be a race condition in Propeller, when Propeller tries to abort a workflow in a terminated status because when Propeller checks the Status of the rest of the subworkflows they are in status "running" but at the time when the abort is called they already changed to a terminated status. I checked that the finish time difference when this happened between the failing subworkflow that is trying to abort the rest and the successful one is 3 ms so I think that when propeller checks the status of the rest it is reported as running although it is actually Succeeded when the abort call is executed. Maybe these lines are relevant to the issue: https://github.com/flyteorg/flytepropeller/blob/master/pkg/controller/nodes/task/handler.go#L795-L825 (currentPhase might change when p.Abort is called) Please check the attached screenshots to see how different executions of the same code produce different results. Eventually, the parent workflow (the one containing the subworkflows) fails with this error:

RuntimeExecutionError: max number of system retry attempts [51/50] exhausted.

This error is increasing the number of calls made to FlyteAdmin and also this is increasing the metric associated to the PermissionDenied error. Please do not hesitate to ask for further information if needed. Expected behavior FlytePropeller should not retry to abort a node in a terminated status and that node status should be updated in parent workflow with the terminated status (sometimes the node is shown as running although it is succeeded when you open the subworkflow). 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

#3583 Flytekit gives ssl certificate verify error while using flyteremote Issue created by samuel-sujith Describe the bug I am trying to use a flytekit.remote to fetch and start a workflow. While doing that I am getting certificate verify error which causes this jod to fail ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1129) However when i run flytectl get projects, I am able to list all the projects without any issues. Please assist in getting this resolved. Expected behavior flytekit remote should behave in exactly the same way as flytectl and not give certificate errors. 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

#741 fix: passthrough runtime env vars Pull request opened by ursucarina TL;DR Allows runtime environment variables to be passed through to the UI 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 Adds cheerio and injects window.env into the served html Tracking Issue NA Follow-up issue NA 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

#27 GHCR Image Registry Link Pull request opened by zeryx Adds a link to the ghcr.io image registry page for flytekit-python-template https://github.com/flyteorg/flytekit-python-template/pkgs/container/flytekit-python-template flyteorg/flytekit-python-template ✅ All checks have passed 2/2 successful checks

#3584 fixes copy button issue Pull request opened by cosmicBboy This fixes an issue with the copy-button on the

flyte

repo docs flyteorg/flyte ✅ All checks have passed 6/6 successful checks

#28 added hashed tag for template push Pull request opened by zeryx Added a secondary tag for each image, which contains the git hash of main; providing a lineage of all previous versions of this repo. flyteorg/flytekit-python-template ✅ All checks have passed 2/2 successful checks

1 new commit pushed to

<https://github.com/flyteorg/flytekit-python-template/tree/main|main>

by zeryx

<https://github.com/flyteorg/flytekit-python-template/commit/f8281b33d330eb0e79a80ca2c013413d311a8bf3|f8281b33>

- Update README.md (#27) flyteorg/flytekit-python-template

1 new commit pushed to

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

by jsonporter

<https://github.com/flyteorg/flyteconsole/commit/7115a0610d03511465373969f8493f0ee997f590|7115a061>

- feat: show launchplan in execution table (#738) flyteorg/flyteconsole

1 new commit pushed to

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

by jsonporter

<https://github.com/flyteorg/flyteconsole/commit/c5fc069c6d5dfeacb21afa166c4fc3141cac3974|c5fc069c>

- feat: show launch plan information in workflow's schedules (#739) flyteorg/flyteconsole

Release - v1.6.0 New release published by flyte-bot 1.6.0 (2023-04-11) Features • show launch plan information in workflow's schedules (#739) (c5fc069) • show launchplan in execution table (#738) (7115a06) flyteorg/flyteconsole

#3585 [UI Feature] Ability to activate/deactiave Launch Plan Issue created by pradithya Motivation: Why do you think this is important? As of now, activating or deactivating the scheduled launch plan can only be done using

flytectl

. This limitation introduce UX friction for users who are used to using UI to operate their ML pipelines. Having the ability to activate/deactivate launch plan from Flyteconsole will greatly improve the usability of the Flyte console. Goal: What should the final outcome look like, ideally? User should be able to activate and deactivate certain version of Launch Plan using Flyte Console. 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

#3586 [BUG] Native scheduler failed silently and restarted when running malformed Launch Plan Issue created by pradithya Describe the bug Native scheduler is not able to create execution for a scheduled Launch Plan that doesn't provide all required input. The error is not surfaced to user and only available as error log in the native scheduler. Additionally, the native scheduler is experiencing restart when trying to catch up the launch plan

{"json":{"src":"schedule_executor.go:93"},"level":"error","msg":"failed to catch up on all the schedules. Aborting","ts":"2023-04-12T07:04:15Z"}
{"json":{"src":"schedule_executor.go:94"},"level":"info","msg":"Flyte native scheduler shutdown","ts":"2023-04-12T07:04:15Z"}

It's also possible that catch up procedure for a valid scheduled launch plan might not be executed if there is malformed launch plan. This line will immediately exit

CatchupAll

which potentially can starve other launch plan (https://github.com/flyteorg/flyteadmin/blob/eb695b19dcc6fd53492176586c2ab9d64f0c990d/scheduler/core/gocron_scheduler.go#L190) Expected behavior 1. Scheduled Launch Plan with incomplete inputs should be rejected during registration. 2. Error during create execution request from scheduler should be surfaced to the user so that they are aware of the issue. 3. Ensure that scheduler doesn't restart when a malformed scheduled launch plan is failed to be executed. I think fixing 1 is more urgent as it can avoid this issue altogether. However, 2 will also be useful in case there is any condition that can lead to this. Additional context to reproduce Using the following workflow and launch plan code.

@task
def square(a: int) -> int:
    return a * a

@task
def add(a: int, b: int) -> int:
    return a + b

@workflow
def my_wf(kickoff_time: datetime, a: int, b: int) -> int:
    # a and b are required inputs
    x = square(a=a)
    return add(a=x, b=b)

my_wf_lp = LaunchPlan.get_or_create(
        name=f"my-schedule",
        workflow=my_wf,
        fixed_inputs={
            "a": 1,
            # omit b from fixed_inputs, so the scheduled launch plan will only pass in "kickoff_time" and "a" input.
        },
        schedule=CronSchedule(
            schedule="*/5 * * * *",
            kickoff_time_input_arg="kickoff_time",
        ),
    )

Log in scheduler

{
  "json": {
    "routine": "jobfunc-11804557365892249653",
    "src": "executor_impl.go:110"
  },
  "level": "error",
  "msg": "failed to create execution create request %+v due to %vproject:\"sample\" domain:\"development\" name:\"f0bd182b3249867ba000\" spec:<launch_plan:<resource_type:LAUNCH_PLAN project:\"sample\" domain:\"development\" name:\"ml_pipeline.launchplan.schedule\" version:\"0.1.5\" > metadata:<mode:SCHEDULED scheduled_at:<seconds:1681271880 > > > inputs:<literals:<key:\"kickoff_time\" value:<scalar:<primitive:<datetime:<seconds:1681271880 > > > > > >  rpc error: code = InvalidArgument desc = expected_inputs b missing",
  "ts": "2023-04-12T04:04:42Z"
}

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

#103 Infer GOOS and GOARCH from environment Pull request opened by jeevb flyteorg/datacatalog GitHub Actions: Goreleaser GitHub Actions: Build & Push Datacatalog Image GitHub Actions: Bump Version ✅ 6 other checks have passed 6/9 successful checks

1 new commit pushed to

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

by jeevb

<https://github.com/flyteorg/datacatalog/commit/9ebdb93534cd4048a236b10b98aeba395849565a|9ebdb935>

- Infer GOOS and GOARCH from environment (#103) flyteorg/datacatalog

#552 Infer GOOS and GOARCH from environment Pull request opened by jeevb flyteorg/flytepropeller GitHub Actions: Goreleaser GitHub Actions: Build & Push Flytepropeller Image GitHub Actions: Bump Version ✅ 10 other checks have passed 10/13 successful checks

1 new commit pushed to

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

by jeevb

<https://github.com/flyteorg/flytepropeller/commit/2be01e251f21687e581e2f78a55b965e46cf184f|2be01e25>

- Infer GOOS and GOARCH from environment (#552) flyteorg/flytepropeller

#550 Infer GOOS and GOARCH from environment Pull request opened by jeevb flyteorg/flyteadmin ✅ All checks have passed 2/2 successful checks

Release - v1.0.45 New release published by flyte-bot Changelog • 9ebdb93 Infer GOOS and GOARCH from environment (#103) flyteorg/datacatalog

#57 Enable multiarch build and infer GOOS and GOARCH from environment Pull request opened by jeevb flyteorg/flytecopilot GitHub Actions: Dry run goreleaser ✅ 8 other checks have passed 8/9 successful checks

#554 fix makefile to read variables from environment and overrides Pull request opened by jeevb flyteorg/flytepropeller GitHub Actions: Build & Push Flytepropeller Image GitHub Actions: Goreleaser GitHub Actions: Bump Version ✅ 11 other checks have passed 11/14 successful checks

#104 fix makefile to read variables from environment and overrides Pull request opened by jeevb flyteorg/datacatalog GitHub Actions: Build & Push Datacatalog Image GitHub Actions: Goreleaser GitHub Actions: Bump Version ✅ 8 other checks have passed 8/11 successful checks

Release - v1.1.79 New release published by flyte-bot Changelog • 2be01e2 Infer GOOS and GOARCH from environment (#552) • ef164c5 Remove resource injection on the node for container task (#544) flyteorg/flytepropeller

#737 fix: force node executions to pull their status Pull request opened by ursucarina TL;DR Running node executions should poll for their status 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 Node executions are now polling for their status while in view as long as they are running. flyteorg/flyteconsole Codecov: 66.40% (-0.24%) compared to 33ee52a GitHub Actions: Build & Push FlyteConsole Image GitHub Actions: Get Release Tag GitHub Actions: Generate Release ✅ 7 other checks have passed 7/11 successful checks

#3587 [Core feature] activate launchplans via pyflyte Issue created by wckdman Motivation: Why do you think this is important? Launchplan is tied to a specific workflow version, and it needs to be activated with two

flytectl

commands: •

flytectl get launchplans -p {project} -d {domain} {launchplan_name}

to list all launchplans •

flytectl update launchplan -p {project} -d {domain} {launchplan_name} --version {version} --activate

to activate the correct one It would be nice to simplify this process. Goal: What should the final outcome look like, ideally? Create a CLI command which activates the latest version of a launch plan by default. It could also accept a specific version as a parameter. Describe alternatives you've considered I propose to add this feature to pyflyte 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

#1588 Feature: add activate-launchplan command to pyflyte Pull request opened by wckdman TL;DR Adds a new command to pyflyte which simplifies the process of activating new launch plans 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 I found that

SynchronousFlyteClient

has update_launch_plan method. So I decided to wrap it up as a CLI-command. Tracking Issue flyteorg/flyte#3587 Follow-up issue NA flyteorg/flytekit ✅ All checks have passed 30/30 successful checks

1 new commit pushed to

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

by cosmicBboy

<https://github.com/flyteorg/flyte/commit/36efb93aabcfed787d008998f8bd85d4f7ccb3c6|36efb93a>

- [auto-update-contributors] update all-contributors (#3571) flyteorg/flyte