#399 Add support for gate nodes Pull request opened by eapolinario Read then delete • Make sure to use a concise title for the pull-request. • Use #patch, #minor #majora or #none in the pull-request title to bump the corresponding version. Otherwise, the patch version will be bumped. More details TL;DR Add support for gate nodes 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 handle gate nodes in

hydrateNode

. Tracking Issue flyteorg/flyte#3461 Follow-up issue NA flyteorg/flytectl GitHub Actions: Goreleaser GitHub Actions: Generate documentation GitHub Actions: Bump Version ✅ 7 other checks have passed 7/10 successful checks

1 new commit pushed to

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

by eapolinario

<https://github.com/flyteorg/flytectl/commit/29da2881ad12b42dd481d3eac6e43a855a46aee7|29da2881>

- Add support for gate nodes (#399) flyteorg/flytectl

Release - v0.6.34 New release published by flyte-bot Changelog • 29da288 Add support for gate nodes (#399) 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/04431d08c7350296b7e0b51380e0278e5c1e7ba7|04431d08>

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

1 new commit pushed to

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

by eapolinario

<https://github.com/flyteorg/flytekit/commit/34f80ba12eda64431be4c21c78df81b7afbe2758|34f80ba1>

- Pluck retry from flytekit and into sagemaker (#1411) flyteorg/flytekit

#1411 Pluck retry from flytekit and into sagemaker Pull request opened by eapolinario Signed-off-by: Eduardo Apolinario eapolinario@users.noreply.github.com TL;DR

retry

is only used in the sagemaker plugin - it should no longer be a flytekit dependence 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

retry

is only used in the sagemaker flytekit plugin, which means that we only need

retry

there. We're going to release a minor version of flytekit and in a follow up PR we can then update the dependence in the sagemaker plugin's requirements. Tracking Issue flyteorg/flyte#3052 Follow-up issue NA flyteorg/flytekit Codecov: 69.51% (-0.19%) compared to 152080f ✅ 29 other checks have passed 29/30 successful checks

#331 persisting k8s plugin phase, version, and reason Pull request opened by hamersaw TL;DR This PR adds support for persisting state of k8s plugins including Phase, PhaseVersion, and Reason. This is used to detect scenarios where the

Reason

has been updated and update the

PhaseVersion

to ensure that the latest

Reason

is reported to FlyteAdmin in a

TaskExecutionEvent

. 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#3440 Follow-up issue NA flyteorg/flyteplugins Codecov: 62.65% (-0.22%) compared to 1329476 Codecov: 51.06% of diff hit (target 62.87%) ✅ 4 other checks have passed 4/6 successful checks

#400 Fix flyteadmin port in `flytectl config init` Pull request opened by eapolinario TL;DR Fix the flyteadmin port by

flytectl config init

to match the one required by demo cluster 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/flytectl GitHub Actions: Dry Run Goreleaser ✅ 8 other checks have passed 8/9 successful checks

#3469 [FlyteCTL Feature] Add `--force` flag to `flytectl config init` Issue created by eapolinario Describe the feature/command for FlyteCTL Config files are usually setup in CI, but this is hard in the case of

flytectl config init

because it expects user input in case there's an existing file. Provide a possible output or UX example We should be able to run

flytectl config init --force

to force an update to the config file. 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/80edd63a788a817513f9d4b2aba51e38cda9c805|80edd63a>

- The rendering of node status in a dynamic workflow is not functioning correctly (#723) flyteorg/flyteconsole

#724 chore(deps): bump webpack from 5.75.0 to 5.76.0 Pull request opened by dependabot[bot] Bumps webpack from 5.75.0 to 5.76.0. Release notes Sourced from webpack's releases.

v5.76.0

Bugfixes

• Avoid cross-realm object access by `@​Jack-Works` in webpack/webpack#16500

• Improve hash performance via conditional initialization by `@​lvivski` in webpack/webpack#16491

• Serialize

generatedCode

info to fix bug in asset module cache restoration by `@​ryanwilsonperkin` in webpack/webpack#16703

• Improve performance of

hashRegExp

lookup by `@​ryanwilsonperkin` in webpack/webpack#16759

Features

• add

target

to

LoaderContext

type by `@​askoufis` in webpack/webpack#16781

Security

• CVE-2022-37603 fixed by `@​akhilgkrishnan` in webpack/webpack#16446

Repo Changes

• Fix HTML5 logo in README by `@​jakebailey` in webpack/webpack#16614

• Replace TypeScript logo in README by `@​jakebailey` in webpack/webpack#16613

• Update actions/cache dependencies by `@​piwysocki` in webpack/webpack#16493

New Contributors

• `@​Jack-Works` made their first contribution in webpack/webpack#16500

• `@​lvivski` made their first contribution in webpack/webpack#16491

• `@​jakebailey` made their first contribution in webpack/webpack#16614

• `@​akhilgkrishnan` made their first contribution in webpack/webpack#16446

• `@​ryanwilsonperkin` made their first contribution in webpack/webpack#16703

• `@​piwysocki` made their first contribution in webpack/webpack#16493

• `@​askoufis` made their first contribution in webpack/webpack#16781

Full Changelog: webpack/webpack@v5.75.0...v5.76.0

Commits • `97b1718` Merge pull request #16781 from askoufis/loader-context-target-type • `b84efe6` Merge pull request #16759 from ryanwilsonperkin/real-content-hash-regex-perf • `c98e9e0` Merge pull request #16493 from piwysocki/patch-1 • `5f34acf` feat: Add

target

to

LoaderContext

type • `b7fc4d8` Merge pull request #16703 from ryanwilsonperkin/ryanwilsonperkin/fix-16160 • `63ea82d` Merge branch 'webpack:main' into patch-1 • `4ba2252` Merge pull request #16446 from akhilgkrishnan/patch-1 • `1acd635` Merge pull request #16613 from jakebailey/ts-logo • `302eb37` Merge pull request #16614 from jakebailey/html5-logo • `cfdb1df` Improve performance of hashRegExp lookup • Additional commits viewable in compare view Maintainer changes This version was pushed to npm by evilebottnawi, a new releaser for webpack since your current version. Dependabot compatibility score Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting

@dependabot rebase

. * * * Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: •

@dependabot rebase

will rebase this PR •

@dependabot recreate

will recreate this PR, overwriting any edits that have been made to it •

@dependabot merge

will merge this PR after your CI passes on it •

@dependabot squash and merge

will squash and merge this PR after your CI passes on it •

@dependabot cancel merge

will cancel a previously requested merge and block automerging •

@dependabot reopen

will reopen this PR if it is closed •

@dependabot close

will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually •

@dependabot ignore this major version

will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) •

@dependabot ignore this minor version

will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) •

@dependabot ignore this dependency

will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) •

@dependabot use these labels

will set the current labels as the default for future PRs for this repo and language •

@dependabot use these reviewers

will set the current reviewers as the default for future PRs for this repo and language •

@dependabot use these assignees

will set the current assignees as the default for future PRs for this repo and language •

@dependabot use this milestone

will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the Security Alerts page. flyteorg/flyteconsole GitHub Actions: Build Flyteconsole Image / Push to Github Registry GitHub Actions: extract_branch GitHub Actions: unit_tests_with_coverage GitHub Actions: lint_project ✅ 2 other checks have passed 2/6 successful checks

#970 Update use_secrets.py Pull request opened by cosmicBboy Signed-off-by: Niels Bantilan niels.bantilan@gmail.com This PR updates the secrets doc to add the instruction that the secret needs to be created in the same K8s namespace as the workflow execution accessing the secret. 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

#720 chore: task observability Pull request opened by ursucarina TL;DR Initial setup for task observability 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 To setup: • run

git fetch -p && git checkout carina/obs

• run

make pack

•

cd packages/console

•

yalc publish

• run

yarn build:watch

Go to

cloud/clients

repo • run

git fetch -p && git checkout carina/obs

• run

make prep_console

• cd

packages/zapp/console

• run

yalc add @flyteorg/console

• run

yarn start

flyteorg/flyteconsole GitHub Actions: Build & Push FlyteConsole Image GitHub Actions: Get Release Tag GitHub Actions: Generate Release DCO: DCO ✅ 5 other checks have passed 5/9 successful checks

#971 [WIP] Doc for out of core Pull request opened by pingsutw This doc includes • how to register a backend plugin in python • how to build a image for the flyteplugins service • How to enable flyteplugins service • WIP flyteorg/flytesnacks GitHub Actions: Docs Warnings GitHub Actions: Create a list of packages WIP: Title contains "WIP" ✅ 1 other check has passed 1/4 successful checks

#3470 [Core feature] change with_overrides to update metadata as well Issue created by jsonporter Motivation: Why do you think this is important? While investigating a different issue born from a a user request to update the execution detail views (list, graph, timeline) to display values passed to

with_overrides

-- we realized this was not an ideal UX/UI because it would mean these views would then be displaying the

nodeId

rather than human-readable function names (eg,

n0-0-n2-0-n0-0-n1

vs

hello_person

). This is because while parsing the

compiledWorkflowClosure

we must choose to display based off either the

nodeId

or the

metadata.name

and a node will always have a

nodeId

so we can't do a conditional. Example: the user was requesting to display the

nodeId

'hello-bob' here instead of the function name 'hello_person' from

metadata.name

but we see in the second example that this is actually less useful in most cases.

"id": "hello-bob",
    "metadata": {
        "name": "hello_person",
        "retries": {}
      }

"id": "n0",
    "metadata": {
        "name": "people",
        "retries": {}
},

As a solution we want to update

with_overrides

to update both the

nodeId

and the

metadata.name

field -- this better matches the user intention of

with_overrides

and in those cases display the overridden name while also preserving the better UX for most/standard executions. Goal: What should the final outcome look like, ideally? When a user defines an entity in flytekit and uses

with_overrides

, it will update both the

nodeId

and

metadata.name

for that execution. Describe alternatives you've considered NA Propose: Link/Inline OR Additional context #3370 flyteorg/flytekit#1344 Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte

#3471 starting controller runtime manager Pull request opened by hamersaw Tracking issue NA Describe your changes Starting the k8s controller runtime manager so that watches on k8s resources work in plugins. This is necessary to ensure propeller promptly evaluates the workflow after a change in task status is detected. Check all the applicable boxes ☐ I updated the documentation accordingly. ☑︎ All new and existing tests passed. ☑︎ All commits are signed-off. Screenshots NA Note to reviewers NA flyteorg/flyte ✅ All checks have passed 9/9 successful checks

1 new commit pushed to

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

by eapolinario

<https://github.com/flyteorg/flyte/commit/c3bdaa42d3b61315884c409dcdee048a80000446|c3bdaa42>

- Update Flyte components (#3445) flyteorg/flyte

Release - Flyte v1.4.1 milestone release New release published by flyte-bot Flyte 1.4.1 release A patch release containing a few bug fixes, including: • Structured Dataset with generic format should be castable to Flyte Schema • Validation of user-provided urls • Show correct app version in info • Fix cache status of Map Tasks flyteorg/flyte

Deployment to github-pages by flyte-bot flyteorg/flyte

2 new commits pushed to

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

by cosmicBboy

<https://github.com/flyteorg/flyte-attendant/commit/bfadac11e681197ed6e8e11c063ae47a70673afa|bfadac11>

- update app config

<https://github.com/flyteorg/flyte-attendant/commit/307ec2bc319eaa361000d488ff5c48cd65a4ace3|307ec2bc>

- update readme flyteorg/flyte-attendant

1 new commit pushed to

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

by cosmicBboy

<https://github.com/flyteorg/flyte-attendant/commit/2592a4b1271b2aabe5a7693c4ed8dd7c6491fcb9|2592a4b1>

- pin numpy flyteorg/flyte-attendant

1 new commit pushed to

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

by cosmicBboy

<https://github.com/flyteorg/flyte-attendant/commit/8fbf97c28051a841e60a2a66c5423b609dac55f8|8fbf97c2>

- minor update flyteorg/flyte-attendant

1 new commit pushed to

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

by cosmicBboy

<https://github.com/flyteorg/flyte-attendant/commit/872e3f21925902f7aa9519948b70b84a2a8d0c36|872e3f21>

- move app-config.yaml flyteorg/flyte-attendant

1 new commit pushed to

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

by cosmicBboy

<https://github.com/flyteorg/flyte-attendant/commit/e6156b1c55e7b66c606bc1ca8f3f3f6a7b308d79|e6156b1c>

- add streamlit dep flyteorg/flyte-attendant

1 new commit pushed to

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

by cosmicBboy

<https://github.com/flyteorg/flyte-attendant/commit/db648f967dba492f459aaa904782a0d9f965f99d|db648f96>

- debug flyteorg/flyte-attendant

1 new commit pushed to

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

by cosmicBboy

<https://github.com/flyteorg/flyte-attendant/commit/9ae8348c320aa4d5b5a6ca3f5d16e39a7703b619|9ae8348c>

- debug auth flyteorg/flyte-attendant

1 new commit pushed to

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

by cosmicBboy

<https://github.com/flyteorg/flyte-attendant/commit/5a0e976ecf47ec446a9a1e9452749133a1f45e34|5a0e976e>

- debug auth flyteorg/flyte-attendant

1 new commit pushed to

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

by cosmicBboy

<https://github.com/flyteorg/flyte-attendant/commit/36af3b6f7d6abaa3c291b9f738bf9aa93dde554e|36af3b6f>

- debugging auth flyteorg/flyte-attendant

1 new commit pushed to

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

by cosmicBboy

<https://github.com/flyteorg/flyte-attendant/commit/0eb50a2eb3ca2870768503e4670a6911dd3ee1b2|0eb50a2e>

- debugging auth flyteorg/flyte-attendant

1 new commit pushed to

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

by cosmicBboy

<https://github.com/flyteorg/flyte-attendant/commit/429cade9bb304e3d36615220ee453c4ea597ab0f|429cade9>

- debugging auth flyteorg/flyte-attendant