Hi flyte community, happy monday 😆 So I am trying to get some clarification on some task related question: I have a

regular python task(T1)

that calls another

regular python task(T2)

without it being dynamic; T2 is a very simple function that runs quickly. I did not want to make T1 dynamic since i didnt wanna add overhead of launching pod for T2. Also I am using T2 in a workflow as a regular python task. My question is

is it a correct way to use it?

or is it fine to call regular task from another regular task. i could create a regular python function and call that from T1 but then i need to create another wrapper for T2 which just calls the regular function and i wanted to avoid that extra stuff. From this page https://docs.flyte.org/projects/cookbook/en/latest/auto/core/flyte_basics/task.html#sphx-glr-auto-core-flyte-basics-task-py i read that

You can execute a Flyte task as any normal function.

maybe i took this statement a bit too liberally

is there ci/cd workflows in flyte, if not did you implement workflows for ci/cd

Hi all, I am trying run a task within a container that I am building within a local deployment of flyte-sandbox. This is what I run:

flytectl sandbox start --source . --imagePullPolicy IfNotPresent
flytectl sandbox exec -- docker build -t new_image .

When I run

flytectl sandbox exec -- docker images

I see my image inside of the flyte-sandbox container.

REPOSITORY                                     TAG                       IMAGE ID       CREATED          SIZE
new_image                                      latest                    044c6f6eb860   44 minutes ago   1.49GB

Within my

@task

, I reference

new_image

. When I go to run the workflow remotely, I receive the following error after about 30 seconds:

[1/1] currentAttempt done. Last Error: USER::containers with unready status: [ffdb7fdd18e544b99a24-n0-0]|Back-off pulling image "new_image:latest"

Any thoughts?

Hi all, I'm getting an OOM error and concerned the limits I'm attempting to provide aren't being taken. When I kubectl describe the pod that failed due to OOMKilled - I see that it says the pod has a memory limit of 2G. However, in the flyte-deployment-config.yaml that I deployed using helm, I have allocated for a memory limit of 8G. See attached images for screenshots of the limit and the description. None of the @tasks have any resource limits imposed. Any help would be much appreciated!

Hi there! How to increase the allowed output size of the node?

RuntimeExecutionError: failed during plugin execution, caused by: failed to execute handle for plugin [k8s-array]: output file @[] is too large [255540150] bytes, max allowed [10485760] bytes

Looking at the propeller prometheus metrics, what's the best way to capture failures/errors by plugin node? Is there a metric for that?

I follow the docs to deploy the flyte. But after I run the hello_world.py in remote, I got “Original exception: Unable to locate credentials” error. I’ve tried to search docs and issues, but found nothing about it.

Good morning! We’re trying out Dynamic tasks for distributed computing/forecasting and notice it takes over 8 minutes for Flyte to kick off the first task. Is this normal? (@Kelsey Messer FYI)

Issue: I have been following the docs here, but while running the code

unionml serve app:app --reload --model-path /tmp/model_object.pt

, I get this error on the browser

{"detail": "Method Not Allowed"}

and in the terminal, it is showing:

INFO: 127.0.0.1:64825 - "GET /predict HTTP/1.1" 405 Method Not Allowed

My Folder structure looks like this (i.e in same directory): -> app.py -> client.py -> main.py (same code as app.py) Thanks,

Bad news @Nastya Rusina, I bounced to Flyte Console

v0.55.0

and I'm back to

Failed to fetch data: invalid wire type 4 at offset 1

for

/console