#1009 Using the auto config loader for flyteremote example Pull request opened by pmahindrakar-oss Currently the example tries to construct a config providing the endpoint name in flyte remote. Instead it can directly rely on the config already used by flytekit, flytectl eg : ~/.flyte/config.yaml which already knows how to connect to the flyte endpoint. Tested using the following example

from flytekit.remote import FlyteRemote
from flytekit.configuration import Config
from flytekit import LaunchPlan
from flytekit.configuration import get_config_file

# FlyteRemote object is the main entrypoint to API
remote = FlyteRemote(
    config=Config.auto(),
    default_project="flytesnacks",
    default_domain="development",
)

# Fetch launch plan
flyte_lp = remote.fetch_launch_plan(
    name="core.flyte_basics.lp.go_greet", version="v0.3.203", project="flytesnacks", domain="development"
)

# Execute
execution = remote.execute(
    flyte_lp, inputs={"day_of_week": "Sun", "number": 1}, execution_name="executionname", wait=True

flyteorg/flytesnacks 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/core) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/case_studies/ml_training/spark_horovod) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/case_studies/ml_training/pima_diabetes) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/case_studies/ml_training/nlp_processing) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/case_studies/ml_training/mnist_classifier) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/case_studies/ml_training/house_price_prediction) ✅ No checks have passed 0/30 successful checks

#780 Fix project selector failing test Pull request opened by FrankFlitton TL;DR A chart.js import was causing the jest tests to fail. 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 Moved a way from

registerables

helper to importing the full list to the verbose syntax here: https://www.chartjs.org/docs/3.6.2/getting-started/integration.html From some light reading it seems like

registrablables

may be generally buggy, even in modern releases. flyteorg/flyteconsole Codecov: 40.32% of diff hit (target 65.80%) GitHub Actions: Build & Push FlyteConsole Image GitHub Actions: Get Release Tag GitHub Actions: Generate Release ✅ 7 other checks have passed 7/11 successful checks

1 new commit pushed to

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

by pmahindrakar-oss

<https://github.com/flyteorg/flytesnacks/commit/7f73fef88caec6f88789a64087675b32948ece84|7f73fef8>

