Release - v1.8.5 New release published by flyte-bot 1.8.5 (2023-06-21) Bug Fixes • launch plan icon (#777) (4b57956) flyteorg/flyteconsole

#778 Carina/collectionfix Pull request opened by ursucarina TL;DR Relaunch workflow form fixes 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 Relaunch form fixes: • adds support for Collection type with union subtypes • theme pollution on opening the dialog flyteorg/flyteconsole Codecov: 65.79% (-0.01%) compared to 4b57956 Codecov: 50.00% of diff hit (target 65.80%) GitHub Actions: Build & Push FlyteConsole Image GitHub Actions: Get Release Tag GitHub Actions: Generate Release ✅ 6 other checks have passed 6/11 successful checks

#1004 Docs/3786 Pull request opened by cosmicBboy First change towards #3786. Merging this PR to a

docs-simplify

branch so we can test and refine the migration approach. In summary, this PR moves all the

core/flyte_basics

code to a new directory

examples/basics

, which is the first step to flattening the example directory structure and making each directory its own stand-alone flyte project. flyteorg/flytesnacks GitHub Actions: Publish artifacts to github release GitHub Actions: Create Prerelease GitHub Actions: Bump Version GitHub Actions: Serialize & Register Flytesnacks workflow / Register example to sandbox GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/kubernetes/ray_example) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/kubernetes/pod) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/kubernetes/kftensorflow) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/kubernetes/kfpytorch) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/kubernetes/kfmpi) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/kubernetes/k8s_spark) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/kubernetes/k8s_dask) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/gcp/bigquery) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/flytekit_plugins/whylogs_examples) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/flytekit_plugins/sql) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/flytekit_plugins/papermilltasks) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/flytekit_plugins/pandera_examples) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/flytekit_plugins/onnx_examples) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/flytekit_plugins/modin_examples) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/flytekit_plugins/mlflow_example) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/flytekit_plugins/greatexpectations) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/flytekit_plugins/duckdb_examples) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/flytekit_plugins/dolt) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/flytekit_plugins/dbt_example) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/external_services/databricks) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/aws/sagemaker_training) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/aws/sagemaker_pytorch) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/aws/batch) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/aws/athena) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/examples/basics) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/core) ✅ No checks have passed 0/30 successful checks

#1703 Fixes a bug in Union types Pull request opened by kumare3 TL;DR Union types iterate through all variants to find the right fit. The non right fits should raise an error to prevent the wrong cast. Today some type transfomers blindly tranform, this is ok for protobuf supported typed, but for pickle, none this is a problem. 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 flyteorg/flytekit 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) GitHub Actions: Docs Warnings ✅ 2 other checks have passed 2/26 successful checks

#1408 Remove placeholders in secrets Pull request opened by jeevb Signed-off-by: Jeev B jeev.balakrishnan@freenome.com flyteorg/flyte ✅ All checks have passed 6/6 successful checks

#779 feat/nav phase 2 Pull request opened by etdotal Description This PR adds classes to side navigation component for given abiity to override styles by referencing them by classnames flyteorg/flyteconsole GitHub Actions: Build & Push FlyteConsole Image GitHub Actions: Get Release Tag GitHub Actions: Generate Release GitHub Actions: unit_tests_with_coverage DCO: DCO ✅ 4 other checks have passed 4/9 successful checks

#3794 [BUG] Map Tasks when using min_success_ratio should fail registration if output isn't Optional #3542 Issue created by EngHabu Describe the bug Using a map task like this:

@task
def some_task(inputs: typing.List[int]) -> int:
  ...

@workflow
def my_wf() -> typing.List[int]
  return map_task(some_task, min_success_ratio=0.5)(inputs=[1, 2, 3, 4])

if some of the items fail to process, the resulting output will have shorter length compared to the input list. This is confusing! Expected behavior The task either fails to register because the output should have been

Optional[int]

or the map task should fail completely because it can't "correctly" produce the output.. 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

#1705 add private registry support Pull request opened by RichhLi TL;DR Add support for pushing/pulling from private registries when using ImageSpec. I submitted a pr to envd devs that enabled this feature: tensorchord/envd#1680 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, ImageSpec

image_spec = ImageSpec(packages=["numpy"], base_image="private_base_image", registry="private_registry", registry_config="registry_config.json")

