Release - v1.0.18 New release published by github-actions[bot] Changelog • 53f62a7 Update .goreleaser.yml (#158) flyteorg/flytestdlib

Release - v1.0.48 New release published by flyte-bot Changelog • 5e2512a Fix archive.replacements in goreleaser (#109) flyteorg/datacatalog

Release - v0.0.32 New release published by flyte-bot Changelog • 10f7420 Update .goreleaser.yml (#61) flyteorg/flytecopilot

1 new commit pushed to

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

by hamersaw

<https://github.com/flyteorg/flyteplugins/commit/3d2525a9f9373a220219fb2d1c07f0b38101b23b|3d2525a9>

- Add ImagePullBackoffGracePeriod configuration (#370) flyteorg/flyteplugins

Release - v1.1.8 New release published by flyte-bot Changelog • 3d2525a Add ImagePullBackoffGracePeriod configuration (#370) flyteorg/flyteplugins

#3847 [Core feature] Flyteadmin email publisher Issue created by pingsutw Motivation: Why do you think this is important? Currently, FlyteaAmin sends an event to aws SNS first. (admin event publisher -> SNS -> SQS -> admin email processor) We can have an admin email publisher, which directly sends the email without SNS/SQS, and we should only use it in the sandbox. The new email publisher can be added to here Goal: What should the final outcome look like, ideally? We are able to use email/slack notifications in the sandbox. Describe alternatives you've considered Add aws sns / sqs config in the sandbox environment. 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

#587 Updating flyteplugins to 1.1.8 Pull request opened by hamersaw TL;DR Updating flyteplugins to 1.1.8. 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#3843 Follow-up issue NA flyteorg/flytepropeller GitHub Actions: Goreleaser GitHub Actions: Build & Push Flytepropeller Image GitHub Actions: Bump Version ✅ 10 other checks have passed 10/13 successful checks

#786 fix: css fixes for breadcrumbs Pull request opened by etdotal Read then delete this section - Make sure to use a concise title for the pull-request. _- Use #patch, #minor or #major in the pull-request title to bump the corresponding version. Otherwise, the patch version will be bumped. More details_ TL;DR Please replace this text with a description of what this PR accomplishes. Type ☐ Bug Fix ☐ Feature ☐ Plugin Are all requirements met? ☐ Code completed ☐ Smoke tested ☐ Unit tests added ☐ Code documentation added ☐ Any pending items have an associated Issue Complete description How did you fix the bug, make the feature etc. Link to any design docs etc Tracking Issue _Remove the '_fixes_' keyword if there will be multiple PRs to fix the linked issue_ fixes https://github.com/flyteorg/flyte/issues/ Follow-up issue NA OR https://github.com/flyteorg/flyte/issues/ flyteorg/flyteconsole ✅ All checks have passed 2/2 successful checks

1 new commit pushed to

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

by hamersaw

<https://github.com/flyteorg/flytepropeller/commit/7c5cc9bb48e9feca2ebefd6636093584677007a0|7c5cc9bb>

- updating flyteplugins (#587) flyteorg/flytepropeller

#3848 [BUG] Inconsistent argument between pyflyte package and register command Issue created by pradithya Describe the bug Input accepted by

pyflyte package

and

pyflyte register

commands are inconsistent causing friction when using the pyflyte CLI. More specifically:

package

command expects

--pkgs <pkg>

option , the

<pkg>

must be dot-delineated python packages. Example:

pyflyte --pkgs my.nested.workflow package

register

command expects

[PACKAGE_OR_MODULE]

argument. The argument, even though it is called package or module, actually is a path. Example:

pyflyte register my/nested/worfklow

This inconsistency causes confusion, especially since the

package

command can be considered a subset of the

register

command. Expected behavior These 2 commands should expect consistent inputs argument/options. In the

register

command: • Add

--pkgs

option support which expect dot-delineated python packages. • Either the existing`[PACKAGE_OR_MODULE]` or the

--pkgs

must be provided by user. In the

package

command: • Add

[PACKAGE_OR_MODULE]

supports which accept path to the workflow package • Either

[PACKAGE_OR_MODULE]

or the

--pkgs

must be provided by user. Hence, the following commands should be legal

pyflyte --pkgs my.nested.workflow package
pyflyte --pkgs my.nested.workflow register
pyflyte package my/nested/worfklow
pyflyte register my/nested/worfklow

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

#159 Extend length of docs section to 120 characters Pull request opened by eapolinario TL;DR Extend the length of sections produced by the

config docs

subcommand to 120 characters 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 flyteorg/flyte#3819 is failing due to invalid markdown. This PR increases the length of the section from 80 characters to 120 characters. 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/flytestdlib GitHub Actions: Lint / Run Lint GitHub Actions: Run tests GitHub Actions: Ensure go generate has run ✅ 2 other checks have passed 2/5 successful checks

1 new commit pushed to

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

by eapolinario

<https://github.com/flyteorg/flytestdlib/commit/3322b07655fbec960f7f3b517df77d1460eb20c5|3322b076>

- Extend length of docs section to 120 characters (#159) flyteorg/flytestdlib

Release - v1.0.19 New release published by github-actions[bot] Changelog • 3322b07 Extend length of docs section to 120 characters (#159) flyteorg/flytestdlib

Release - v1.1.105 New release published by flyte-bot Changelog • 7c5cc9b updating flyteplugins (#587) flyteorg/flytepropeller

#588 Bump flytestdlib to fix docs issue blocking 1.8 release Pull request opened by eapolinario TL;DR Fix docs generation by using flytestdlib@1.0.19 Type ☐ Bug Fix ☐ Feature ☐ Plugin Are all requirements met? ☐ Code completed ☐ Smoke tested ☐ Unit tests added ☐ Code documentation added ☐ Any pending items have an associated Issue Complete description I tested it locally compiling propeller locally and running:

❯ ./bin/flytepropeller config docs | grep -A1 Gke
...
gke-task-workload-identity (`google.GkeTaskWorkloadIdentityTokenSourceFactoryConfig`_)
""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
--
google.GkeTaskWorkloadIdentityTokenSourceFactoryConfig
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

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/flytepropeller GitHub Actions: Build & Push Flytepropeller Image GitHub Actions: Goreleaser GitHub Actions: Bump Version ✅ 10 other checks have passed 10/13 successful checks

1 new commit pushed to

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

by eapolinario

<https://github.com/flyteorg/flytepropeller/commit/5b68c2f4111a21822ba6433c7cf05cd1a9e7a803|5b68c2f4>

- Bump flytestdlib (#588) flyteorg/flytepropeller

1 new commit pushed to

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

by cosmicBboy

<https://github.com/flyteorg/flyte-conference-talks/commit/2e97272837d1c7cadd901731e789fd5d442728d4|2e972728>

- update readme flyteorg/flyte-conference-talks

Release - v1.1.106 New release published by flyte-bot Changelog • 5b68c2f Bump flytestdlib (#588) flyteorg/flytepropeller

1 new commit pushed to

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

by cosmicBboy

<https://github.com/flyteorg/flyte-conference-talks/commit/6022206d914a298da19815ea7fffcc72ff637204|6022206d>

- update readme flyteorg/flyte-conference-talks

#1721 Throw warning for nested @Task functions Pull request opened by oliverhu [BUG] Nested @task invocations should not supported #3734 TL;DR Address flyteorg/flyte#3734 that nested Tasks/Workflows is not warned. In this PR, we fixed two things: 1. During local execution, pass proper

execution_state.mode

to

flyte_entity_call_handler

, so the underlying entity handler can create the correct FlyteContext (not always LOCAL_WORKFLOW_EXECUTION). 2. If

flyte_entity_call_handler

is invoked inside LOCAL_TASK_EXECUTION or TASK_EXECUTION, warn the users of nested tasks/workflows. 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 ✅ All checks have passed 2/2 successful checks

#3849 Run specific set of tests in functional tests suite Pull request opened by eapolinario Describe your changes We pluck a specific set of tests and register those as opposed to registering all flytesnacks examples. This PR uses the default flytekit image as base image and fast-registers the flyte entities mentioned in the P0 functional tests. Check all the applicable boxes ☐ I updated the documentation accordingly. ☐ All new and existing tests passed. ☐ All commits are signed-off. Screenshots Note to reviewers flyteorg/flyte GitHub Actions: build-and-push-sandbox-bundled-image GitHub Actions: sandbox-bundled-functional-tests ✅ 8 other checks have passed 8/10 successful checks

#787 [Snyk] Security upgrade babel-loader from 8.3.0 to 9.1.3 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

npm

dependencies of this project. Changes included in this PR • Changes to the following files to upgrade the vulnerable dependencies to a fixed version: • package.json Vulnerabilities that will be fixed With an upgrade: (*) Note that the real score may have changed since the PR was raised. Commit messages Package name: babel-loader The new version differs by 34 commits. • b89dfbd 9.1.3 • 54fb781 Update caniuse • 6f300f3 bump find-cache-dir to v4 (#995) • 2fd1c0a Bump semver from 7.3.2 to 7.5.2 (#993) • b3682fd Add more exhaustive example on customized-loader (#897) • a797c3b ci: bump actions/checkout (#981) • 170350e Bump http-cache-semantics from 4.1.0 to 4.1.1 (#982) • 78bd0a1 Update README.md (#987) • c049187 Bump webpack from 5.74.0 to 5.76.0 (#986) • 0406d16 9.1.2 • ca0cc0e Bump json5 from 2.2.1 to 2.2.3 (#980) • c8b1feb build: harden ci.yml permissions (#976) • 4e70cca Bump qs from 6.5.2 to 6.5.3 (#977) • 15fbacf 9.1.0 • 6348e1c Pass external dependencies from Babel to Webpack (#971) • 457b9ad Update webpack • f42ac9b 9.0.1 • 4f9c0bf remove "node:" builtin prefix (#970) • 9ff288f 9.0.0 • 006a3dc Update README.md • daed88a Update README.md • 0ed5fd6 Bump ini from 1.3.5 to 1.3.8 (#968) • b1749e3 Bump y18n from 4.0.0 to 4.0.3 (#967) • 3a55a4a Bump lodash from 4.17.20 to 4.17.21 (#966) See the full diff 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/95f910b45c72f129e609c3df0bb49348892483722ce13149764b6c655bf6fb75/68747470733a2f2f6170692e7365676d656e742e696f2f76312f706978656c2f747261636b3f646174613d65794a33636d6c305a55746c65534936496e4a79576d785a634564485932527954485a7362306c596430645563566734576b4652546e4e434f5545774969776959573576626e6c746233567a535751694f694a6b4f54426b596a526d59693031596d45324c5451354e6a6374595455314e5331694e6a45324e446c6b4e6d466a4d5455694c434a6c646d567564434936496c425349485a705a58646c5a434973496e42796233426c636e52705a584d694f6e736963484a4a5a434936496d51354d4752694e475a694c545669595459744e446b324e7931684e5455314c5749324d5459304f57513259574d784e534a3966513d3d 🧐 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/flyteconsole GitHub Actions: Build & Push FlyteConsole Image GitHub Actions: Get Release Tag GitHub Actions: Generate Release GitHub Actions: unit_tests_with_coverage GitHub Actions: lint_project DCO: DCO ✅ 3 other checks have passed 3/9 successful checks

#3850 [BUG][UI] Launchplan Icon in FlyteConsole is not rendered properly Issue created by pradithya Describe the bug Launchplan icon in FlyteConsole's side bar sometime appears in a random position until the page is refreshed. Expected behavior Launchplan icon should be rendered properly. Additional context to reproduce This behavior is triggered when navigating to workflow execution page and then pressing back button. Screenshots Incorrect launchplan icon position Flyte console version Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte

#3851 Doc: gang-scheduling for kubeflow training-operator Pull request opened by fg91 Describe your changes In the Flyte Slack community there have been multiple questions recently how timeout errors can be avoided which occur when the workers of distributed training jobs don't start at the same time due to resource constraints. The best solution to this problem is to use a Kubernetes scheduler which supports gang scheduling. In this PR I add documentation how this can be configured. ☑︎ I updated the documentation accordingly. ☑︎ All new and existing tests passed. ☑︎ All commits are signed-off. flyteorg/flyte ✅ All checks have passed 6/6 successful checks

2 new commits pushed to

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

by cosmicBboy

<https://github.com/flyteorg/flyte-conference-talks/commit/d93d71ff8182532cb6fe7f0c3a8ede1f46add347|d93d71ff>

- pin flytekit

<https://github.com/flyteorg/flyte-conference-talks/commit/06999174034c5018c45052861cc7a313983755f9|06999174>

- add github workflow flyteorg/flyte-conference-talks

1 new commit pushed to

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

by cosmicBboy

<https://github.com/flyteorg/flyte-conference-talks/commit/9889ed6c9b7e4b9388fb02a36c0a2f2acc6e2d52|9889ed6c>

- update ci flyteorg/flyte-conference-talks

1 new commit pushed to

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

by cosmicBboy

<https://github.com/flyteorg/flyte-conference-talks/commit/298073fd2d9e7e52a0f00e82ce816ca659641073|298073fd>

- update integration ci flyteorg/flyte-conference-talks

1 new commit pushed to

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

by cosmicBboy

<https://github.com/flyteorg/flyte-conference-talks/commit/1d2adc8c39a94e8c8f06850114de553dcf23eaec|1d2adc8c>

- debug flyteorg/flyte-conference-talks

1 new commit pushed to

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

by cosmicBboy

<https://github.com/flyteorg/flyte-conference-talks/commit/b9c929b4726186bfdee5ceffc3f5a8202a2b80de|b9c929b4>

- debugging flyteorg/flyte-conference-talks

1 new commit pushed to

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

by cosmicBboy

<https://github.com/flyteorg/flyte-conference-talks/commit/54a6b9a052491a7a0d557a9418bfe296ec75e428|54a6b9a0>

- debug flyteorg/flyte-conference-talks