#1545 Filter out remote entity when generating pb Pull request opened by honnix TL;DR Skip remote entity when generating protobuf files. cc @sonjaer 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 should not generate protobuf files for remote entities. Tracking Issue Closes flyteorg/flyte#3386 Follow-up issue NA flyteorg/flytekit 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 GitHub Actions: docs ✅ 2 other checks have passed 2/27 successful checks

#3315 Fix maptask caching in FlyteConsole Issue created by cosmicBboy Map tasks in the console are not showing the correct cached status: This issue requires both backend and frontend fixes: • Backend PR: flyteorg/flyteplugins#300 • Issue for Frontend fix: flyteorg/flyteconsole#644 flyteorg/flyte

#592 Signal: Add Resume button to execution details panel Issue created by jsonporter To support the signaling uI we want to add a "resume" button the execution detail pane (slide-out nav) that will detect if the execution is a gated node and if so, render a "resume" button. Clicking the button will open the resume form. Acceptance Criteria: • Resume button only displays on gated nodes in "paused" phase • Clicking button opens the Resume form UX flyteorg/flyteconsole

#591 Signal: Add signaling UI to Graph Issue created by jsonporter We want to add the signaling UI to the graph. The button should behave similar to the graph legend where a user can click to open and view. There container should use flex to fit the amount of items - starting at a tight for each item until it reaches its max-height (refer to comps) at which point the container should stop growing and the items should scroll. Clicking one of the items should: 1. Present the launch form to resume the execution if the user clicks on (directly) on the resume icon 2. Expand the execution details panel (slide-out) if the user clicks anywhere else in the item; there is currently no resume button in the execution detail panel yet but there will be (in a later ticket) so simply triggering the panel to open is enough for this ticket. Updated: ticket for execution details slide out #592 flyteorg/flyteconsole

#586 Signal: Add Signal UX to node list view Issue created by jsonporter To support signaling, we need to add a "resume" icon and new phase to node-list view. Requirements: • Display phase as "Paused" • Display "resume" icon on hover flyteorg/flyteconsole

#627 Spike: integration tests research Issue created by ursucarina 1. Investigate existing end-to-end testing frameworks. 2. Add a test to make sure that NodeExecutionsTable shows updated data (and query was not read from cache) after execution was relaunched. flyteorg/flyteconsole

#628 Spike: Look into envoy Issue created by ursucarina https://medium.com/swlh/ditching-rest-with-grpc-web-and-envoy-bfaa89a39b32 flyteorg/flyteconsole

#618 Relaunch/recover execution with same clusterPool as original execution Issue created by iaroslav-ciupin flyteidl was recently updated to support specifying cluster pool when creating new execution. We need to make sure when we recover/relaunch execution, same cluster pool is sent in CreateExecution request. On hitting relaunch/recover button, new CreateExecution request must take same cluster pool as original execution. flyteorg/flyteconsole

#2960 [UI Feature] Issue created by iaroslav-ciupin Motivation: Why do you think this is important? flyteidl was recently updated to support specifying cluster pool when creating new execution. We need to make sure when we recover/relaunch execution, same cluster pool is sent in CreateExecution request. Goal: What should the final outcome look like, ideally? On hitting relaunch/recover button, new CreateExecution request must take same cluster pool as original execution. 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

#617 [UI][Refactor] After NodeExecutionsTable refactor filters don't work with undefined executions Issue created by olga-union flyteorg/flyteconsole

#608 Improve project domain level workflow execution config display Issue created by wild-endeavor Project Level Settings (Temporary patch) Current state Currently console does a get request on the project domain level workflow execution attributes (

<http://localhost:8088/api/v1/project_domain_attributes/flytesnacks/staging?resource_type=6>

for example). If something is found, it shows this Change We would like to change it so that it also runs this request:

<http://localhost:8088/api/v1/project_attributes/flytesnacks?resource_type=6>

This request is special because unlike the higher specificity requests (like the project-domain one above and project/domain/workflow/lp requests), this endpoint will also merge in and return settings from Admin's system level configuration. This is helpful for the user. This ticket is to add a call to that endpoint, and merge in the existing call, with the existing project-domain call taking higher priority of course. Keep in mind that you should do a deep check on objects. That is, if the security context object is there, but both role and service account are empty strings, then don't use it ofc. See flyteorg/flyte#2322 for the backend changes and more information, but keep in mind the information on there is also a bit confusing because there is a longer term project described in that issue. flyteorg/flyteconsole