@task(container_image=image_spec)
def t1() -> str:
    import numpy as np
    print("task 1")
    print(np.array([1,2,3]))
    return("blah1")

@workflow
def wf():
    t1()

Tracking Issue NA Follow-up issue NA flyteorg/flytekit ✅ All checks have passed 30/30 successful checks

2 new commits pushed to

<https://github.com/flyteorg/flyte-conference-talks/tree/main|main>

by samhita-alla

<https://github.com/flyteorg/flyte-conference-talks/commit/ed0f60a496228b9311c2c0177e9784274afd83db|ed0f60a4>

- updates to code

<https://github.com/flyteorg/flyte-conference-talks/commit/cbcf3e92b198981b88ee72f2cff582f26d061d01|cbcf3e92>

- Merge remote-tracking branch 'origin/main' flyteorg/flyte-conference-talks

1 new commit pushed to

<https://github.com/flyteorg/community/tree/main|main>

by davidmirror-ops

<https://github.com/flyteorg/community/commit/0220cda54783a0315345b662edce12ba65495d71|0220cda5>

- Add presentation schedule flyteorg/community

1 new commit pushed to

<https://github.com/flyteorg/community/tree/main|main>

by davidmirror-ops

<https://github.com/flyteorg/community/commit/9c1a9a842cc7f4451fa8a953d33426292dcc0464|9c1a9a84>

- Add presentation schedule link flyteorg/community

#1700 PR into #1679 - Support for generalized container types and clean-up of promise.py and workflow.py in local execution Pull request opened by wild-endeavor on <!date^1687289828^{date_short}|2023-06-20T19:37:08Z> This is a PR into #1679 (currently this PR is a bit hard to follow because it merged in master, hopefully that gets easier once it's merged) Blocked This PR is currently blocked - it's unclear if the current approach works. Currently the new dataclass transformer in the main PR interprets a dataclass as a literalmap type with a

map_value_type

set to an empty

LiteralType()

. This makes the compiler think that no bindings are needed. Since dataclasses are inherently multi-variate, we're at a bit of a impasse. And this PR depends on that. If this approach is untenable, most of this PR should be discarded. (The parts that should be retained are in the Other issues below.) One possible way around this is to make the new dataclass transformer follow the pattern of the existing dataclass json transformer - just expose a scalar, and only interpret the Background There's a few places in flytekit core today that blur the line between the type engine and not type engine. These are: • Extraction of literals from nested promises (

translate_inputs_to_literals

) for local execution • Extraction of literals from nested promises for local workflow execution (

ensure_literal

) • Construction of literals in pyflyte run (one example), there are many others in the file. This PR attempts to resolve the first two by • Merging the logic for the first two and moving to the type engine. • Generalizing what it means to be a container type (see the test here to see more clearly what that implies), • Remove

isinstance(..., list)

and

isinstance(..., dict)

• Adding three new functions to the type transformer: •

is_container_type

(returns bool) •

flyte_container_type

(returns LiteralCollection or LiteralMap) •

traverse

(responsible for appropriately walking the structure of the container and returning one of two generators. •

ListGen = typing.Generator[typing.Tuple[typing.Any, typing.Type[T], _type_models.LiteralType], None, None]

•

MapGen = typing.Generator[typing.Tuple[str, typing.Any, typing.Type[T], _type_models.LiteralType], None, None]

(Some code has also been left in place to allow

flyte_container_type

to return Scalar.) Other issues In addition to merging the two very related calls (

ensure_literal

and

extract_value

), some other bugs/issues uncovered: • the handling of unions in the

extract_value

subroutine was not correct but

ensure_literal

was correct. • we were not correctly walking bindings when the binding was a list or map. That is, if you do

x = t1()
    y = t2(a={"key1": x})

the

t1

node would not have been listed as an upstream node of

n1

flyteorg/flytekit GitHub Actions: build-plugins (3.11, flytekit-sqlalchemy) 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-hive) GitHub Actions: build-plugins (3.11, flytekit-dolt) GitHub Actions: build-plugins (3.11, flytekit-deck-standard) 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-snowflake) GitHub Actions: build-plugins (3.10, flytekit-ray) GitHub Actions: build-plugins (3.10, flytekit-papermill) ✅ 13 other checks have passed 13/30 successful checks