- Using the auto config loader for flyteremote example (#1009) flyteorg/flytesnacks

1 new commit pushed to

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

by davidmirror-ops

<https://github.com/flyteorg/community/commit/4fca09bf9d381be6f51580ee8401c088a1f2f9a6|4fca09bf>

- Add minutes files flyteorg/community

1 new commit pushed to

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

by jsonporter

<https://github.com/flyteorg/flyteconsole/commit/e2fd2a48dd6d56aca73c90f3e18492b55f77df58|e2fd2a48>

- Fix project selector failing test (#780) flyteorg/flyteconsole

#579 real time deck support Pull request opened by Yicheng-Lu-llll TL;DR This PR adds real-time deck support. Previously: 1. Propeller would only send a node event to the admin when there was a change in the node state (e.g., from 'Queued' to 'Running', or from 'Running' to 'Succeeding'). 2. The deck URI was only added to the node event if the URI existed in remote storage(S3) and the task had succeeded. 3. If deck URI is in node event, the deck URI would be stored in the admin and later fetched by the console. With this PR: 1. Propeller will continue to send node events to the admin upon any changes in node state. 2. Propeller will now always add the deck URI to the event at non-final state(like at running time, so it is possible deck uri actually does not exist). 3. Once the task is in final state(succeeded or failed), deck URI will be removed in node event if not exists. 4. the deck URI will be stored in the admin and fetched by the console, even while the task is running. During running time, it is possible the deck URI is stored though actually not exists. But once the task is finished, deck URI will be removed if not exists. Why not only add deck URI to event when the URI exists? Due to constraints within Propeller, we cannot determine if a user has enabled deck or when they will upload the deck.html to remote storage. Therefore, without constantly checking the existence of the URI at every reconciliation (which would be too costly), it's impossible to know when the URI becomes available. More details As node events are only sent when the node state changes, the only chance we have to send the deck URI with the event is when the state changes from 'Queued' to 'Running'. As explained above, it is not feasible to send additional events once the deck URI exists, as we cannot accurately determine when the URI will become available. Checks and behaviors 1. Running a task with deck disabled. Deck URI should appears during the task running time but will not shown when task succeeded or failed. • running: - succeeded: - failed: 3. Running a task with deck enabled. Deck URI should appears during the task running time as well as when task succeed or failed. • running: - succeeded: - failed: real time deck support includes: • flytekit: flyteorg/flytekit#1704 • flyteadmin: flyteorg/flyteadmin#579 • flytepropeller: #579 • flyteconsole: flyteorg/flyteconsole#781 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/flytepropeller ✅ All checks have passed 2/2 successful checks

#579 real time deck support Pull request opened by Yicheng-Lu-llll TL;DR This PR: 1. stores DeckUri at task running stage to support real-time deck. with flyteorg/flytepropeller#579, propeller can send node event with deck uri at running time, So, admin needs to also store the DeckUri inomation. 2. In the CreateDownloadLink method, ensure to verify the existence of the URL prior to generating a signed URL. The console invokes CreateDownloadLink to convert the native deck URI into a signed URI. As indicated in FlytePropeller Pull Request #579, the deck URI may not exist yet, necessitating this validation step. real time deck support includes: • flytekit: flyteorg/flytekit#1704 • flyteadmin: #579 • flytepropeller: flyteorg/flytepropeller#579 • flyteconsole: flyteorg/flyteconsole#781 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/flyteadmin ✅ All checks have passed 2/2 successful checks

#234 [Snyk] Upgrade org.scala-lang:scala-reflect from 2.12.11 to 2.13.11 Pull request opened by EngHabu This PR was automatically created by Snyk using the credentials of a real user. Snyk has created this PR to upgrade org.scala-lang:scala-reflect from 2.12.11 to 2.13.11. ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project. * * * • The recommended version is 36 versions ahead of your current version. • The recommended version was released 22 days ago, on 2023-06-02. * * * Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs. For more information: https://camo.githubusercontent.com/d24913fd28a6d7c79cda4f1783fc2ad2a1a85051143f0222c261ddbc7b909810/68747470733a2f2f6170692e7365676d656e742e696f2f76312f706978656c2f747261636b3f646174613d65794a33636d6c305a55746c65534936496e4a79576d785a634564485932527954485a7362306c596430645563566734576b4652546e4e434f5545774969776959573576626e6c746233567a535751694f6949305a6a686a5a446b344d7931685954457a4c5451774d574574595451314d53316c5a574e684d6a63334d544e6a4d7a55694c434a6c646d567564434936496c425349485a705a58646c5a434973496e42796233426c636e52705a584d694f6e736963484a4a5a434936496a526d4f474e6b4f54677a4c5746684d544d744e444178595331684e4455784c57566c593245794e7a63784d324d7a4e534a3966513d3d 🧐 View latest project report 🛠️ Adjust upgrade PR settings 🔕 Ignore this dependency or unsubscribe from future upgrade PRs flyteorg/flytekit-java GitHub Actions: build-snapshot DCO: DCO ✅ 1 other check has passed 1/3 successful checks

#1704 Real time deck support Pull request opened by Yicheng-Lu-llll TL;DR This PR adds real-time deck support. After this PR, User can use

flytekit.Deck.persist()

to generate the html based on current collected metrics/information. So that user can see the real time deck even the task is running or has already failed. See the below example:

import flytekit
from flytekit import Resources, task, workflow
from flytekit.core.utils import timeit

@task(
    disable_deck=False,
    limits=Resources(mem="4Gi", cpu="1"),
)
def t1():
    import time

    for i in range(2):
        # timeit measure the time used in the block and shown in time line deck. See <https://github.com/flyteorg/flytekit/pull/1581>. 
        # Or you can add information to your own deck. See <https://docs.flyte.org/projects/cookbook/en/latest/auto/core/flyte_basics/deck.html>.
        with timeit(f"iteration {i}"):
            time.sleep(50)
        flytekit.Deck.persist()


@workflow
def wf():
    t1()


if __name__ == "__main__":
    wf()

real time deck support includes: • flytekit: #1704 • flyteadmin: flyteorg/flyteadmin#579 • flytepropeller: flyteorg/flytepropeller#579 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: build-plugins (3.11, flytekit-snowflake) GitHub Actions: build-plugins (3.11, flytekit-papermill) GitHub Actions: build-plugins (3.11, flytekit-pandera) 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-duckdb) GitHub Actions: build-plugins (3.11, flytekit-dolt) GitHub Actions: build-plugins (3.11, flytekit-aws-athena) GitHub Actions: build-plugins (3.10, flytekit-ray) ✅ 20 other checks have passed 20/30 successful checks

#1710 Add Iterator Transformer Pull request opened by pingsutw TL;DR Add support using

typing.Iterator

in the type annotation 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 ✅ All checks have passed 30/30 successful checks

#1711 Improve task type hint Pull request opened by pingsutw TL;DR Before: After: 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 ✅ All checks have passed 30/30 successful checks

#3802 [Housekeeping] Show warning or error message if GOPATH environment variable is not set Issue created by shekhar-kotekar Describe the issue On Mac M1 system, golang is installed using

brew install go

command which apparently does not bother exporting

GOPATH

environment variable. So if we try to build Flyte code from the source,

make compile

command fails with below error.

<http://github.com/flyteorg/flyte/cmd|github.com/flyteorg/flyte/cmd>
mv ./flyte /bin || echo "Skipped copying 'flyte' to /bin"
mv: fastcopy: open() failed (to): /bin/flyte: Operation not permitted
Skipped copying 'flyte' to /bin

Below line in

Makefile

is using

GOPATH

environment variable.

mv ./flyte ${GOPATH}/bin || echo "Skipped copying 'flyte' to ${GOPATH}/bin"

This is not a show stopper but we can simply check if this environment variable is set and handle the error accordingly. What if we do not do this? We have to set

GOPATH

environment variable and then retry

make compile

command. 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

#235 [Snyk] Upgrade org.scala-lang:scala-library from 2.13.10 to 2.13.11 Pull request opened by eapolinario This PR was automatically created by Snyk using the credentials of a real user. Snyk has created this PR to upgrade org.scala-lang:scala-library from 2.13.10 to 2.13.11. ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project. * * * • The recommended version is 3 versions ahead of your current version. • The recommended version was released 24 days ago, on 2023-06-02. * * * Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs. For more information: https://camo.githubusercontent.com/0f82a581a29d3ed0de25371673cd64a4e59aa9fcb9bac189a8af35fe07b45105/68747470733a2f2f6170692e7365676d656e742e696f2f76312f706978656c2f747261636b3f646174613d65794a33636d6c305a55746c65534936496e4a79576d785a634564485932527954485a7362306c596430645563566734576b4652546e4e434f5545774969776959573576626e6c746233567a535751694f6949314f44646c596a6b304d5330774f4745304c5452684d6d497459544d344f43307a5a6a6c6d5a446731593259324e7a63694c434a6c646d567564434936496c425349485a705a58646c5a434973496e42796233426c636e52705a584d694f6e736963484a4a5a434936496a55344e3256694f5451784c544134595451744e474579596931684d7a67344c544e6d4f575a6b4f44566a5a6a59334e794a3966513d3d 🧐 View latest project report 🛠️ Adjust upgrade PR settings 🔕 Ignore this dependency or unsubscribe from future upgrade PRs flyteorg/flytekit-java GitHub Actions: build-snapshot DCO: DCO ✅ 1 other check has passed 1/3 successful checks

#562 [Feature] Add multi-query Presto support Issue created by wild-endeavor Motivation: Why do you think this is important? When developing the Presto plugin, we overlooked the fact that users can't submit multiple queries within one query like they can in Hive and most other query languages. Thus the practice of setting up temp tables to stage data before a final query is not something that is easily done. We shoul further investigate this need, and amend the Presto task/plugin to be able to support this use case. Perhaps a series of related queries can be passed in per task that can be run sequentially. This brings in questions around atomicity of course. Goal: What should the final outcome look like, ideally? Support users who want to first query into a temp table, and then make a final query. Should investigate if this is possible with with statements in the current framework. Describe alternatives you've considered with statements? Flyte component ☐ Overall ☐ Flyte Setup and Installation scripts ☐ Flyte Documentation ☐ Flyte communication (slack/email etc) ☐ FlytePropeller ☐ FlyteIDL (Flyte specification language) ☑︎ Flytekit (Python SDK) ☐ FlyteAdmin (Control Plane service) ☑︎ FlytePlugins ☐ DataCatalog ☐ FlyteStdlib (common libraries) ☐ FlyteConsole (UI) ☐ Other [Optional] Propose: Link/Inline If you have ideas about the implementation please propose the change. If inline keep it short, if larger then you link to an external document. Additional context Add any other context or screenshots about the feature request here. Is this a blocker for you to adopt Flyte Please let us know if this makes it impossible to adopt Flyte flyteorg/flyte

#555 [Feature] Access control on who can run/view workflows Issue created by senthilnathan23 Motivation: Why do you think this is important? We want to have better access control over who can run/view workflows. Currently this is blocker to create any critical pipelines on Flyte. Goal: What should the final outcome look like, ideally? Flyte UI/CLI: Should allow certain list of users to view/run the workflows. This could be configured through the code. Describe alternatives you've considered There are no alternatives at this point to overcome this. Flyte component ☑︎ Overall ☐ Flyte Setup and Installation scripts ☐ Flyte Documentation ☐ Flyte communication (slack/email etc) ☐ FlytePropeller ☐ FlyteIDL (Flyte specification language) ☐ Flytekit (Python SDK) ☐ FlyteAdmin (Control Plane service) ☐ FlytePlugins ☐ DataCatalog ☐ FlyteStdlib (common libraries) ☐ FlyteConsole (UI) ☐ Other [Optional] Propose: Link/Inline N/A Additional context N/A Is this a blocker for you to adopt Flyte This is a blocker for us to start using Flyte for our critical data pipelines. flyteorg/flyte

#283 [Feature] CodeCoverage Gate for Various components Issue created by kumare3 Motivation: Why do you think this is important? Recently I have noticed that code coverage has dropped for some of our components. We should ensure that code coverage keeps improving or atleast stays the same. Goal: What should the final outcome look like, ideally? In case a PR drops code coverage, it should not be allowed to checkin Describe alternatives you've considered Code reviews, but that is not enforceable Flyte component ☐ Overall ☐ Flyte Setup and Installation scripts ☐ Flyte Documentation ☐ Flyte communication (slack/email etc) ☑︎ FlytePropeller ☐ FlyteIDL (Flyte specification language) ☑︎ Flytekit (Python SDK) ☑︎ FlyteAdmin (Control Plane service) ☑︎ FlytePlugins ☑︎ DataCatalog ☑︎ FlyteStdlib (common libraries) ☑︎ FlyteConsole (UI) ☐ Other [Optional] Propose: Link/Inline NA Additional context NA Is this a blocker for you to adopt Flyte No, but as a contributor my confidence will improve to checkin new code. flyteorg/flyte

#365 Pass location to the BigQuery request Pull request opened by pingsutw TL;DR Failed to get the BigQuery job status because we didn't pass the location config to the BibQuery request. 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/p1683133259253529 Follow-up issue NA flyteorg/flyteplugins Codecov: 50.00% of diff hit (target 64.05%) Codecov: 62.75% (-1.31%) compared to dfdf6f9 ✅ 5 other checks have passed 5/7 successful checks

1 new commit pushed to

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

by pingsutw

<https://github.com/flyteorg/flytekit/commit/d7bfa6e9b047678dda1c4baed53260bf5d6c138d|d7bfa6e9>

- Fix config of user facing execution parameters in spawning elastic tasks (#1677) flyteorg/flytekit

#3803 [BUG] Fix visual subworkflow graph expansion Issue created by victorchurikovcommonground Describe the bug There is an issue with subworkflows expansion in graph when they are too big, about half the time they collapse like this: This is how it looks when it occasionally succeeds: This is how it looks before I expand it: It alternates between the full and collapsed view rapidly before settling on one or the other after 2-3 seconds Expected behavior I expect the workflow to eventually settle on the full expanded view even if it takes a while to load it Additional context to reproduce 1. Create a workflow 2. Call another workflow from your workflow (preferably a dynamic one so you can create many nodes quickly) 3. Observe that it rapidly switched between the collapsed and expanded view before settling on one of them If you're not able to reproduce this with just these steps, note that each iteration of my dynamic for loop also has its own conditional with a (small) dynamic inside of it, maybe the issue is dynamic in dynamic, or conditionals in dynamics, not sure. Screenshots Screenshots attached in the bug description Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte

#578 Alter ID sequence to bigint Pull request opened by honnix TL;DR Alter ID sequence to bigint. 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 I tested the sql on one of our sequences and it worked as expected. Complete description As described by flyteorg/flyte#3777, some of the ID sequences are not bigint due to historical reason. It makes sense to use bigint because integer is easy to run out of. Note that this PR does not try to change

cycle

in order to keep backward compatibility, and also

bigint

will practically make that unnecessary. For reference https://www.postgresql.org/docs/current/sql-altersequence.html Tracking Issue Fixes flyteorg/flyte#3777 Follow-up issue NA flyteorg/flyteadmin GitHub Actions: Goreleaser GitHub Actions: Build & Push Flyteadmin Image GitHub Actions: Build & Push Flytescheduler Image GitHub Actions: Bump Version Codecov: 0.00% of diff hit (target 58.60%) Codecov: 58.58% (-0.03%) compared to 949f5a2 ✅ 8 other checks have passed 8/14 successful checks

#1010 clean up cruft Pull request opened by cosmicBboy This is the final PR that fixes #3786 flyteorg/flytesnacks GitHub Actions: Build & Push Example Image to GHCR (cookbook/examples/dbt_plugin) GitHub Actions: Build & Push Example Image to GHCR (cookbook/examples/databricks_plugin) GitHub Actions: Build & Push Example Image to GHCR (cookbook/examples/control_flow) GitHub Actions: Build & Push Example Image to GHCR (cookbook/examples/containerization) GitHub Actions: Build & Push Example Image to GHCR (cookbook/examples/blast) GitHub Actions: Build & Push Example Image to GHCR (cookbook/examples/bigquery_plugin) GitHub Actions: Build & Push Example Image to GHCR (cookbook/examples/basics) GitHub Actions: Build & Push Example Image to GHCR (cookbook/examples/aws_batch_plugin) GitHub Actions: Build & Push Example Image to GHCR (cookbook/examples/athena_plugin) ✅ 3 other checks have passed 3/12 successful checks

1 new commit pushed to

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

by hamersaw

<https://github.com/flyteorg/flyteadmin/commit/f44d7feedd3158941a409f0da3cc03aa47dc373b|f44d7fee>

- Bump propeller version (#580) flyteorg/flyteadmin

Pending review on flyteorg/flyteplugins - Manage reminder [#347] Fix double http in the Spark Driver UI Link (mucahitkantepe) a month stale · 2 months old · Waiting on _ pingsutw_

Pending review on flyteorg/flytekit-java - Manage reminder [#6] Update .env.local in README (kanterov) a year stale · 3 years old · Waiting on _ @Ketan (kumare3)_

[#59] [Snyk] Security upgrade alpine from 3.16 to 3 (snyk-bot) 20 days stale · 20 days old · Waiting on _ @Haytham Abuelfutuh, @Ketan (kumare3)_

1 new commit pushed to

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

by hamersaw

<https://github.com/flyteorg/flytepropeller/commit/7b104d335d6fc41684217ce99781390cbd74cf84|7b104d33>

- propagating environment variables through launchplans (#576) flyteorg/flytepropeller

Release - v1.1.107 New release published by flyte-bot Changelog • f44d7fe Bump propeller version (#580) flyteorg/flyteadmin

1 new commit pushed to

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

by wild-endeavor

<https://github.com/flyteorg/flytekit/commit/aedd721c9b4dbc70c458b99d9e575b3b173e5235|aedd721c>

- Union | optional return types supported (#1703) flyteorg/flytekit

#3319 [BUG] OneHotEncoder type not supported as task input when None is supplied as input value. Issue created by xshen8888 Describe the bug The task’s input is of type sklearn.preprocessing.OneHotEncoder. It is either supplied by the caller or None if user doesn’t have a encoder instance as input (in which case the task code will get it from an offline storage location). I tried both, with or without Optional.

@task
def transform(encoder: Optional[OneHotEncoder] = None, ...)
def transform(encoder: OneHotEncoder = None, ...)
When caller do transform(encoder=None, ...), the task will work successfully with pyflyte run (locally).
However, if I bake the module containing the task estimate() into an image and refer to it in a pyflyte remote run, no mater what I do, I keep getting at the terminal (before pyflyte submit the code to remote flyte server):
flytekit/core/type_engine.py", line 1060, in to_literal
    raise TypeError("Ambiguous choice of variant for union type")
...
flytekit/core/promise.py", line 937, in create_and_link_node
    raise AssertionError(f"Failed to Bind variable {k} for function {entity.name}.") from e
AssertionError: Failed to Bind variable **_encoder_** for function dai_mle_models.onehotenc.simple_onehotenc. transform.

Expected behavior The task should run remotely just like when None is supplied to pandas.DataFrame as task input value (which I have verified working). e.g.

@task
def sometask(test_data: pd.DataFrame = None, ...)

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

Release - v1.1.99 New release published by flyte-bot Changelog • 7b104d3 propagating environment variables through launchplans (#576) flyteorg/flytepropeller