#351 updating dask plugin to use container resources with overrides Pull request opened by hamersaw TL;DR This PR updates the Dask plugin to use container resources by default and then merges the task execution overrides and platform overrides if necessary. 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#3694 Follow-up issue NA flyteorg/flyteplugins ✅ All checks have passed 7/7 successful checks

#761 chore: add item when mapped task Pull request opened by jsonporter Note: This PR is WIP Adds a more correct context to the attempts UI when dealing with mapped tasks. 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 NA Tracking Issue NA Follow-up issue NA 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

#1646 pyflyte run supports pickle Pull request opened by pingsutw TL;DR This allows pyflyte run to accept pickle file.

from typing import Dict, Any
from flytekit import task, workflow

@task
def test(config: Dict[str, Any]) -> None:
    print(config)


@workflow
def wf(config: Dict[str, Any]) -> None:
    test(config=config)

pyflyte --config ~/.flyte/config-remote.yaml --verbose run --remote test.py wf --config '{"hello": "world"}'

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 https://flyte-org.slack.com/archives/CP2HDHKE1/p1684272325647759 Follow-up issue NA flyteorg/flytekit Codecov: 71.01% (-0.21%) compared to faf02b1 ✅ 29 other checks have passed 29/30 successful checks

#37 Remove mentions to awscli Pull request opened by eapolinario As of flytekit 1.5.0 we now rely exclusively on fsspec for handling IO. flyteorg/flytekit-python-template GitHub Actions: integration_tests ✅ 3 other checks have passed 3/4 successful checks

1 new commit pushed to

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

by jsonporter

<https://github.com/flyteorg/flyteconsole/commit/e316beff83d6b363aa2285bbc06864172c823f9f|e316beff>

- Bug: Execution Page's back button returns Workflows route from Launch Plan route #patch (#760) flyteorg/flyteconsole

Release - v1.2.12 New release published by eapolinario As mentioned in flytekit 1.3.0 release, we'll be backporting flytekit releases to the 1.2 release. This release is targeted at flytekit users who for some reason cannot upgrade to the new major version of the protobuf library. In this specific case we're backporting all changes announced in the 1.6 release. What's Changed • [v1.2 Backport] Less strict docker dependency versions (#1536) by @jcugat in #1564 • [release v1.2] Backport v1.6 by @eapolinario in #1645 Full Changelog: v1.2.11...v1.2.12 flyteorg/flytekit

1 new commit pushed to

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

by eapolinario

<https://github.com/flyteorg/flytekit-python-template/commit/c96bff8b23196f38b0dd296d9bfd2e848221059a|c96bff8b>

