Niels Bantilan
03/10/2023, 4:53 PMseunggs
03/10/2023, 5:19 PMpyflyte run
for local testing?Eric Song
03/10/2023, 5:23 PMwf_6
and wf_7
also rendered in the UI bug I don’t see in the “Nodes” tab nor the “Timeline” tab. The “Graph” tab only shows a single node which is another problem but I believe people are aware and working on that issue.
@dynamic
def wf_1(n: int) -> int:
return wf_2(n=n+1)
@dynamic
def wf_2(n: int) -> int:
return wf_3(n=n+1)
@dynamic
def wf_3(n: int) -> int:
return wf_4(n=n+1)
@dynamic
def wf_4(n: int) -> int:
return wf_5(n=n+1)
@dynamic
def wf_5(n: int) -> int:
return wf_6(n=n+1)
@dynamic
def wf_6(n: int) -> int:
return wf_7(n=n+1)
@dynamic
def wf_7(n: int) -> int:
return n+1
@workflow
def run_wf(n: int) -> int:
return wf_1(n=n)
Bosco Raju
03/10/2023, 6:07 PMFrank Shen
03/10/2023, 7:58 PMGerry Meixiong
03/10/2023, 10:54 PMGerry Meixiong
03/10/2023, 10:57 PMWorkflow execution not found in flyteadmin.
which I don’t fully understand.Eduardo Matus
03/10/2023, 11:51 PMChandrashekhar Kotekar
03/11/2023, 11:12 PMRyo M
03/12/2023, 3:03 AMkubectl get po -n flyte
shall show scheduler pod, but for me I cannot find such pods. So I get stacked now. Could you give me some advice?
$ kubectl get po -n flyte
NAME READY STATUS RESTARTS AGE
flyte-sandbox-proxy-d95874857-m8hlt 1/1 Running 0 46m
flyte-sandbox-kubernetes-dashboard-6757db879c-867nz 1/1 Running 0 46m
flyte-sandbox-docker-registry-78686dccc-vd666 1/1 Running 0 46m
flyte-sandbox-postgresql-0 1/1 Running 0 46m
flyte-sandbox-c744b94c5-5mp68 1/1 Running 1 (45m ago) 46m
flyte-sandbox-minio-645c8ddf7c-4vwxr 1/1 Running 0 46m
Ryo M
03/12/2023, 12:42 PMSamhita Alla
Lukas Bommes
03/13/2023, 9:58 AMEduardo Matus
03/13/2023, 2:27 PMseunggs
03/13/2023, 2:59 PMTypeError: 'Promise' object is not subscriptable
since flyte creates promises during packaging/deployment:
@workflow
def wf(wf_args) -> int:
print(wf_args["x"])
...
Bernhard Stadlbauer
03/13/2023, 6:25 PMViljem Skornik
03/13/2023, 9:08 PMGreg Gydush
03/13/2023, 10:47 PMseunggs
03/13/2023, 11:48 PM@dynamic
is a workflow whose DAG is created during runtime (unlike @workflow
whose DAG is created during compile time), which makes it more flexible. So my question is, what are the downsides of @dynamic
compared to a static @workflow
? Why aren’t all flyte workflows @dynamic
(kind of like how all PyTorch computational graphs are by default dynamic)? Are there meaningful performance penalties to using @dynamic
?Tal Shiri US
03/13/2023, 11:49 PM$ pyflyte run --remote example.py training_workflow \
--hyperparameters '{"C": 0.1}'
{"asctime": "2023-03-13 16:41:33,286", "name": "flytekit", "levelname": "WARNING", "message": "FlyteSchema is deprecated, use Structured Dataset instead."}
Go to <http://localhost:30080/console/projects/flytesnacks/domains/development/executions/f3f06e76414d540c0994> to see execution in the console.
On the webiste:
[1/1] currentAttempt done. Last Error: USER::containers with unready status: [f3f06e76414d540c0994-n0-0]|Back-off pulling image "<http://cr.flyte.org/flyteorg/flytekit:py3.9-1.4.2|cr.flyte.org/flyteorg/flytekit:py3.9-1.4.2>"
Anyone seen this before?Jimmy Du
03/14/2023, 12:42 AMpyflyte register
was failing because a module's path was not included in syspath. To workaround this failure and allow the registration command to complete, I added the path to PYTHONPATH
. However, when I try to run the workflow that's successfully registered, pyflyte-execute
fails in the pod that Flyte launches because that same module whose path I had included in PYTHONPATH
was not packaged into the tar file that contains the workflow logic. Does pyflyte register
support a workaround that allows me to pass in specific module paths that aren't included in the default registration logic (and package those module paths)? I would prefer not to change my project layout if possible.
Project layout:
root
|__ module_with_workflow_and_tasks
|__ build
|__ generated
|__source
|__..
|__ _module_not_loaded_
Update: I've temporarily worked around the issue by adding init.py to every subdirectory (build, generated, source) and adding the path to module_not_loaded as an additional argument to pyflyte register
Eduardo Matus
03/14/2023, 1:45 AMEna Škopelja
03/14/2023, 9:51 AM{
"json": {
"exec_id": "a98zvdbl4hzdwn95f7xv",
"ns": "development",
"res_ver": "381075629",
"routine": "worker29",
"wf": "flyteexamples:development:container_task_demo.workflows.mmseqs_demo"
},
"level": "error",
"msg": "Error when trying to reconcile workflow. Error [failed at Node[n1]. RuntimeExecutionError: failed during plugin execution, caused by: failed to execute handle for plugin [container]: [] failed to create resource, caused by: admission webhook \"mutate.kyverno.svc-fail\" denied the request: failed to add image information to the policy rule context: invalid image {{.image.container_task_demo_default.fqn}}:{{.image.container_task_demo_default.version}}]. Error Type[*errors.NodeErrorWithCause]",
"ts": "2023-03-14T09:47:08Z"
}
I registered with the image, here are the logs:
Running pyflyte register from [...] with images ImageConfig(default_image=Image(name='default', fqn='<http://cr.flyte.org/flyteorg/flytekit|cr.flyte.org/flyteorg/flytekit>', tag='py3.9-1.4.1'), images=[Image(name='default', fqn='<http://cr.flyte.org/flyteorg/flytekit|cr.flyte.org/flyteorg/flytekit>', tag='py3.9-1.4.1'), Image(name='container_task_demo_default', fqn='location-docker.pkg.dev/[path to image]', tag='6747b4e2db0d5145e23a00044bdd547d4f276c01')]) and image destination folder /root on 1 package(s)
Registering against flyte.[domain]
Detected Root [...], using this to create deployable package...
Loading packages ['container_task_demo'] under source root [...]
Successfully serialized 1 flyte objects
[✔] Registration container_task_demo.workflows.[task_name] type TASK successful with version 6747b4e2db0d5145e23a00044bdd547d4f276c01
Successfully registered 1 entities
flyte_task
The UI reports the correct image and the task before it runs with that image without issue. I'm not sure what could be causing this.João Lobo Guerra Neto
03/14/2023, 12:09 PMpanic: [AUTH_CONTEXT_SETUP_FAILED] Error creating oidc provider w/ issuer [], caused by: Get "/.well-known/openid-configuration": unsupported protocol scheme ""
I have hidden my values for security but I am using azure ad for authentication
is there something wrong with my configuration?
server.yaml: |
server:
grpcPort: 8089
httpPort: 8088
security:
useAuth: true
allowCors: true
allowedHeaders:
- Content-Type
- flyte-authorization
allowedOrigins:
- '*'
secure: false
auth:
authorizedUris:
- <https://test.com>
- <http://flyteadmin:80>
- <http://flyteadmin.flyte.svc.cluster.local:80>
userAuth:
openId:
baseUrl: <https://login.microsoftonline.com/{tenent}/v2.0>
clientId: app-id
clientSecretLocation: /etc/secrets/client_secret
scopes:
- profile
- openid
- offline_access
appAuth:
thirdPartyConfig:
flyteClient:
clientId: app-id
redirectUri: https://{url}/callback
scopes:
- offline
- all
flyteadmin:
eventVersion: 2
metadataStoragePrefix:
- metadata
- admin
metricsScope: 'flyte:'
profilerPort: 10254
testing:
host: <http://flyteadmin:80>
Eli Bixby
03/14/2023, 1:31 PMnn.Module
with the pytorch plugin, but I want a downstream task to receive the filepath that the nn.Module
is saved to. Is there a way to do that?Michael Tinsley
03/14/2023, 2:07 PMNiels Bantilan
03/14/2023, 2:16 PMRyo M
03/14/2023, 2:23 PMSonja Ericsson
03/14/2023, 5:26 PMJustin Boutwell
03/14/2023, 7:40 PMdf = pd.read_sql_query(interpolated_query, connection)
becomes
df = pd.read_sql_query(sqlalchemy.text(interpolated_query), connection)
I can verify locally sqlalchemy 1.4.x works with either a text object or string, but 2.0.x only works with text.
I can submit that as an issue against flytekit, but I'm wondering if a) if there is a way to verify what version of the module the task is using and b) if there is a way to force using a specific sqlalchemy version.