#1706 Remove ensure literal Pull request opened by wild-endeavor TL;DR The ensure_literal call in workflow.py was a duplicate that we just didn't realize was a duplicate. Removing and updating the existing function in promise with the correct union handling behavior. 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 was discovered while implementing the now-defunct #1700 Tracking Issue NA flyteorg/flytekit 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: lint 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) GitHub Actions: docs GitHub Actions: Docs Warnings ✅ 2 other checks have passed 2/27 successful checks

#1005 Increase memory of horovod_train_task Pull request opened by pingsutw horovod_train_task failed because of OOM 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

#1707 fix upstream nodes Pull request opened by wild-endeavor TL;DR Upstream nodes were not correctly being detected in cases where the inputs were behind a {} or a []. For example,

n1

here

def my_wf(a: int, b: str) -> (int, str):
    x, y = t1(a=a)
    d = t2(a={"key1": b, "key2": y})
    return x, d

would not have picked up

n0

as an upstream node because we weren't correctly traversing the structure. Found while implementing the now rejected generalized container types https://github.com/flyteorg/flytekit/pull/1700/files 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 Instead of iterating through the kwargs again, save nodes found while traversing the bindings from the promises. Tracking Issue NA flyteorg/flytekit 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) GitHub Actions: lint GitHub Actions: Docs Warnings ✅ 2 other checks have passed 2/17 successful checks

#1006 move all examples to new structure Pull request opened by cosmicBboy This PR moves all examples to the new docs structure • Userguide: https://flyte--1006.org.readthedocs.build/projects/cookbook/en/1006/userguide.html • Tutorials: https://flyte--1006.org.readthedocs.build/projects/cookbook/en/1006/tutorials.html • Integrations: https://flyte--1006.org.readthedocs.build/projects/cookbook/en/1006/integrations.html flyteorg/flytesnacks ✅ All checks have passed 30/30 successful checks

1 new commit pushed to

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

by wild-endeavor

<https://github.com/flyteorg/flyteadmin/commit/9b22c0e12b858ff6e6accb5e415b83cb3df62ee8|9b22c0e1>

