#3412 Fix broken build in sandbox-lite Pull request opened by jeevb flyteorg/flyte ✅ All checks have passed 2/2 successful checks

#3413 Add charts to gitignore Pull request opened by jeevb flyteorg/flyte ✅ All checks have passed 2/2 successful checks

1 new commit pushed to

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

by jeevb

<https://github.com/flyteorg/flyte/commit/34e9fd543f8f24d35d101d056b0f5fb97a98cee5|34e9fd54>

- Fix broken build in sandbox-lite (#3412) flyteorg/flyte

#1536 Less strict docker dependency versions Pull request opened by jcugat TL;DR Change the minimum required version of the docker dependency from v5.* to v4.* 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 We need it because we use Flyte alongside other packages which force a docker version in the v4.* range (specifically tensorflow's tfx package). I have tried running the tests locally while force-installing docker

docker==4.0.2

and it worked without any errors, so there's no breaking change between those versions that would affect this project. Also it would be great if this change was backported to the Flyte v1.2.* and v1.3.* branches, thanks! Tracking Issue NA Follow-up issue NA flyteorg/flytekit ✅ All checks have passed 30/30 successful checks

#712 Mapped Tasks not showing cache status correctly. Pull request opened by james-union #644 Two issues (1) It renders cache status incorrectly because it depended on the index of the logs instead of the id. While running, the logs are not in the original order (they are in order of queued/success instead of original order). So need to find correct cache status based on id (2) the useStyles/hooks should not be used after component is rendered. It broke the app when the execution status is updated. I managed to place it before any render To reproduce For this workflow, https://development.uniondemo.run/console/projects/flytesnacks/domains/development/workflows/map-task.my_cached_map_workflow_1?duration=all • Click

Launch Workflow

button • For the parameter, we need to mix some cached numbers and non-cached numbers to reproduce this issue. Right now, 0 ~ 8 are cached. (This will be changed if someone run this more). So for example, if 0 ~ 8 are cached, we can set the param as

[9,1,0,12,11,3]

• Then while running the mapped task, if you go to the Map Execution panel on the right side (by navigating to the execution details and and click the first Map task), you will see some queued & succeeded tasks. Actually the problem is the icons next to the task names. If those are already queued, then it should be the refresh icon which identifies already cached. • To reproduce the second issue, you should wait until the Map task is completed while open this right panel. Once it is updated, the right panel will be broken. 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 flyteorg/flyte#644 flyteorg/flyteconsole GitHub Actions: Build & Push FlyteConsole Image GitHub Actions: Get Release Tag GitHub Actions: Generate Release ✅ 6 other checks have passed 6/9 successful checks

1 new commit pushed to

<https://github.com/flyteorg/static-resources/tree/main|main>

by cosmicBboy

<https://github.com/flyteorg/static-resources/commit/252f16bb5fa0c4deeaf9392e9e7ec88b269b7f17|252f16bb>

- Add mlflow images (#19) flyteorg/static-resources

1 new commit pushed to

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

by ursucarina

<https://github.com/flyteorg/flyteconsole/commit/c13adbcff5c213186ebd1832b8a56c023d7a130f|c13adbcf>

- chore: fix update_npmversion (#709) flyteorg/flyteconsole

#3414 [Core feature] Spark, Ray, Dask plugins should support `pod_template` and `pod_template_name` arguments Issue created by cosmicBboy Motivation: Why do you think this is important? Similar to flyteorg/flytekit#1515, we want to add support for the new pod template configuration for the spark, ray, and dask plugins: ☐ spark plugin code changes: https://github.com/flyteorg/flytekit/tree/master/plugins/flytekit-spark ☐ spark plugin flytesnacks docs: https://github.com/flyteorg/flytesnacks/tree/master/cookbook/integrations/kubernetes/k8s_spark ☐ ray plugin code changes: https://github.com/flyteorg/flytekit/tree/master/plugins/flytekit-ray ☐ ray plugin flytesnacks docs: https://github.com/flyteorg/flytesnacks/tree/master/cookbook/integrations/kubernetes/ray_example ☐ dask plugin code changes: https://github.com/flyteorg/flytekit/tree/master/plugins/flytekit-dask ☐ dask plugin flytesnacks docs: https://github.com/flyteorg/flytesnacks/tree/master/cookbook/integrations/kubernetes/k8s_dask Goal: What should the final outcome look like, ideally? Each of the plugins mentioned above needs to accept

pod_template

and

pod_template_name

arguments, like the ContainerTask PR, with documentation updates in the Spark, Ray, and Dask integration examples. Describe alternatives you've considered NA 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

2 new commits pushed to

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

by davidmirror-ops

<https://github.com/flyteorg/community/commit/96a0ff9e420a8b46b341d436309f6b0e04df2432|96a0ff9e>

- Add MAINTAINERS

<https://github.com/flyteorg/community/commit/350996468d7b47970499eaf9ca904dbdbc75941b|35099646>

- Merge branch 'main' of https://github.com/flyteorg/community flyteorg/community

1 new commit pushed to

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

by davidmirror-ops

<https://github.com/flyteorg/community/commit/b7b71c3b1f0e946dd6577904269e8e8a84effbeb|b7b71c3b>

- Update README.md flyteorg/community

1 new commit pushed to

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

by ursucarina

<https://github.com/flyteorg/flyteconsole/commit/2a40b099204f7781b432e6a9b53e94eb038d2943|2a40b099>

- Mapped Tasks not showing cache status correctly. (#712) flyteorg/flyteconsole

1 new commit pushed to

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

by ursucarina

<https://github.com/flyteorg/flyteconsole/commit/fa789e24ffaca9f00d61b3dea87bb417ef85223e|fa789e24>

- fix: cleanup, passthrough runtime variables (#710) flyteorg/flyteconsole

1 new commit pushed to

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

by jeevb

<https://github.com/flyteorg/flyte/commit/da0ed93b7014bd5402d46b902d0752fe0fce5101|da0ed93b>

- Add charts to gitignore (#3413) flyteorg/flyte

#3415 [Housekeeping] FE: Update flyteconsole to Node 18 Issue created by jsonporter Describe the issue Currently flyteconsole builds on Node 16 and this has caused problems when updating other packages - most notably semantic-release. This ticket will cover any required updates/changes to allow build/release with node 18. What if we do not do this? We must 😎 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

#3416 Docstring not supported on flyteconsole Issue created by ByronHsu 1. docstring is already stored in database but not exposed to UI 2. My idea is to add a docstring column and provide an doc icon to hover. When users hover on the icon, they can see the doc flyteorg/flyte

1 new commit pushed to

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

by jeevb

<https://github.com/flyteorg/flyte/commit/6d4a0621847932417182e811545ec28f66e2d69a|6d4a0621>

- Make clientIds and self auth server configurable in flyte-binary helm chart (#3411) flyteorg/flyte

Release - v1.4.5 New release published by flyte-bot 1.4.5 (2023-03-07) Bug Fixes • cleanup, passthrough runtime variables (#710) (fa789e2) flyteorg/flyteconsole

1 new commit pushed to

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

by jeevb

<https://github.com/flyteorg/flyte/commit/d40eb8b790e12fa0f7e0a412f0eae0cd59e076b4|d40eb8b7>

- Use signedURL endpoint override for signed URLs generated by flyte in sandbox-bundled (#3410) flyteorg/flyte

1 new commit pushed to

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

by jeevb

<https://github.com/flyteorg/flyte/commit/c8fa4e6a9573ffc819b4468867123aabbe503725|c8fa4e6a>

- update example local dev config file (#3401) flyteorg/flyte

#3418 [Core feature] Matchable resource updates should show diffs/force confirm on overrides Issue created by katrogan Motivation: Why do you think this is important? When updating project or workflow based matchable resources using flytectl, users can run into a scenario where an existing override exists and their call to update completely overwrites it. This isn't always intentional so having a merging strategy or some kind of confirmation can help reduce churn in unintentional updates For example, existing cluster resource controller attrs:

domain: development
project: flytesnacks
attributes:
  foo: "bar"

which are then updated with

domain: development
project: flytesnacks
attributes:
  buzz: "lightyear"

completely removes the existing foo template value (which means the actual rendering falls back to the application default.) Users may intend for their behavior to be a merge but be unaware an existing override exists. We should reduce the potential for unintended overrides. Goal: What should the final outcome look like, ideally? It should be difficult to unintentionally overwrite matchable resources. Describe alternatives you've considered The current system is error prone. The below proposals are just some suggestions for making sure we don't introduce accidental overwrites. Propose: Link/Inline OR Additional context We could • have flytectl first do a get before writing an update and showing a lightweight, terraform plan like preview of the applied changes and require user confirmation • Introduce a dry run flag to show anticipated changes • Use a kubernetes-like versioning scheme for making sure only the latest version of a resource is applied in update calls (you can't overwrite with a stale version) • this would be a wider-sweeping and more complicated change for a behavior that is infrequently exercised Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte

#3419 [BUG] Spark plugin should include ContainerName label Issue created by andrewwdye Describe the bug The spark plugin does not include ContainerName, preventing container-level log filtering. Expected behavior Can filter at container level using a template like

<https://console.cloud.google.com/logs/query;query=resource.labels.namespace_name%3D%22{{.namespace}}%22%0Aresource.labels.pod_name%3D%22{{.podName}}%22%0Aresource.labels.container_name%3D%22{{.containerName}}%22>...

Additional context to reproduce 1. Configure spark log template with

.containerName

as noted above 2. Run spark task 3. Navigate to logs Screenshots No response Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte

#1537 Pin fsspec to <=2023.1 Pull request opened by wild-endeavor TL;DR fsspec 2023.3.0 seems to have broken something in the old code. We are pinning to less than that while we work out the new code. 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 Pin Tracking Issue https://flyte-org.slack.com/archives/CP2HDHKE1/p1678209398640519 flyteorg/flytekit ✅ All checks have passed 2/2 successful checks

#1538 Pyflyte docs formatting Pull request opened by bryanwweber TL;DR Update docs formatting for pyflyte. RestructuredText is a little bit different to Markdown... 😢 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 ✅ All checks have passed 30/30 successful checks

#1539 Backport #1537 Pull request opened by wild-endeavor Please see https://github.com/flyteorg/flytekit/pull/1537/files flyteorg/flytekit GitHub Actions: build-plugins (3.8, flytekit-snowflake) GitHub Actions: build-plugins (3.8, flytekit-ray) GitHub Actions: build-plugins (3.8, flytekit-polars) GitHub Actions: build-plugins (3.8, flytekit-papermill) GitHub Actions: build-plugins (3.8, flytekit-pandera) GitHub Actions: build-plugins (3.8, flytekit-onnx-scikitlearn) GitHub Actions: build-plugins (3.8, flytekit-onnx-pytorch) GitHub Actions: build-plugins (3.8, flytekit-modin) GitHub Actions: build-plugins (3.8, flytekit-kf-tensorflow) GitHub Actions: build-plugins (3.8, flytekit-kf-pytorch) 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-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: build (windows-latest, 3.9) GitHub Actions: build (windows-latest, 3.8) 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 ✅ No checks have passed 0/30 successful checks

#1540 Pin fsspec Pull request opened by wild-endeavor Please see https://github.com/flyteorg/flytekit/pull/1537/files flyteorg/flytekit ✅ All checks have passed 30/30 successful checks

#713 fix: update_npmversion Pull request opened by ursucarina TL;DR Fixes bug in update_npmversion script 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 Fixes bug in update_npmversion script flyteorg/flyteconsole ✅ All checks have passed 1/1 successful checks

1 new commit pushed to

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

by katrogan

<https://github.com/flyteorg/flyteidl/commit/6ad4072d90d1917dbfb9b98f466614ba138527aa|6ad4072d>

- Use TokenCache in ClientCredentialsTokenSourceProvider (#377) flyteorg/flyteidl

#1541 Release v1.2 backport to 1.4 Pull request opened by wild-endeavor Pull in changes in master from 7a77508 to d4bf234 dropping 45c0110 flyteorg/flytekit GitHub Actions: build-plugins (3.8, flytekit-modin) GitHub Actions: build-plugins (3.8, flytekit-kf-tensorflow) GitHub Actions: build-plugins (3.8, flytekit-kf-pytorch) 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-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-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: build (windows-latest, 3.9) GitHub Actions: build (windows-latest, 3.8) GitHub Actions: build (windows-latest, 3.7) GitHub Actions: build (ubuntu-latest, 3.10) GitHub Actions: build (ubuntu-latest, 3.9) GitHub Actions: build (ubuntu-latest, 3.8) GitHub Actions: build (ubuntu-latest, 3.7) GitHub Actions: lint GitHub Actions: docs ✅ 2 other checks have passed 2/27 successful checks

#398 Doc updates Pull request opened by pmahindrakar-oss 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 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/flytectl ✅ All checks have passed 2/2 successful checks

1 new commit pushed to

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

by ursucarina

<https://github.com/flyteorg/flyteconsole/commit/0c4e5598d1ae6aaf68710ea4ca41c3d118ddb0d3|0c4e5598>

- fix: update_npmversion (#713) flyteorg/flyteconsole