- Remove mentions to awscli (#37) flyteorg/flytekit-python-template

#1647 Wait for the pod plugin instead of flytekit Pull request opened by eapolinario TL;DR Wait for one the plugins to show up in PyPI instead of the main package 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 We introduced an explicit wait in #1554, but it turns out that most of the failures (e.g. https://github.com/flyteorg/flytekit/actions/runs/5007729856/jobs/8974742807#step:7:659) we're seeing during releases are for the plugins (which are published in order). So, let's wait for the pod plugin instead of the main package. Tracking Issue https://github.com/flyteorg/flyte/issues/ Follow-up issue NA OR https://github.com/flyteorg/flyte/issues/ 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-envd) 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-whylogs) GitHub Actions: build-plugins (3.10, flytekit-vaex) GitHub Actions: build-plugins (3.10, flytekit-sqlalchemy) GitHub Actions: build-plugins (3.10, flytekit-spark) GitHub Actions: build-plugins (3.10, flytekit-snowflake) GitHub Actions: build-plugins (3.10, flytekit-ray) GitHub Actions: build-plugins (3.10, flytekit-polars) GitHub Actions: build-plugins (3.10, flytekit-papermill) ✅ 1 other check has passed 1/30 successful checks

#1648 Enable envd plugin for python 3.7 Pull request opened by eapolinario TL;DR envd supports python 3.7, let's make the envd flytekit plugin in the 1.2 branch also support that 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 This is preventing us from generating the default docker images for the 1.2.12 release. Tracking Issue https://github.com/flyteorg/flyte/issues/ Follow-up issue NA OR https://github.com/flyteorg/flyte/issues/ flyteorg/flytekit 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-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: lint GitHub Actions: build (windows-latest, 3.9) GitHub Actions: build (windows-latest, 3.8) GitHub Actions: build (windows-latest, 3.7) GitHub Actions: build (ubuntu-latest, 3.10) GitHub Actions: build (ubuntu-latest, 3.9) GitHub Actions: build (ubuntu-latest, 3.8) GitHub Actions: build (ubuntu-latest, 3.7) ✅ 2 other checks have passed 2/18 successful checks

#3695 [Core feature] Support start and end times for mapped task Issue created by pmahindrakar-oss Motivation: Why do you think this is important? Currently mapped task don't contain the start and end times The execution metadata for the map task has info in the ExternalResources but doesn't contain any information about the range of each mapped task https://github.com/flyteorg/flyteidl/blob/master/gen/pb-go/flyteidl/event/event.pb.go#L1180 https://github.com/flyteorg/flyteidl/blob/master/gen/pb-go/flyteidl/event/event.pb.go#L1034 Goal: What should the final outcome look like, ideally? The ask here is to obtain this information and store in the ExternalResources Describe alternatives you've considered None available 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

#404 Single literal Pull request opened by wild-endeavor TL;DR Add a single Literal to the response map for the new GetData endpoint. This allows users to request a specific input or output instead of having to filter the literal map. 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 See https://github.com/flyteorg/flyteadmin/pull/565/files for the implementation. Tracking Issue NA flyteorg/flyteidl ✅ All checks have passed 13/13 successful checks

#565 Tiny url improvements Pull request opened by wild-endeavor TL;DR This adds the ability to return an individual input or output in the flyte url, e.g.

<flyte://v1/flytesnacks/development/ad5cb55f675g2s78swgp/end-node/i/o0>

There's currently no mechanism by which these URLs can be returned to the frontend however. This can be worked on separately. 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 • Refactored out the parsing logic to return a union instead. go doesn't have unions so returning a struct. • Split out the GetData function into one for node level and one for task execution level. • Added a second regex object to try to match against. Tracking Issue NA flyteorg/flyteadmin GitHub Actions: Build & Push Flyteadmin Image GitHub Actions: Goreleaser GitHub Actions: Build & Push Flytescheduler Image GitHub Actions: Bump Version ✅ 10 other checks have passed 10/14 successful checks

1 new commit pushed to

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

by eapolinario

<https://github.com/flyteorg/flytectl/commit/5cb23b7fb2f6838817bd20350708727a95aabd5f|5cb23b7f>

- Print instruction after teardown (#403) flyteorg/flytectl

#404 [Snyk] Fix for 2 vulnerabilities Pull request opened by snyk-bot Snyk has created this PR to fix one or more vulnerable packages in the

pip

dependencies of this project. Changes included in this PR • Changes to the following files to upgrade the vulnerable dependencies to a fixed version: • doc-requirements.txt Vulnerabilities that will be fixed By pinning: (*) Note that the real score may have changed since the PR was raised. Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded. Check the changes in this PR to ensure they won't cause issues with your project. * * * Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs. For more information: https://camo.githubusercontent.com/5f9290c5b0e0891d4a11826366b933ee8da1b0599c10deb97073e0461352302c/68747470733a2f2f6170692e7365676d656e742e696f2f76312f706978656c2f747261636b3f646174613d65794a33636d6c305a55746c65534936496e4a79576d785a634564485932527954485a7362306c596430645563566734576b4652546e4e434f5545774969776959573576626e6c746233567a535751694f694a6a4e446c6d59324d314d5330784e6d5a6a4c5451354e6d557459575533597930345a544d794d6a4d34595751304d7a63694c434a6c646d567564434936496c425349485a705a58646c5a434973496e42796233426c636e52705a584d694f6e736963484a4a5a434936496d4d304f575a6a597a55784c5445325a6d4d744e446b325a5331685a54646a4c54686c4d7a49794d7a68685a44517a4e794a3966513d3d 🧐 View latest project report 🛠️ Adjust project settings 📚 Read more about Snyk's upgrade and patch logic * * * Learn how to fix vulnerabilities with free interactive lessons: 🦉 Regular Expression Denial of Service (ReDoS) flyteorg/flytectl GitHub Actions: Goreleaser GitHub Actions: Generate documentation GitHub Actions: Bump Version DCO: DCO ✅ 8 other checks have passed 8/12 successful checks

Release - v0.6.37 New release published by flyte-bot Changelog • 5cb23b7 Print instruction after teardown (#403) flyteorg/flytectl

1 new commit pushed to

<https://github.com/flyteorg/homebrew-tap/tree/main|main>

by flyte-bot

<https://github.com/flyteorg/homebrew-tap/commit/9a6b211b9f07c75179cd20a56ae53ab56371cb73|9a6b211b>

- Brew formula update for flytectl version v0.6.37 flyteorg/homebrew-tap

1 new commit pushed to

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

by pingsutw

<https://github.com/flyteorg/flytekit/commit/4f57ab9009e73aa06a538ec4eafff90443e35219|4f57ab90>

- pyflyte run supports pickle (#1646) flyteorg/flytekit

1 new commit pushed to

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

by wild-endeavor

<https://github.com/flyteorg/flyte/commit/a50039aebfe6c20d113f4bf35c0ff059fb6c896b|a50039ae>

- Add default project (#3692) flyteorg/flyte

1 new commit pushed to

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

by eapolinario

<https://github.com/flyteorg/flytekit/commit/ba70f4685e5ab4e00f23c5adedb281110b20f96e|ba70f468>

- Wait for the pod plugin instead of flytekit (#1647) flyteorg/flytekit

Release - v1.2.13 New release published by eapolinario What's Changed • Enable envd plugin for python 3.7 by @eapolinario in #1648 Full Changelog: v1.2.12...v1.2.13 flyteorg/flytekit

#1649 Add RemoteFileAccessProvider Pull request opened by pingsutw TL;DR Currently, flytekit remote will try to use s3fs to upload data, but it should use data proxy instead. RemoteFileAccessProvider allows flytekit remote to upload the data (structure dataset, flyte file, etc) to the s3. 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 https://flyte-org.slack.com/archives/CP2HDHKE1/p1684272325647759 Follow-up issue NA flyteorg/flytekit 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-mlflow) 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-envd) 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.11) GitHub Actions: build (windows-latest, 3.9) GitHub Actions: build (windows-latest, 3.8) GitHub Actions: build (ubuntu-latest, 3.11) GitHub Actions: build (ubuntu-latest, 3.10) GitHub Actions: build (ubuntu-latest, 3.9) GitHub Actions: build (ubuntu-latest, 3.8) ✅ No checks have passed 0/30 successful checks

#20 Add architecture diagram Pull request opened by davidmirror-ops flyteorg/static-resources ✅ All checks have passed 2/2 successful checks

#3696 [Core feature] Add execution id as an available log parameter for log links UI Issue created by btang-stripe Motivation: Why do you think this is important? We want to integrate other products with Flyte and be able to link to the logs. Specifically we'd like to link to wandb which requires an identifier created at runtime. Using the Flyte execution id as a wand group id would allow us to create the log link Goal: What should the final outcome look like, ideally? the execution id of the workflow should be available as a log parameter Describe alternatives you've considered Providing the ability to pass arbitrary strings as log parameters would be ideal, then we could pull the actual wandb run id instead. This, however, would not be as straight forward as passing the Flyte execution id. Propose: Link/Inline OR Additional context Currently the plugin machinery does not have the execution id. Talking with @Ketan (kumare3) this should be updated here and here 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/flyteconsole/tree/master|master>

by ursucarina

<https://github.com/flyteorg/flyteconsole/commit/333940fc55c0346e461759be76396c3d16f7f5cc|333940fc>

- chore: add item when mapped task (#761) flyteorg/flyteconsole

#566 Revert conditional setting of SecurityContext when launching security context Pull request opened by wild-endeavor TL;DR This PR inadvertently removed a conditional check that only set the security context to non-nil if there were meaningful values. The downstream

MergeIntoExecConfig

function relies on the nil-ness as an indication that something needs to be down. 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 Possibly related to: https://flyte-org.slack.com/archives/CP2HDHKE1/p1684415744068949 flyteorg/flyteadmin GitHub Actions: Integration Test / Integration tests GitHub Actions: End2End Test / End to End tests ✅ 6 other checks have passed 6/8 successful checks

1 new commit pushed to

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

by wild-endeavor

<https://github.com/flyteorg/flyteadmin/commit/313ac294ac18fd70f90e9605e6a3f5544b69427c|313ac294>

- revert conditional set and add tests (#566) flyteorg/flyteadmin

#762 Bug: union val missing for LP relaunch Pull request opened by FrankFlitton TL;DR Fixed parsing for a more verbose variant of the union data type in the relaunch modal's parsers. This data structure is present on the first relaunch. 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 Added a check to see if the input value is nested and pass the child nested value to the parser. Tracking Issue fixes flyteorg/flyte#3690 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

1 new commit pushed to

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

by hamersaw

<https://github.com/flyteorg/flytepropeller/commit/33ca38cf0c1c311e4b2eb46d803a92c95e8c103f|33ca38cf>

- Use correct k8 client (#563) flyteorg/flytepropeller

1 new commit pushed to

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

by wild-endeavor

<https://github.com/flyteorg/flyteidl/commit/21107f5fcb69cd685b435542dca2f913a7f52480|21107f5f>

- Single literal in GetDataResponse (#404) flyteorg/flyteidl

Release - v1.5.6 New release published by flyte-bot Changelog • 21107f5 Single literal in GetDataResponse (#404) flyteorg/flyteidl