- Add a user-specifiable root to upload link request (#577) flyteorg/flyteadmin

1 new commit pushed to

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

by jsonporter

<https://github.com/flyteorg/flyteconsole/commit/007e63605be094b3efee8fb0bddee5a266e8b16a|007e6360>

- WIP: Add localStorage for selected Project/Domain (#774) flyteorg/flyteconsole

#3797 [UI Feature] Can't trigger an execution from the launch plan page Issue created by katrogan Motivation: Why do you think this is important? I wanted to find and launch a specific launch plan but there's no way to from the console "Launch Plans" details page for a specific launch plan Goal: What should the final outcome look like, ideally? It should be possible to trigger an execution once you've landed on details for a specific launch plan 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

#1708 Remove ensure literal Pull request opened by pingsutw 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 GitHub Actions: docs ✅ 2 other checks have passed 2/3 successful checks

Release - v1.1.106 New release published by flyte-bot Changelog • 9b22c0e Add a user-specifiable root to upload link request (#577) flyteorg/flyteadmin

1 new commit pushed to

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

by pingsutw

<https://github.com/flyteorg/flytesnacks/commit/d641c106b404cb3663199dede7a153c0eaa4cca8|d641c106>

- Increase memory of horovod_train_task (#1005) flyteorg/flytesnacks

Release - flytesnacks v0.3.204 New release published by flyte-bot Changelog • d641c10 Increase memory of horovod_train_task (#1005) flyteorg/flytesnacks

#1007 Update Athena example Pull request opened by pingsutw Athena writes output to a CSV file, but Flyteschema cannot read CSV file, so the dataframe is always empty. We should replace FlyteSchema with Structured dataset. Temporarily update

df[df.total_vaccinations.notnull()]

to

df

, so the example can work. 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

#3798 [BUG] Athena task cache miss Issue created by pingsutw Describe the bug When re-running the same Athena task, Propeller doesn't read the data from the cache and still reruns the task. Expected behavior Tasks should also be cached. Additional context to reproduce Athena task. https://github.com/flyteorg/flytesnacks/blob/d641c106b404cb3663199dede7a153c0eaa4cca8/cookbook/integrations/aws/athena/athena.py#L77-L93 Screenshots Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte

#1709 Fail registration if output isn't Optional when using map tasks with min_success_ratio &lt; 1 Pull request opened by pingsutw TL;DR Fixes flyteorg/flyte#3794. Fail registration if output isn't Optional when using map tasks with min_success_ratio < 1 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 flyteorg/flyte#3794 Follow-up issue NA flyteorg/flytekit 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: lint 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) GitHub Actions: Docs Warnings GitHub Actions: docs ✅ 2 other checks have passed 2/26 successful checks

#1008 Partial task support docs Pull request opened by samhita-alla This PR includes documentation updates for partial tasks, covering both map tasks and basic tasks. Fixes flyteorg/flyte#3603 & flyteorg/flyte#3604 flyteorg/flytesnacks GitHub Actions: Build & Push to GHCR (cookbook/integrations/flytekit_plugins/pandera_examples) GitHub Actions: Build & Push to GHCR (cookbook/integrations/flytekit_plugins/onnx_examples) GitHub Actions: Build & Push to GHCR (cookbook/integrations/flytekit_plugins/modin_examples) GitHub Actions: Build & Push to GHCR (cookbook/integrations/flytekit_plugins/mlflow_example) GitHub Actions: Build & Push to GHCR (cookbook/integrations/flytekit_plugins/greatexpectations) GitHub Actions: Build & Push to GHCR (cookbook/integrations/flytekit_plugins/duckdb_examples) GitHub Actions: Build & Push to GHCR (cookbook/integrations/flytekit_plugins/dolt) GitHub Actions: Build & Push to GHCR (cookbook/integrations/flytekit_plugins/dbt_example) GitHub Actions: Build & Push to GHCR (cookbook/integrations/external_services/databricks) GitHub Actions: Build & Push to GHCR (cookbook/integrations/aws/sagemaker_training) GitHub Actions: Build & Push to GHCR (cookbook/integrations/aws/sagemaker_pytorch) GitHub Actions: Build & Push to GHCR (cookbook/integrations/aws/batch) GitHub Actions: Build & Push to GHCR (cookbook/integrations/aws/athena) GitHub Actions: Build & Push to GHCR (cookbook/core) GitHub Actions: Build & Push to GHCR (cookbook/case_studies/ml_training/spark_horovod) GitHub Actions: Build & Push to GHCR (cookbook/case_studies/ml_training/pima_diabetes) GitHub Actions: Build & Push to GHCR (cookbook/case_studies/ml_training/nlp_processing) GitHub Actions: Build & Push to GHCR (cookbook/case_studies/ml_training/mnist_classifier) GitHub Actions: Build & Push to GHCR (cookbook/case_studies/ml_training/house_price_prediction) GitHub Actions: Build & Push to GHCR (cookbook/case_studies/feature_engineering/feast_integration) GitHub Actions: Build & Push to GHCR (cookbook/case_studies/feature_engineering/eda) GitHub Actions: Build & Push to GHCR (cookbook/case_studies/bioinformatics/blast) GitHub Actions: Docs Warnings ✅ 3 other checks have passed 3/26 successful checks

#3799 [Docs] Update the plugin setup guide Issue created by samhita-alla Description Our existing plugin setup guide provides instructions for the Flyte sandbox environment but does not cover the Flyte demo cluster. To address this issue, we need to: • Install plugins on the demo cluster. • Enhance the plugin setup guide by incorporating detailed, user-friendly instructions that are more explicit and comprehensive in nature. Key points to ponder: • Can plugins be installed on the demo cluster? • Is the web API plugins guide necessary in light of Flyte agents' functionality? Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte

#3800 [BUG] pyflyte serialize --image doesn't handle image names Issue created by cosmicBboy Describe the bug Specifying

--image name=<image_uri>

raises and error in a

pyflyte serialize

invocation:

Failed with Unknown Exception <class 'docker_image.reference.ReferenceInvalidFormat'> Reason: invalid reference format

pyflyte package

can handle this format. Expected behavior

pyflyte serialize

should have the same behavior as

pyflyte package

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

#580 Bump propeller version Pull request opened by pingsutw TL;DR Bump propeller version to reflect this change 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/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