jack
05/24/2023, 5:57 PMDarren Liu
05/24/2023, 8:20 PM@flow(name="test", flow_run_name="dev > test")
def test():
return variables.get("test")
Brayyan Yanes
05/24/2023, 8:24 PMNicholas Torba
05/25/2023, 1:16 PMNicholas Torba
05/26/2023, 3:14 PMJane Jeong
05/26/2023, 8:50 PMprefect deployment
are failing with:
pydantic.error_wrappers.ValidationError: 1 validation error for CloudRunJob
command
value is not a valid list (type=type_error.list)
The value is now null - I don't think "command" should still be checked at this pointJezreel Zamora
05/29/2023, 1:17 AMZombie Killer
process works in V1?
From what i understand, it should mark the flows as failed if the flows failed to send heartbeats on a X number of times.
I’m testing this behavior with a flow that is running in ECS by simulating Out of Memory. I can see that the ECS Task failed and stopped running in AWS Console but the flow run in Prefect Cloud remains in Running state. This cause our schedule flows to not run until we manually set the status to Failed for the stuck flow.
Is there anything I’m missing or something we need to setup to make this work properly?Wei Hong Ho
05/29/2023, 10:47 AMps ax
i realized, there's a lot of prefect.engine
not sure whether they are zombie processes or not. any tips on how to prevent this in the future?Zhang David
05/29/2023, 8:56 PM"The notification block was invalid: KeyError(\"No class found for dispatch key 'slack-incoming-webhook' in registry for type 'Block'.\")"
Has anyone run into this as well ?
Below is the full log:
{
"id": "77b5b58d-e9fa-4fff-bb5b-5c2157314dba",
"account": "94a1563f-c82c-4049-854c-df6f4547b850",
"event": "prefect-cloud.automation.action.failed",
"occurred": "2023-05-29T21:52:20.401Z",
"payload": {
"reason": "The notification block was invalid: KeyError(\"No class found for dispatch key 'slack-incoming-webhook' in registry for type 'Block'.\")",
"invocation": "8ff1536d-55b2-4170-9af4-10d6dd13243f",
"action_type": "send-notification",
"action_index": 0
},
"received": "2023-05-29T21:52:20.401Z",
"related": [],
"resource": {
"prefect.resource.id": "prefect-cloud.automation.fcac6a63-01bb-4ade-94f0-e27664583542",
"prefect-cloud.posture": "Reactive",
"prefect.resource.name": "prod-wf-state"
},
"workspace": "1e3683bb-8412-4b7f-a2a8-c858d613af44"
}
Matthew Scanlon
05/30/2023, 1:18 PMNicholas Torba
05/30/2023, 3:58 PMYing Sheng Lam
06/01/2023, 2:41 AMMatt Alhonte
06/05/2023, 11:17 PMjohn
06/06/2023, 12:52 PMNicholas Torba
06/07/2023, 4:54 PMJoseph Thickpenny Ryan
06/08/2023, 10:43 AMAhmed Maged
06/11/2023, 4:11 PMBrett
06/12/2023, 9:36 PMBrett
06/12/2023, 9:36 PMprefect 2.10.13
it appears that there is some error with using metadata.generateName
where it is only generating the "-value". Example response in the snippet above.
Forcing it back to prefect 2.10.9
allows it to work properly.
Is this a known bug?Syed Areeb Amjed
06/14/2023, 8:01 AMGosia
06/14/2023, 8:11 AMalex
06/14/2023, 6:02 PMRobert Esteves
06/15/2023, 6:43 PMMitch
06/15/2023, 9:13 PMImporting flow code from 'XXXX.py:yy'
Flow could not be retrieved from deployment.
Sergey Zmeyev
06/15/2023, 9:44 PMClaire Scott
06/16/2023, 6:33 AMKees
06/19/2023, 11:59 AMBen Muller
06/20/2023, 1:02 AMdeployments ( old projects )
thingy, we store our docker images in ecr to run on ecs (AWS) and use git storage in github.
I noticed on prefect-aws that the steps required for the build of the prefect.yaml
doesnt have anything yet for a build_docker_image
from ecs.
Am I missing something or can I use a vanilla - prefect_docker.deployments.steps.build_docker_image:
and reference a ecr image and it will handle it?Jey Farmer
06/20/2023, 3:06 PMapiUrl: <http://127.0.0.1:4200/api>
- this is default in the helm chart and docs don’t mention changing this
Error I receive when looking at the logs of the worker
Worker 'KubernetesWorker 3f629027-a4e8-4b08-b856-2e5c62e38933' started!
15:01:39.075 | DEBUG | prefect.worker.kubernetes.kubernetesworker 3f629027-a4e8-4b08-b856-2e5c62e38933 - Exiting worker context...
15:01:39.075 | DEBUG | prefect.worker.kubernetes.kubernetesworker 3f629027-a4e8-4b08-b856-2e5c62e38933 - Tearing down worker...
15:01:39.076 | DEBUG | MainThread | prefect._internal.concurrency - <AsyncCancelScope, name='start' COMPLETED, runtime=2.02> exited
15:01:39.076 | DEBUG | MainThread | prefect._internal.concurrency - Encountered exception in async call start(worker_name=None, work_pool_name='jey-test-custom-k8s-work-pool', work_queues=[], worker_type='kuber...)
Traceback (most recent call last):
..... shortened logs.....
prefect.exceptions.PrefectHTTPStatusError: Client error '403 Forbidden' for url '<https://api.prefect.cloud/api/accounts/><REMOVED_ACCOUNT_ID>/workspaces/<REMOVED_WORKSPACE_ID>/work_pools/jey-test-custom-k8s-work-pool'
Response: {'detail': 'Unauthorized'}
For more information check: <https://httpstatuses.com/403>
Mr Eli W Jones
06/20/2023, 11:36 PM