flyte-org #flyte-github

GitHub

05/24/2023, 12:30 AM

#1654 Support single literals in tiny url Pull request opened by wild-endeavor TL;DR Bump flyteidl and add the ability to return individual elements. 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 Also removed single dispatch. flyteorg/flytekit Codecov: 71.00% (-0.02%) compared to d7060cc Codecov: 0.00% of diff hit (target 71.02%) ✅ 28 other checks have passed 28/30 successful checks

GitHub

05/24/2023, 12:41 AM

1 new commit pushed to

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

by hamersaw

<https://github.com/flyteorg/flyteplugins/commit/7bb490f8c5dc4370fceb0c80a564f09b79342c2a|7bb490f8>

- updating dask plugin to use container resources with overrides (#351) flyteorg/flyteplugins

GitHub

05/24/2023, 12:58 AM

#405 [Snyk] Security upgrade requests from 2.27.1 to 2.31.0 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 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/978d929ce2999c79d81c240876c2840953f75982b5f78640e6512fad7026b5b2/68747470733a2f2f6170692e7365676d656e742e696f2f76312f706978656c2f747261636b3f646174613d65794a33636d6c305a55746c65534936496e4a79576d785a634564485932527954485a7362306c596430645563566734576b4652546e4e434f5545774969776959573576626e6c746233567a535751694f694a695a446b7a4d5745334e5330344e545a6c4c5451324e575174595449334d43316a5a47566b4e474d355a6a45794d5451694c434a6c646d567564434936496c425349485a705a58646c5a434973496e42796233426c636e52705a584d694f6e736963484a4a5a434936496d4a6b4f544d78595463314c5467314e6d55744e4459315a4331684d6a63774c574e6b5a575130597a6c6d4d5449784e434a3966513d3d 🧐 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: 🦉 Learn about vulnerability in an interactive lesson of Snyk Learn. flyteorg/flytectl GitHub Actions: Goreleaser GitHub Actions: Generate documentation GitHub Actions: Bump Version DCO: DCO ✅ 8 other checks have passed 8/12 successful checks

GitHub

05/24/2023, 1:17 AM

Release - v1.0.61 New release published by flyte-bot Changelog • 7bb490f updating dask plugin to use container resources with overrides (#351) flyteorg/flyteplugins

GitHub

05/24/2023, 4:29 AM

#565 Update flyteplugins from 1.0.56 to 1.0.61 #minor Pull request opened by bstadlbauer TL;DR Bumps

flyteplugins

from 1.0.56 to 1.0.61 to bring in

dask

fix from flyteorg/flyteplugins#351 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 GitHub Actions: Unit Tests / Run Unit Test GitHub Actions: Lint / Run Lint GitHub Actions: Check Go Generate / Go Generate GitHub Actions: Docker Build Images / Build Docker Image GitHub Actions: Analyze (go) ✅ 2 other checks have passed 2/7 successful checks

GitHub

05/24/2023, 4:48 AM

1 new commit pushed to

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

by pingsutw

<https://github.com/flyteorg/flytekit/commit/a21dd46b1bf19c40fdfe4b89015d910212e85b34|a21dd46b>

- Map over notebook task (#1650) flyteorg/flytekit

GitHub

05/24/2023, 4:53 AM

1 new commit pushed to

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

by samhita-alla

<https://github.com/flyteorg/flyte/commit/1a2871fb5822fef899bca0a009be973c14f65f2f|1a2871fb>

- fix typo in cluster resources doc (#3704) flyteorg/flyte

GitHub

05/24/2023, 1:02 PM

#566 bumped flyteplugins to pickup dask resource fix Pull request opened by hamersaw TL;DR See title. 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/flytepropeller GitHub Actions: Lint / Run Lint GitHub Actions: Docker Build Images / Build Docker Image GitHub Actions: Unit Tests / Run Unit Test GitHub Actions: Check Go Generate / Go Generate GitHub Actions: Analyze (go) ✅ 2 other checks have passed 2/7 successful checks

GitHub

05/24/2023, 4:53 PM

1 new commit pushed to

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

by jsonporter

<https://github.com/flyteorg/flyteconsole/commit/39c252d9fc77c7b83fc756d01810bfc91cd9470f|39c252d9>

- fix: dynamic-node-tasks (#765) flyteorg/flyteconsole

GitHub

05/24/2023, 4:54 PM

#3455 [BUG] FlyteConsole: execution detail panel task template dynamic executions Issue created by jsonporter Describe the bug User reported inconsistent behavior when dealing with dynamic executions in the detail panel (right slide-out). The first issue is that sometimes the task tab doesn't show up (it should) and then sometimes the detail are incorrect. Dynamic tasks should always have a task template and this template should be pulled from the closure (in the case of dynamics this should be the dynamic's closure) Expected behavior 1. All tasks (dynamic included) should show a task tab in the execution details panel 2. The values displayed in this the task tab should always from the execution closure. 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

GitHub

05/24/2023, 4:57 PM

1 new commit pushed to

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

by wild-endeavor

<https://github.com/flyteorg/flyteidl/commit/9d7900381b16ccd546d10f8e9851d17d8f05665b|9d790038>

- Add oauth2 http proxy client (#405) flyteorg/flyteidl

GitHub

05/24/2023, 4:57 PM

Release - v1.5.8 New release published by flyte-bot Changelog • 9d79003 Add oauth2 http proxy client (#405) flyteorg/flyteidl

GitHub

05/24/2023, 5:19 PM

#3720 [Core feature] Show FlyteDeck even when task fails Issue created by peridotml Motivation: Why do you think this is important? Users want to surface failing validation checks on data and models in Decks. For example, • Show which checks failed in pandera • A model did not pass quality checks, i.e. the model returned random results This also allows users to use Decks early in tasks that could be used for debugging. I can see someone saving summary statistics on a dataset to the Deck before training. Then when training fails, they could inspect the deck and be like "Oh lol I had 10000 columns instead of 5" Goal: What should the final outcome look like, ideally? A user will go through this flow 1. See an error was raised that says their validation check failed 2. Click on FlyteDecks 3. Look at the reasons it failed For plugins, like Pandera, the FlyteDeck cloud be built into the plugin! Describe alternatives you've considered Have the validation task succeed and then return a boolean to see if it failed. Then raise in a separate task.

Copy code

@task(container_image=python_image, disable_deck=False)
def validate_dataset(df: pd.DataFrame) -> bool:
    try:
        InputSchema.validate(df, lazy=True)
    except SchemaErrors as err:
        Deck(
            "Schema Validation Failures",
            build_table(err.failure_cases, "orange_light"),
        )
        return True

    return False

@workflow
def data_validaition_wf(valid: bool):
    df = load_dataset()
    failure = validate_dataset(df=df)
    raise_error(failure=failure) >> etl_task(df=df)

I don't like the extra steps! Propose: Link/Inline OR Additional context slack convo: https://flyte-org.slack.com/archives/CP2HDHKE1/p1684947483699369?thread_ts=1684945136.431699&cid=CP2HDHKE1 Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte

GitHub

05/24/2023, 5:20 PM

#3721 [BUG] Flyteconsole task template not showing for signal nodes Issue created by jsonporter Describe the bug Currently in

flyteconsole

the task template data is not present for signal nodes that are children of a dynamic task. This effects all node execution views (list, graph, timeline and execution detail panel) Example:

flytesnacks/development/human_in_the_loop.wf_dyn

Expected behavior Signal nodes should display their task templates. 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

GitHub

05/24/2023, 5:31 PM

Release - v1.8.3 New release published by flyte-bot 1.8.3 (2023-05-24) Bug Fixes • dynamic-node-tasks (#765) (39c252d) flyteorg/flyteconsole

GitHub

05/24/2023, 5:44 PM

#3722 Override container image by using with_overrides Issue created by jimxliu Motivation: Why do you think this is important? The

@task

wrapped function inside the container image might not be aware of the container image fqn, since the image was not created when the task was being packaged into an image layer. So having the parent task in a separate container that knows child container image fqn, override the fqn of the child container image seems the way to go. Goal: What should the final outcome look like, ideally? Parent task can override child task container image at runtime using

with_overrides(container_image='...')

. Describe alternatives you've considered Not sure if there is a workaround. Propose: Link/Inline OR Additional context Pull request: flyteorg/flytekit#1652 Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte

GitHub

05/24/2023, 6:00 PM

1 new commit pushed to

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

by wild-endeavor

<https://github.com/flyteorg/flytekit/commit/c30ccd459bc193335904f817b123ffd935908bc9|c30ccd45>

- Support single literals in tiny url (#1654) flyteorg/flytekit

GitHub

05/24/2023, 6:02 PM

1 new commit pushed to

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

by eapolinario

<https://github.com/flyteorg/flytekit/commit/67b92be90e65e39cfc21843a7e0d00ae00ec9af7|67b92be9>

- Skip grpcio 1.55.0 (#1653) flyteorg/flytekit

GitHub

05/24/2023, 6:18 PM

1 new commit pushed to

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

by wild-endeavor

<https://github.com/flyteorg/flyte/commit/0cd5ec1b7d6b04211b3ff6d59e717c8536556891|0cd5ec1b>

- Add azure ad auth setup doc (#3625) flyteorg/flyte

GitHub

05/24/2023, 6:19 PM

#3723 [Snyk] Security upgrade requests from 2.28.2 to 2.31.0 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 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 ⚠️ Warning

Copy code

sphinxext-remoteliteralinclude 0.4.0 has requirement MarkupSafe<=2.0.1; python_version < "3.8", but you have MarkupSafe 2.1.2.
Sphinx 4.5.0 requires sphinxcontrib-htmlhelp, which is not installed.
Sphinx 4.5.0 requires sphinxcontrib-applehelp, which is not installed.

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/dfd5a59f60a2278185d97df3aa3f265ab1ec2abfe5c508d2242f853c8e2b39ae/68747470733a2f2f6170692e7365676d656e742e696f2f76312f706978656c2f747261636b3f646174613d65794a33636d6c305a55746c65534936496e4a79576d785a634564485932527954485a7362306c596430645563566734576b4652546e4e434f5545774969776959573576626e6c746233567a535751694f6949784e474a6b4d5445304e43316c4e32526a4c54526b595749744f474a684e4330304d7a686b4f5749304d544a6a4d4455694c434a6c646d567564434936496c425349485a705a58646c5a434973496e42796233426c636e52705a584d694f6e736963484a4a5a434936496a4530596d51784d5451304c5755335a474d744e47526859693034596d45304c54517a4f475135596a51784d6d4d774e534a3966513d3d 🧐 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: 🦉 Learn about vulnerability in an interactive lesson of Snyk Learn. flyteorg/flyte GitHub Actions: generate_kustomize GitHub Actions: generate_helm GitHub Actions: compile GitHub Actions: docs DCO: DCO ✅ 1 other check has passed 1/6 successful checks

GitHub

05/24/2023, 6:21 PM

1 new commit pushed to

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

by wild-endeavor

<https://github.com/flyteorg/flytekit/commit/eafcc820303367749e63edc62190b9153fd6be5e|eafcc820>

- Add support overriding image (#1652) flyteorg/flytekit

GitHub

05/24/2023, 6:24 PM

#3724 [UI Feature] Improve JSON renderer to prefer friendly names over enum Issue created by FrankFlitton Motivation: Why do you think this is important? It can be hard to determine what resources the request is using via the app UI. For example, in the image below, the blue numeric keys represent CPU, GPU, etc.

image▾

Goal: What should the final outcome look like, ideally? In place the blue numeric key values showing the enum value, show a friendly string instead. 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

GitHub

05/24/2023, 6:40 PM

#3566 [Core feature] Add user id to security context Issue created by ByronHsu Motivation: Why do you think this is important? Currently, we do not have user id in the security context. Therefore, the developers are unable to decorate the task with user id on flytepropeller side. Goal: What should the final outcome look like, ideally? Add userid to security context protobuf and change related repo accordingly. Describe alternatives you've considered None Propose: Link/Inline OR Additional context No response Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte

GitHub

05/24/2023, 6:43 PM

1 new commit pushed to

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

by davidmirror-ops

<https://github.com/flyteorg/community/commit/b33d4d6b0dbb5b7e89642c82d265decbe9d0aa4b|b33d4d6b>

- Add SIG charter template flyteorg/community

GitHub

05/24/2023, 6:49 PM

1 new commit pushed to

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

by hamersaw

<https://github.com/flyteorg/flytepropeller/commit/e1f6d763a5f7f3c32bbc20c0981f00f391ea6244|e1f6d763>

- bumped flyteplugins (#566) flyteorg/flytepropeller

GitHub

05/24/2023, 7:10 PM

1 new commit pushed to

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

by davidmirror-ops

<https://github.com/flyteorg/community/commit/92d2db5b5e5ceabd701f74458a01fe7a1f0f2acf|92d2db5b>

- Add groups.yaml flyteorg/community

GitHub

05/24/2023, 7:33 PM

1 new commit pushed to

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

by davidmirror-ops

<https://github.com/flyteorg/community/commit/658a87d81d5afb03fd5521f56553f5053116ebc7|658a87d8>

- Implement RFC 007 flyteorg/community

GitHub

05/24/2023, 7:41 PM

1 new commit pushed to

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

by hamersaw

<https://github.com/flyteorg/flyteplugins/commit/8a2f8ca2e723d067c4915b8a9ec2960eb4ff6526|8a2f8ca2>

- only initializing maptask if there is no failure (#352) flyteorg/flyteplugins

GitHub

05/24/2023, 8:13 PM

Release - v1.0.62 New release published by flyte-bot Changelog • 8a2f8ca only initializing maptask if there is no failure (#352) flyteorg/flyteplugins

GitHub

05/24/2023, 8:54 PM

Release - v1.1.92 New release published by flyte-bot Changelog • e1f6d76 bumped flyteplugins (#566) flyteorg/flytepropeller