Hi team, Is this expected? or are there workarounds?

flytekit.core.type_engine.RestrictedTypeError: Transformer for type <class 'tuple'> is restricted currently

Is it possible to construct a "dynamic workflow" using the Flyte "imperative" API? The DAGs I want to execute will be described by some rpc call:

get_dag( job_input ) ->   DAG of task inputs

In Flyte, I need to read the response, which is a DAG represented as an adjacency list. The directed edges say which tasks need to be executed before which other tasks, and each node in the graph has a payload which is the input to the task. This

get_dag()

call happens at runtime, so I understand from [1] that I can do this:

@dynamic
start_workflow(...) -> ...:
   dag = get_dag(...)
   ???

@workflow
def my_workflow(...) -> None
  return start_workflow(...)

but I can't figure out how to use "imperative workflows"[2] at the same time. How do I get a `

wf = Workflow(name="my.imperative.workflow.example")

? I did find the dynamic workflow in the API docs: https://docs.flyte.org/projects/flytekit/en/latest/generated/flytekit.dynamic.html But how do I use it? Do I need to create a "sub workflow" or is there a more direct way? [1] https://docs.flyte.org/projects/cookbook/en/stable/auto/core/control_flow/dynamics.html [2] https://docs.flyte.org/projects/cookbook/en/stable/auto/core/flyte_basics/imperative_wf_style.html

looking to set maxMessageSizeBytes option as mentioned here in a more declarative way (i.e. via Helm), it doesn't seem clear how to do this. Any pointers?

Hello, is there a way to handle "workflow termination from UI" from python task plugins? Our plugin spins up a

dask

cluster and we would like to ensure that the cluster gets cleaned up in every case that the workflow finishes (successful completion, failure, or user terminates). We are currently using the dask-kubernetes

KubeCluster

operator to create the cluster in

pre_execute

, then close everything in the

post_execute

(pseudo-code). However,

post_execute

doesn't get called when a user terminates from the UI, so we are seeing the

dask

cluster consistently hang. Thanks for your help!

Just to be sure, when we run

flytectl update task-resource-attribute

does that setting still have to be within whatever limits we set in the Admin config map, right? We've tried to up the task-resource-attribute but when registering the workflow still get

Requested MEMORY limit [1Ti] is greater than current limit set in the platform configuration [512Gi]. Please contact Flyte Admins to change these limits or consult the configuration

Because if I call

flytectl get task-resource-attribute

it does say

{"project":"<>","domain":"<>","defaults":{"cpu":"500m","memory":"1Gi"},"limits":{"cpu":"2","memory":"1024Gi"}}

We are deploying Flyte this week 🎉 Main pieces are running but configuration needs some adjustments. I have one question regarding TLS certificates. Is it required for grpc/flytectl to set up TLS on the Flyte endpoint? I get the following error with the current config. Is it only due to missing tls configuration or other reasons?

flytectl get projects   
Error: Connection Info: [Endpoint: dns:///flyte.internal.n0q.eu, InsecureConnection?: true, AuthMode: ClientSecret]: rpc error: code = Unavailable desc = timed out waiting for server handshake
{"json":{},"level":"error","msg":"Connection Info: [Endpoint: dns:///flyte.internal.n0q.eu, InsecureConnection?: true, AuthMode: ClientSecret]: rpc error: code = Unavailable desc = timed out waiting for server handshake","ts":"2022-11-08T16:12:04+01:00"}

#~/.flyte/config.yaml
admin:
  # For GRPC endpoints you might want to use dns:///flyte.myexample.com
  endpoint: dns:///flyte.internal.eu
  insecure: true
  insecureSkipVerify: true

Getting SSL error while running pyflyte register command for an AWS EKS setup. ssl.SSLError: [SSL: WRONG_VERSION_NUMBER] wrong version number (_ssl.c:1131)

Hi we recently had a few large workflows get in a bad state. I let them run for a long time and eventually had to abort a few. Nothing is running anymore but the flytepropeller logs are flooded with the following

Failed to record taskEvent, error [EventAlreadyInTerminalStateError: conflicting events; destination: ABORTED, caused by [rpc error: code = FailedPrecondition desc = invalid phase change from FAILED to ABORTED for task execution

i feel like it is related to this ticket. My main question however is When something like this happens what is the best way to reset flytepropeller? I tried restarting the pod but it seems like is a problem with the database state?

Hello flyte team, we are encountering the following error when running one of our larger map-tasks. We did not encounter this error on previous map-tasks but we are seeing this reproducibly (last 2 runs) now. Any thoughts on the cause?

Hi, is it possible to manually hard delete executions through

flytectl

? I have 3 workflow executions that have been stuck in

ABORTING

for the past ~2 hours.