1 new commit pushed to

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

by hamersaw

<https://github.com/flyteorg/flytepropeller/commit/e4ca252977fe791946e70e79d645658025f3d2af|e4ca2529>

- Setting primaryContainerName by default on Pod plugin (#555) flyteorg/flytepropeller

Release - v1.1.83 New release published by flyte-bot Changelog • e4ca252 Setting primaryContainerName by default on Pod plugin (#555) flyteorg/flytepropeller

#3604 [Docs] Add documentation for partial task support Issue created by cosmicBboy Description Flytekit 1.5.0 added support for using

partial

to provide default arguments to tasks. The flytesnacks documentation should be updated with this information in the basics section and maybe also the Flyte Fundamentals section Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte

#3605 [BUG] Flytectl update project doesn't respect state from yaml file Issue created by katrogan Describe the bug If you specify the desired project state in the a

project.yaml

file as documented in the flytectl helpstring: https://docs.flyte.org/projects/flytectl/en/latest/gen/flytectl_update_project.html#id1 The state doesn't actually get respected but gets overridden by the default config value (which is to set the project to active) Expected behavior Project state defined in a yaml spec should be respected when using flytectl to update a project 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

#402 Respect project state in project.yaml file Pull request opened by katrogan TL;DR Project state specified in a project.yaml file is always overridden by the default config flag currently. This change updates project.yaml parsing to respect the state defined in the project.yaml file and only read from the config value when no project.yaml is defined. 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 Testing: • Tested by setting

state: 1

and then

state: 0

in project.yaml and verified the project was archived and activated as expected (see https://github.com/flyteorg/flyteidl/blob/master/protos/flyteidl/admin/project.proto#L37,L45 for enum values) • Also used command line flags

flytectl update project -p flytetester --archiveProject

and then

flytectl update project -p flytetester --activate

to verify the project archived and activated as expected Tracking Issue flyteorg/flyte#3605 Follow-up issue NA flyteorg/flytectl GitHub Actions: Goreleaser GitHub Actions: Generate documentation GitHub Actions: Bump Version GitHub Actions: Unit Tests / Run Unit Test ✅ 6 other checks have passed 6/10 successful checks

#1595 Set default ComSpec when running on Windows Pull request opened by pingsutw TL;DR Fixes below errors in the CI, The test is failing because the latest python requires user to set

COMSPEC

in environment variable. For more detail, check python/cpython#101283

FAILED tests/flytekit/unit/extras/tasks/test_shell.py::test_shell_task_no_io - FileNotFoundError: shell not found: neither %ComSpec% nor %SystemRoot% is set
FAILED tests/flytekit/unit/extras/tasks/test_shell.py::test_input_substitution_primitive - FileNotFoundError: shell not found: neither %ComSpec% nor %SystemRoot% is set
FAILED tests/flytekit/unit/extras/tasks/test_shell.py::test_input_substitution_files - FileNotFoundError: shell not found: neither %ComSpec% nor %SystemRoot% is set
FAILED tests/flytekit/unit/extras/tasks/test_shell.py::test_input_substitution_files_ctx - FileNotFoundError: shell not found: neither %ComSpec% nor %SystemRoot% is set
FAILED tests/flytekit/unit/extras/tasks/test_shell.py::test_input_output_substitution_files - FileNotFoundError: shell not found: neither %ComSpec% nor %SystemRoot% is set
FAILED tests/flytekit/unit/extras/tasks/test_shell.py::test_input_single_output_substitution_files - FileNotFoundError: shell not found: neither %ComSpec% nor %SystemRoot% is set
FAILED tests/flytekit/unit/extras/tasks/test_shell.py::test_reuse_variables_for_both_inputs_and_outputs - FileNotFoundError: shell not found: neither %ComSpec% nor %SystemRoot% is set
FAILED tests/flytekit/unit/extras/tasks/test_shell.py::test_can_use_complex_types_for_inputs_to_f_string_template - FileNotFoundError: shell not found: neither %ComSpec% nor %SystemRoot% is set

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

1 new commit pushed to

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

by katrogan

<https://github.com/flyteorg/flytectl/commit/bd6b85605f49ff4877484edd69942ca72f4e19dd|bd6b8560>

- Respect project state in project.yaml file (#402) flyteorg/flytectl

1 new commit pushed to

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

by jsonporter

<https://github.com/flyteorg/flyteconsole/commit/27238ced4679266c7bbf8c409fdcc21721802841|27238ced>

- fix: force node executions to pull their status (#737) flyteorg/flyteconsole

1 new commit pushed to

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

by pingsutw

<https://github.com/flyteorg/flytekit/commit/401c505ecb511aad6dba70adcae50762b4288521|401c505e>

- Add support nested FlyteFile in pyflyte run (#1587) flyteorg/flytekit

Release - v0.6.36 New release published by flyte-bot Changelog • bd6b856 Respect project state in project.yaml file (#402) 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/df4e84ccb2843d1af91314a1090e72893d904594|df4e84cc>

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

Release - v1.6.2 New release published by flyte-bot 1.6.2 (2023-04-17) Bug Fixes • force node executions to pull their status (#737) (27238ce) flyteorg/flyteconsole

#3606 [BUG] Runtime error causes retries Issue created by gregfriedland Describe the bug When a task fails with a user-generated

RuntimeError

, the workflow is retried. According to the docs, it seems like this case is considered non-recoverable and should not be retried. Expected behavior Workflow and task fail with no retries Additional context to reproduce No response Screenshots Traceback (most recent call last):

File "/app/pip_pypi__flytekit/flytekit/exceptions/scopes.py", line 203, in user_entry_point
    return wrapped(*args, **kwargs)
  File "/app/atomwise/...", line 266, in run_block
    block.validate_output(cmpds, result)
  File "/app/atomwise/..., line 119, in validate_output
    raise RuntimeError(

Message:

<blah>

User error. 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/flytekit/tree/master|master>

by eapolinario

<https://github.com/flyteorg/flytekit/commit/b721b5772dddcccdd22c1a60268172fac1312ca4|b721b577>

- Set cache_regions=True in the case of s3fs (#1592) flyteorg/flytekit

#3423 [BUG] ARM64 Docker Images contains x86_64 binaries (helm) Issue created by qbx2 Describe the bug I am not able to run the arm64 docker images on aws graviton instances because arm64 docker images are built in incorrect way. To check:

$ docker run -it --platform linux/arm64 -u root <http://cr.flyte.org/flyteorg/flyteadmin-release:latest|cr.flyte.org/flyteorg/flyteadmin-release:latest> sh

/ # apk add file

/ # file bin/flyteadmin
bin/flyteadmin: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, Go BuildID=pwwxVfCtJjTsZm9XA0ED/BJdCEuBm0QjhMujOZ7E7/a_vHl8mBZ4xrHPFYqAdf/on6kzeFZfsYdRjhPjzhK, stripped

Other images also have this issue, for example:

$ docker run -it --platform linux/arm64 -u root <http://cr.flyte.org/flyteorg/datacatalog:latest|cr.flyte.org/flyteorg/datacatalog:latest> sh

/ # apk add file

/ # file bin/datacatalog
bin/datacatalog: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, Go BuildID=YBzDJD8nguzh9dRW4GPp/iKNJqrMQzbqKL7lVR_L0/_wLIwVTI2EO3sXJO2Sup/5m-2xGfqxh4rTZlXehX4, not stripped

I did not check every images, but I'm pretty sure that most images have the issue. Expected behavior ARM64 Docker Images should not contain x86_64 binaries. They should contain arm64 binaries instead. Graviton instances should be able to run flyte using docker. 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

#744 [UI Feature] Add full-list log output to execution detail panel Pull request opened by james-union flyteorg/flyte#3592 mono.mov How to test this: Even though I had a discussion with Dan, but I could not create a workflow to generate the error messages real time so I just test this with some generated text (increasing by time interval on the video) This PR includes flyteidl version updates (to v1.3.18). 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 Added a new component ScrollableMonospaceText Tracking Issue flyteorg/flyte#3592 flyteorg/flyteconsole Codecov: 59.37% of diff hit (target 66.40%) GitHub Actions: Build & Push FlyteConsole Image GitHub Actions: Get Release Tag GitHub Actions: Generate Release DCO: DCO ✅ 6 other checks have passed 6/11 successful checks

1 new commit pushed to

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

by pingsutw

<https://github.com/flyteorg/flytekit/commit/f83e4b366ae03b2ed087cb22f868ba27e7639c3a|f83e4b36>

- Set default ComSpec when running on Windows (#1595) flyteorg/flytekit

#333 Adding cleanupOnFailure to PhaseInfo Pull request opened by hamersaw TL;DR Adding a

cleanupOnFailure

field to the

PhaseInfo

reported by each task evaluation. This is useful to track situations where Flyte marks a task as

FAILED

but it should still be cleaned up during the workflow abort. An example is

ImagePullBackoff

where a k8s

Pod

requests an image that does not exist. Flyte will mark the

Pod

as a failure, but it is not cleaned up until the workflow CR is garbage collected. The `Pod`will continually reattempt to download the missing image (with backoff) maintaining it's hold on resources. 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#3239 Follow-up issue NA flyteorg/flyteplugins Codecov: 62.64% (-0.03%) compared to f5f4182 Codecov: 33.33% of diff hit (target 62.67%) ✅ 4 other checks have passed 4/6 successful checks

#557 Maintaining Interruptible and OverwriteCache for reference launchplans Pull request opened by hamersaw TL;DR The

Interruptible

and

OverwriteCache

flags should be maintained through the

ExecutionSpec

when running reference launchplans in from a workflow. 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#3550 Follow-up issue NA flyteorg/flytepropeller GitHub Actions: Build & Push Flytepropeller Image GitHub Actions: Goreleaser GitHub Actions: Bump Version ✅ 11 other checks have passed 11/14 successful checks

#745 chore: fix details panel card padding Pull request opened by ursucarina TL;DR Fixes details panel card padding 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 Added padding to the panel content Tracking Issue NA flyteorg/flyteconsole GitHub Actions: Build & Push FlyteConsole Image GitHub Actions: Get Release Tag GitHub Actions: Generate Release ✅ 8 other checks have passed 8/11 successful checks

#396 Add default limit to Task Resources Pull request opened by wild-endeavor TL;DR Add a default limit

TaskResourceSpec

section to

TaskResourceAttributes

. There's been lots of confusion around Admin's existing behavior of setting the a task's limits to the same as the requests. Adding a default limit section to admin explicitly will fix this. Limits from now on will just be used for checking that the default requests and default limits conform to the system level limit. 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 NA Tracking Issue flyteorg/flyte#3574 flyteorg/flyte#3467 flyteorg/flyteidl ✅ All checks have passed 13/13 successful checks

#985 fix whylogs docs Pull request opened by cosmicBboy typo in installation instructions flyteorg/flytesnacks GitHub Actions: Create a list of packages GitHub Actions: Docs Warnings ✅ 2 other checks have passed 2/4 successful checks

#1596 Remove extraneous debug statement Pull request opened by wild-endeavor 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/flytekit ✅ All checks have passed 30/30 successful checks

1 new commit pushed to

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

by pingsutw

<https://github.com/flyteorg/flytekit/commit/0a34f4f968e8cbaf62aae9d9227aadcb99b30f32|0a34f4f9>

- Feature: add activate-launchplan command to pyflyte (#1588) flyteorg/flytekit

#2842 [Docs] Change limit set in the platform configuration [1Gi] for memory in sandbox Issue created by SmritiSatyanV Description You can change the set limit using the below commands:

$ k edit cm flyte-admin-config

  task_resource_defaults.yaml: |
    task_resources:
      defaults:
        cpu: 100m
        memory: 500Mi
        storage: 500Mi
      limits:
        cpu: 2
        gpu: 1
        memory: 1Gi <- change this value
        storage: 20Mi

Add it in the environment guide setup or troubleshooting guide. The above config works for sandbox. For demo cluster, you can't change config at runtime. Hence, change the config and build a custom image.

$ git clone git@github.com:flyteorg/flyte.git
$ cd flyte
$ vim flyte.yaml (update config)
$ docker build -t user_name/sandbox-lite-test -f docker/sandbox-lite/Dockerfile . # Build image
$ docker push user_name/sandbox-lite-test
$ flytectl demo start --image user_name/sandbox-lite-test

OR

docker exec

into the cluster and modify the flyte.yaml file.

docker run -v my_flyte.yaml:flyte.yaml …

docker restart flyte-sandbox

flyteorg/flyte

#1597 pyflyte run imperative workflow Pull request opened by pingsutw TL;DR Fix the bug that was reported in the community sync.

AttributeError: 'ImperativeWorkflow' object has no attribute 
'instantiated_in'

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

1 new commit pushed to

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

by jsonporter

<https://github.com/flyteorg/flyteconsole/commit/bbe8d51251722e9f6a3cdf77b690648603cdb0a1|bbe8d512>

- chore: fix details panel card padding (#745) flyteorg/flyteconsole

1 new commit pushed to

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

by pingsutw

<https://github.com/flyteorg/flytesnacks/commit/094211ae56c36d4191e6309e643f9430721886c3|094211ae>

- fix whylogs docs (#985) flyteorg/flytesnacks

1 new commit pushed to

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

by eapolinario

<https://github.com/flyteorg/flytekit/commit/c363881c4aeb4fe9a4479e5ff2eef7c03c13e87e|c363881c>

- nit (#1596) flyteorg/flytekit

1 new commit pushed to

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

by eapolinario

<https://github.com/flyteorg/flyteidl/commit/c7ae927f73df9ecdbbf01b6021836b9b2079e527|c7ae927f>

- Migrate to buf remote plugins v1 (#393) flyteorg/flyteidl