#604 [UI] Add/fix tests related to NodeExecutionsTable refactor Issue created by olga-union flyteorg/flyteconsole

#603 [UI] Refactor NodeExecutionsTable to use the same data as other execution tabs Issue created by olga-union flyteorg/flyteconsole

#600 FlyteConsole - ValueError: Generic Type typing.Union not supported currently in Flytekit Issue created by sakthi-tech4th Hi, I'm trying to launch a workflow in the FlyteConsole (Sandbox Environment in a Windows Machine) and I'm getting the above mentioned error for a task that accept pandas DataFrames (2 data frames) and returns a DataFrame.

[1/1] currentAttempt done. Last Error: USER::Pod failed. No message received from kubernetes.

[adbrq7s7x2kbwln2k5df-n0-0] terminated with exit code (1). Reason [Error]. Message:  
a_worflows.py", line 211, in  
def process_data_frames(lc_df: pd.DataFrame=None, data_frame: pd.DataFrame=None)->pd.DataFrame:  
File "/usr/local/lib/python3.9/site-packages/flytekit/core/task.py", line 209, in task  
return wrapper(_task_function)  
File "/usr/local/lib/python3.9/site-packages/flytekit/core/task.py", line 193, in wrapper  
task_instance = TaskPlugins.find_pythontask_plugin(type(task_config))(  
File "/usr/local/lib/python3.9/site-packages/flytekit/core/tracker.py", line 30, in call  
o = super(InstanceTrackingMeta, cls).call(*args, **kwargs)  
File "/usr/local/lib/python3.9/site-packages/flytekit/core/python_function_task.py", line 118, in init  
super().init(  
File "/usr/local/lib/python3.9/site-packages/flytekit/core/python_auto_container.py", line 72, in init  
super().init(  
File "/usr/local/lib/python3.9/site-packages/flytekit/core/base_task.py", line 389, in init  
interface=transform_interface_to_typed_interface(interface),  
File "/usr/local/lib/python3.9/site-packages/flytekit/core/interface.py", line 210, in transform_interface_to_typed_interface  
inputs_map = transform_variable_map(interface.inputs, input_descriptions)  
File "/usr/local/lib/python3.9/site-packages/flytekit/core/interface.py", line 318, in transform_variable_map  
res[k] = transform_type(v, descriptions.get(k, k))  
File "/usr/local/lib/python3.9/site-packages/flytekit/core/interface.py", line 332, in transform_type  
return _interface_models.Variable(type=TypeEngine.to_literal_type(x), description=description)  
File "/usr/local/lib/python3.9/site-packages/flytekit/core/type_engine.py", line 611, in to_literal_type  
transformer = cls.get_transformer(python_type)  
File "/usr/local/lib/python3.9/site-packages/flytekit/core/type_engine.py", line 584, in get_transformer  
raise ValueError(f"Generic Type {python_type.origin} not supported currently in Flytekit.")  
ValueError: Generic Type typing.Union not supported currently in Flytekit.

the data frames has columns with strings, consequently the dtypes for these columns were object. Would it be possible, for some one to let me know what is the problem or if I'm missing something? Of if this because, I'm running it in a Windows machine? Thanks and Regards flyteorg/flyteconsole

#598 Refactor Nav Components Issue created by ursucarina flyteorg/flyteconsole

#597 Feat: Change Graph UI to display subworkflow nodes differently. Issue created by jsonporter Users have said that the current graph UI that shows nested/subworkflows as a solid grey is confusing - it does not show the phase of the (parent) execution and its not clear that its a subworkflow. We want to change this so that: • Subworkflow node (collapsed) color reflects it's phase • Subworkflow node (collapsed) is not solid and instead has a border; border style is TBD. flyteorg/flyteconsole

#587 Signal: Add Signal resume resume view Issue created by jsonporter The signal resume modal window will render a single input (of any

Literal

type) that the user will enter to resume that node. The inputs should be the same as the launch window (ie, rendering with a type and empty-text helpers) and should validate in the same manner as the launch form. Additionally, we should show the node's input. The comps are currently out of date but will soon be updated to no longer click-to-show and instead will always ben shown as json (in the same manner we display node inputs in the node execution detail panel). Note: will update comps but now render inputs as in execution details panel Requirements: • Correctly rendering input (same as launch form) • Validates input • Displays node's input flyteorg/flyteconsole

#3436 Investigate noneType test failures Issue created by ursucarina After fixing a prop error in tests in this PR ,, we are getting actual test failures for noneTypes flyteorg/flyte

#54 Add support upload collections Pull request opened by pingsutw TL;DR Add support upload collection (a list). When using raw container in the map task, flytepropeller expect the subtask upload a list. 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 https://flyte-org.slack.com/archives/CP2HDHKE1/p1678230956906899 Follow-up issue NA flyteorg/flytecopilot GitHub Actions: Unit Tests / Run Unit Test GitHub Actions: Build & Push Flyte copilot Image / Push to Github Registry GitHub Actions: Lint / Run Lint GitHub Actions: Check Go Gennerate / Go Generate GitHub Actions: Dry run goreleaser ✅ 2 other checks have passed 2/7 successful checks

#3438 Bug: Dict value loses 1 trailing character on UI Launch. Issue created by jsonporter User reported that when working with a dictionary type - the last/trailing character is lost on launch. To repo this error launch an execution with a datatype of dictionary, then once that execution has been launched view the inputs/outpus tab and see that the last character is lost. flyteorg/flyte

#554 Recent runs should be separated by workflow version Issue created by hamersaw In the workflow view under "Recent Workflow Version" there is a section for "Recent Runs". Currently this displays all runs of the workflow under each version. In the below example I ran each version once, so I would expect each "Recent Runs" in the "Recent Workflow Version" to only have a single failure, rather than all 3. flyteorg/flyteconsole

#3439 [BUG] [Graph] Cannot read properties of null/undefined for workflows referencing launch plans Issue created by MorpheusXAUT We're currently seeing two variants of what appears to be an issue similar to flyteorg/flyteconsole#378: error1 error2 The first error encountered was the one reported by our developers, the second one was my attempt to reproduce this issue in a sample workflow. Both errors were encountered using flyteconsole

v1.1.7

. I believe the culprit to be launch plan references in workflows with at least one other sub-workflow called. I've used the launchplan example from the Flyte docs to reproduce the issue. The following workflow caused the second error message:

import calendar
import datetime

from flytekit import dynamic, task, workflow, LaunchPlan


@task
def greet(day_of_week: str, number: int, am: bool) -> str:
    greeting = "Have a great " + day_of_week + " "
    greeting += "morning" if am else "evening"
    return greeting + "!" * number


@workflow
def go_greet(day_of_week: str, number: int, am: bool = False) -> str:
    return greet(day_of_week=day_of_week, number=number, am=am)


morning_greeting = LaunchPlan.create(
    "morning_greeting",
    go_greet,
    fixed_inputs={"am": True},
    default_inputs={"number": 1},
)


@workflow
def test_flyteconsole_graph_launchplanref() -> None:
    go_greet(day_of_week="Monday", number=1, am=True) # Important, workflow must have sub-workflows!

    today = datetime.datetime.today()
    for n in range(7):
        day = today + datetime.timedelta(days=n)
        weekday = calendar.day_name[day.weekday()]
        if day.weekday() < 5:
            print(morning_greeting(day_of_week=weekday))
        else:
            print(morning_greeting(number=3, day_of_week=weekday))

If I remove the first line from

test_flyteconsole_graph_launchplanref

(and thus don't have any other sub-workflows), the graph renders just fine. Our production workflow produces the following stacktrace:

TypeError: Cannot read properties of null (reading 'resourceType')
    at t.checkIfObjectsAreSame (main-56c8d9de.js:1:349519)
    at t.getSubWorkflowFromId (main-56c8d9de.js:1:350236)
    at m (main-56c8d9de.js:1:347158)
    at p (main-56c8d9de.js:1:347537)
    at f (main-56c8d9de.js:1:348547)
    at m (main-56c8d9de.js:1:347200)
    at p (main-56c8d9de.js:1:347537)
    at f (main-56c8d9de.js:1:348589)
    at t.transformerWorkflowToDag (main-56c8d9de.js:1:348639)
    at main-56c8d9de.js:1:345223

The actual stack trace displayed in my reproduction attempt leads to a slightly different place when accessing the graph:

TypeError: Cannot read properties of undefined (reading 'n0-0-n0')
    at main-56c8d9de.js:1:344707
    at t.WorkflowGraph (main-56c8d9de.js:1:344858)
    at we (react-dom.production.min.js:84:293)
    at zj (react-dom.production.min.js:226:496)
    at Th (react-dom.production.min.js:152:223)
    at tj (react-dom.production.min.js:152:152)
    at Te (react-dom.production.min.js:146:151)
    at react-dom.production.min.js:61:68
    at unstable_runWithPriority (react.production.min.js:25:260)
    at Da (react-dom.production.min.js:60:280)

Interestingly enough, the "Nodes" tab is already partially broken though: error3 The stack trace printed when loading the nodes points to the same location as our production workflow. It seems to me that

parseNode

in

components/WorkflowGraph/transformerWorkflowToDag.tsx

only seems to handle `subworkflowRefs`, but not

launchplanRefs

, thus passing on

null

as

id

to `getSubWorkflowFromId` and subsequently `checkIfObjectsAreSame`. The nodes causing the crash have no

subworkflowRefs

, but a

launchplanRef

instead, according to my hastily slapped on debug logging: launchplanRef If the workflow executed doesn't have any sub-workflows, we're not running into this issue as the comparison containing `checkIfObjectsAreSame` is not run at all. I was able to "fix" this by having

checkIfObjectsAreSame

check for `null`/`undefined` before its `for` loop:

export const checkIfObjectsAreSame = (a, b) => {
  if ((!a && b) || (a && !b)) {
    return false;
  } else if (!a && !b) {
    return true;
  }
  for (const k in a) {
    if (a[k] !== b[k]) {
      return false;
    }
  }
  return true;
};

Above change "fixes" the graphs (and nodes view), however I feel like that's only halfway to solving the actual issue 😅 Would that additional check be enough in this case (if so, I can open a tiny PR, if you'd like), or must

parseNode

handle the

launchplanRefs

as well? I'm happy to help with further testing/development if so desired, but would appreciate some pointers on how to best proceed 🙂 flyteorg/flyte

#3440 [BUG] Latest task status may not always be reported Issue created by hamersaw Describe the bug Every time FlytePropeller checks a task status it constructs a pluginRequestedTransition which contains information regarding the state change of the plugin. This information is used to determine whether the current state has altered from the previously reported state which is determined using the

Phase

and

PhaseVersion

information that each plugin reports. If this has not changed (based on these two field) then FltyePropeller immediately returns and bypasses sending a TaskExecutionEvent reporting the task state to FlyteAdmin. The problem is that plugins may report new status with the same

Phase

and

PhaseVersion

but with an updated

Reason

, the

Reason

field contains information regarding task execution. One such scenario is where a k8s Pod requests more resources than are available within the cluster. The initial

TaskExecutionEvent

will report a

Reason

"task submitted to K8s". In a subsequent evaluation the plugin updates this

Reason

to "Unschedulable:0/1 nodes are available: 1 Insufficient memory.", however this is never reported to FlyteAdmin because the

Phase

and

PhaseVersion

remain the same. Expected behavior The FlyteConsole UI should always display the latest status. This requires FlytePropeller to correctly identify an update and therefore to send an event to FlyteAdmin reporting the change. Additional context to reproduce Start a workflow with resource requests larger than what is available in the cluster. In the task status' pane in the UI it will always display the "RUNNING" phase with a reason of "task submitted to K8s".

@task(requests=Resources(mem="12G"))
def say_hello_resources(name: str) -> str:
    return f"hello {name}"

@workflow
def my_wf_resources(name: str) -> str:
    res = say_hello_resources(name=name)
    return res

Screenshots Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte

#968 Add gate node example to the control flow section of flytesnacks Pull request opened by cosmicBboy fixes flyteorg/flyte#3270 flyteorg/flytesnacks GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/kubernetes/ray_example) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/kubernetes/pod) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/kubernetes/kftensorflow) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/kubernetes/kfpytorch) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/kubernetes/kfmpi) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/kubernetes/k8s_spark) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/kubernetes/k8s_dask) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/flytekit_plugins/whylogs_examples) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/flytekit_plugins/sql) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/flytekit_plugins/papermilltasks) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/flytekit_plugins/pandera_examples) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/flytekit_plugins/onnx_examples) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/flytekit_plugins/modin_examples) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/flytekit_plugins/mlflow_example) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/flytekit_plugins/greatexpectations) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/flytekit_plugins/duckdb_examples) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/flytekit_plugins/dolt) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/flytekit_plugins/dbt_example) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/external_services/databricks) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/aws/sagemaker_training) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/aws/sagemaker_pytorch) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/aws/batch) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/integrations/aws/athena) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/core) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/case_studies/ml_training/spark_horovod) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/case_studies/ml_training/pima_diabetes) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/case_studies/ml_training/nlp_processing) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/case_studies/ml_training/mnist_classifier) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/case_studies/ml_training/house_price_prediction) GitHub Actions: Serialize & Register Flytesnacks workflow / Serialize Example (cookbook/case_studies/feature_engineering/feast_integration) ✅ No checks have passed 0/30 successful checks

#1546 ignore, test pr Pull request opened by wild-endeavor on <!date^1678398092^{date_short}|2023-03-09T21:41:32Z> flyteorg/flytekit ✅ All checks have passed 30/30 successful checks

#329 Add support raw container in the map task Pull request opened by pingsutw TL;DR When using regular task in the map task, the entrypoint is

pyflyte-map-execute

. it does two things before running the task. 1. Update sub task input / output interface to list interface 2. Append job id to output prefix However, when using raw container, the entrypoint will not be

pyflyte-map-execute

. Therefore, we should update the output prefix for copilot, and support upload collection in the copilot. 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 https://flyte-org.slack.com/archives/CP2HDHKE1/p1678230956906899 Follow-up issue NA flyteorg/flyteplugins GitHub Actions: Run tests and lint ✅ 3 other checks have passed 3/4 successful checks

#1547 Add support raw container in the map task Pull request opened by pingsutw TL;DR 1. Add support raw container in the map task 2. Use default command of the raw container in the map task instead of replacing it with

pyflyte-map-execute ....

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 Here is an example

import typing
from typing import List

from flytekit import map_task, task, workflow, ContainerTask, kwtypes

calculate_ellipse_area_shell = ContainerTask(
    name="ellipse-area-metadata-python",
    input_data_dir="/var/inputs",
    output_data_dir="/var/outputs",
    inputs=kwtypes(a=int),
    outputs=kwtypes(area=float),
    image="pingsutw/raw-container:v9",
    command=[
        "python",
        "test.py",
        "{{.inputs.a}}",
        "/var/outputs",
    ],
)


@task
def coalesce(b: List[str]) -> str:
    coalesced = "".join(b)
    return coalesced


@task
def g_l(n: int) -> List[int]:
    res = []
    for i in range(n):
        res.append(i)
    return res


@workflow
def wf(n: int = 2):
    l = g_l(n=n)
    map_task(calculate_ellipse_area_shell)(a=l)


if __name__ == "__main__":
    result = wf()

• dockerfile

FROM python:3.10-slim-buster

WORKDIR /root

COPY *.py /root/

• test.py

import math
import sys
import os

def write_output(output_dir, output_file, v):
    with open(f"{output_dir}/{output_file}", "w") as f:
        f.write(str(v))


def calculate_area(a, b):
    return math.pi * a * b


def main(a, output_dir):
    # parse list
    li = a.strip('][').split(',')
    res = [eval(i) for i in li]

    # get the job index
    index = int(os.environ.get(os.environ.get("BATCH_JOB_ARRAY_INDEX_VAR_NAME")))

    area = calculate_area(res[index], 3)

    write_output(output_dir, "area", f"{area}")
    write_output(output_dir, "_SUCCESS", "")


if __name__ == "__main__":
    a = sys.argv[1]
    output_dir = sys.argv[2]

    main(a, output_dir)

Tracking Issue https://flyte-org.slack.com/archives/CP2HDHKE1/p1678230956906899 Follow-up issue flyteorg/flytecopilot#54 flyteorg/flyteplugins#329 flyteorg/flytekit ✅ All checks have passed 30/30 successful checks

1 new commit pushed to

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

by wild-endeavor

<https://github.com/flyteorg/flytekit/commit/7c3c255655d25e70988028d8773b034c7519d6e8|7c3c2556>

- Prefer FLYTE_ prefixed AWS creds env vars (#1523) flyteorg/flytekit

Release - [Beta] Prefer FLYTE_ prefixed env vars for aws access New release published by wild-endeavor flyteorg/flytekit

1 new commit pushed to

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

by pingsutw

<https://github.com/flyteorg/flytekit/commit/aee20eac7d0d65874b5f3c04dc1a5ddfed591063|aee20eac>

- Filter out remote entity when generating pb (#1545) flyteorg/flytekit