I'm trying to setup my dev environment. I installed flytekit and the requirements for flytesnacks in an venv as recommended here: https://docs.flyte.org/projects/cookbook/en/latest/userguide_setup.html However, my pyflyte looks broken. I can't run any commands as they all fail with: ModuleNotFoundError: No module named 'flyteidl.service.external_plugin_service_pb2_grpc' That module definitely isn't installed in my venv, and I don't see the proto for it in the flyteidl repo either. Have I installed a wrong version of flytekit somehow?

I'm looking to interact with the flyte REST API and admin database to be able to query for execution input / output data. I have 2 questions: 1. How to query input / output data from the database? I can find references to proto input files, but can't find any reference to where the outputs exist. I also wonder if there is an example of decoding the downloaded proto files. 2. How to authenticate the REST API? I found the API swagger docs, but I neither see examples of using the API or how to authenticate. I can generate JWT's easily enough against our IdP, but passing that as a standard Authorization header doesn't appear sufficient.

Hi Team, We are getting the below error when we are using pandascursor to get the Athena query result in the flyte workflow, which is only occurring when we use PyAthena >3.0.10. However below python code works fine with other application but doesn't work inside flyte. ERROR in Organization Cluster:

__init__() got an unexpected keyword argument 'connection'

We are using the 'production flow' approach of registration pattern. 1. We have poetry project with the workflows and Docker file. 2. In poetry project we are using the below dependencies.

[tool.poetry.dependencies]
python = "~3.9"
botocore = "1.31.17"
flytekit = "1.10.2"
flytekitplugins-deck-standard = "1.10.2"
flytekitplugins-papermill = "1.10.2"
flytekitplugins-pod = "1.10.2"
kubernetes = "^28.1.0"
pyathena = "3.1.0"

3. When we build the docker and running the python code inside the docker its working fine.

from flytekit import task, workflow
from pyathena import connect
from pyathena.pandas.cursor import PandasCursor

@task
def test1():
    access_key = ""
    secret_key = ""
    conn  = connect(aws_access_key_id=access_key,
               aws_secret_access_key=secret_key,
                  s3_staging_dir="<s3://drd-029652062076-28e0/>",region_name="us-east-1",
                              cursor_class=PandasCursor).cursor()
    query = "SELECT * FROM default.flytetesting limit 10;"
    df = conn.execute(query).as_pandas()
    print(df.head(5))

@workflow
def hello_world_wf():
    test1()
    print("success")


if __name__ == "__main__":
    print(f"Running wf() {hello_world_wf()}")

4. We are registering workflows using below commands

- pyflyte --pkgs workflows package --image public.ecr.aws/<application-name>/flyte:latest -f

- git rev-parse HEAD 

- flytectl register files --project my-project --domain development --archive flyte-package.tgz --version "${git rev-parse HEAD}"

Is there internal some circular dependency from flyte causing this issue? I tried the above project in my local setup to test with basic installation. I am getting below error in local setup. ERROR in local flyte cluster:

[1/1] currentAttempt done. Last Error: USER::Pod failed. No message received from kubernetes.
[f24327f2f9d41438aaef-n0-0] terminated with exit code (128). Reason [StartError]. Message: 
failed to create containerd task: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "pyflyte-fast-execute": executable file not found in $PATH: unknown.

Anybody faced this issue before and knows what could be the reason ?

i installed the flyteorg/flyte-binary v1.7.0 helm chart in my local k8s cluster, when enabled the auth, the flyte container can not started , the error is "{"json":{"src":"start.go:58"},"level":"fatal","msg":"Flyte native scheduler failed to start due to async future was canceled","ts":"2023-06-26T014846Z"}" how to deal with it??

I need some help getting launchplans with a cronjob configured to work: I first register a launchplan with a

* * * * *

cron expression via flyteremote. After that, the flyte UI still shows

This workflow has no schedules

, as expected. I then execute

flytectl update launchplan -p default -d development --version fabio-cron-2a3fb7f-dirty-BQN44 cron_hydra_workflow_cfg_flyte_workflows.collaborative_filtering.workflow_0 --activate

which gives:

updated launchplan successfully on cron_hydra_workflow_cfg_flyte_workflows.collaborative_filtering.workflow_0%

In the UI, the schedule is updated as well, it now says

Every minute

. Problem: I’m not seeing any executions. The flyte admin shows this in the logs after I activated the launchplan:

{"json":{"src":"launch_plan.go:108"},"level":"info","msg":"Adding resource type for unspecified value in request: [%+v]id:\u003cproject:\"default\" domain:\"development\" name:\"cron_hydra_workflow_cfg_flyte_workflows.collaborative_filtering.workflow_0\" version:\"fabio-cron-2a3fb7f-dirty-BQN44\" \u003e state:ACTIVE ","ts":"2022-03-31T18:13:01Z"}
{"json":{"src":"log.go:42"},"level":"warning","msg":"Failed to parse authenticated client metadata when creating audit log","ts":"2022-03-31T18:13:01Z"}
{"json":{"src":"log.go:91"},"level":"info","msg":"Recording request: [{\"Principal\":{\"Subject\":\"\",\"ClientID\":\"\",\"TokenIssuedAt\":\"0001-01-01T00:00:00Z\"},\"Client\":{\"ClientIP\":\"\"},\"Request\":{\"Method\":\"UpdateLaunchPlan\",\"Parameters\":{\"domain\":\"development\",\"name\":\"cron_hydra_workflow_cfg_flyte_workflows.collaborative_filtering.workflow_0\",\"project\":\"default\",\"version\":\"fabio-cron-2a3fb7f-dirty-BQN44\"},\"Mode\":1,\"ReceivedAt\":\"2022-03-31T18:13:01.578706629Z\"},\"Response\":{\"ResponseCode\":\"OK\",\"SentAt\":\"2022-03-31T18:13:01.597983728Z\"}}]","ts":"2022-03-31T18:13:01Z"}

The

flytescheduler

doesn’t show any update in the logs. Does anyone have some guidance where to start debugging this? Thanks!

Hi, everyone! I was wondering: is there a simple way to execute file persistence in Flyte? My use case: I have a workflow that generates a dataset. I want to save that dataset somewhere so I can call it on my training workflow without regenerating it. Is it possible? When I return a

FlyteFile

, the path is not really obvious/human-friendly.

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

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!

👋 we launched a workflow on the UI setting max parallelism and the Flyte UI in the execution shows the

Parallelism

attribute as

5

but the workflow executed with more than 5 tasks in parallel. Are we misunderstanding the parallelism attribute or is there a bug here?