Hi everyone. I started recieving an error message for all flows:

404 Client Error for <http+docker://localhost/v1.41/containers/create?name=elastic-salamander>: Not Found ("No such image: <http://26123096XXXX.dkr.ecr.us-east-1.amazonaws.com/cal_val_etl_flows:latest-165946XXXX%22|26123096XXXX.dkr.ecr.us-east-1.amazonaws.com/cal_val_etl_flows:latest-165946XXXX">)

I can go on AWS ECR, see the container, and see that the URI matches with the one from the error so it does exist…I have changed some settings recently regarding the python version and docker build, but cannot understand why i would get a container not found error edit: formatting

while running the deployemnt from ui in prefect 2.0.1 . athough the directory exists

Which syntax I can use to get current flow run's parameters value

Hello. In Prefect 1: Context: we have a flow of flows, and to manage dependencies, we have 2 solution. Either make sure the infra registers the flows in order, or to import and register the underlying flows in the flow-of-flows. What could go wrong if you do register a flow in the flow-of-flows like

from underlying_flows.flow_a import flow_a

flow_a.register(project...)

With Flow(...):
    ...

Because when we do that, prefect throws a warning

UserWarning: Attempting to call "flow.register" during execution of flow file will lead to unexpected results.

For launching an ECS instance via the

--cli-input-json

tag for cli, should there be an extra argument in the

prefect-agent-td.json

file called

agentRoleArn

? There are two for

executionRoleArn

and

taskRoleArn

but if the agent itself needs a Role in AWS should that be specified or can it be included in the other variables?

Hello! I have a 2.0 question about registering and using blocks, specifically infrastructure blocks.

Following these links for running prefect sample flow on cloud 2.0 : https://orion-docs.prefect.io/ui/cloud-getting-started/ + https://orion-docs.prefect.io/concepts/storage/ Executed this command:

prefect deployment build ./sample.py:samplefunc --name "ALS Deployment" --storage-block recommenderprefectserver

Error: Deployment.yaml is not created with following exception

Hi all! I could use some help here. I’m trying to query a DB to get a collection of inputs to process, and to dispatch each input to a sub-flow:

@task()
def get_inputs() -> List:
    # This task retrieves a list of inputs to process from a DB and returns it
    pass


with Flow(name='dispatcher') as dispatcher:

    inputs = get_inputs()

    for i in inputs:
        create_flow_run('worker', parameters={'input': i})

It doesn’t work as I need to provide either nouts or return a Tuple in order to iterate over my inputs, however I don’t know the size of it. What would be a correct approach here? Thanks!

Hi! I'm trying to specify result location per task in Orion but I can't find any documentation on the issue. Was the task result functionality removed in Orion?

Prefect Agent and and Orion both are up, yet the flow on cloud: 2.0 is scheduled only and paused in the late state

Hello, is there a way to render markdown written in deployment.yaml:description in the Prefect Orion Cloud UI?

Do we have docker-compose for prefect 2.0 ?

How can we logout of prefect cloud:2.0 and switch back to prefect UI? I am running Orion start command but queue is created on cloud

Hi all~ I'm using Prefect1.0. Is there any method that trigger to immeadiatly excute the flow, if the certain task is finished in the app we developed? NOT trigger from the task.

Version:             2.0.2

API version:         0.8.0

Python version:      3.9.13

I having problems with both the

read_flow_by_name

and

read_deployment_by_name

. Neither of these method is working in when i try to use them: Sample code:

from prefect.client import get_client

import asyncio

import json

async def main():

async with get_client() as client:

data = await client.read_flow_by_name(flow_name='test_flow')

loop = asyncio.get_event_loop()

loop.run_until_complete(main())

Error:

Traceback (most recent call last):

File

data = await client.read_flow_by_name(flow_name='test_flow')

/.venv/lib/python3.9/site-packages/prefect/client.py", line 508, in read_flow_by_name

return schemas.core.Deployment.parse_obj(response.json())

File "pydantic/main.py", line 521, in pydantic.main.BaseModel.parse_obj

File "pydantic/main.py", line 341, in pydantic.main.BaseModel.__init__

pydantic.error_wrappers.ValidationError: 2 validation errors for Deployment

flow_id

field required (type=value_error.missing)

manifest_path

field required (type=value_error.missing)

Hi all, I'm having a look at prefect-email, and wonder if there is a better way to securely store the password rather than having it hard coded into the Python scripts? https://github.com/PrefectHQ/prefect-email Thank you 🙂

Is anyone else on 2.0.2 yet? I'm getting an interesting error when I try to deploy using a remote storage block (seems to work with a local file system). Code: prefect deployment build orchestration/flows/test_cleansed.py:default -n test_cleansed -t dev --storage-block azure/azure-dev --infra docker-container -o test_cleansed-deployment.yaml Error: TypeError: put_directory() got an unexpected keyword argument 'ignore_file' on line 470 of cli/deployment.py Judging by the source code in Github, it seems like the overload of put_directory() for the Azure storage block specifically omits the ignore_file argument. Perhaps these two features were not tested together, unless I'm missing something. I'll give people an hour to say that I'm doing something wrong, otherwise I'll create an issue (or a PR, might be an easy fix).

Hi all, (working on prefect 2.0.2) I am running a deployment flow on scheduled interval. I have 2 agents listening on the same work-queue and grabbing this flow. One agent gets an error : prefect.exceptions.Abort: This run has already terminated. ---> The flow is considered "Crashed". Is it the expected behavior ? How is it possible to split the load on multiple agents for Scheduled deployments ? Cheers

I'm trying to find how to use kubernetes tasks on prefect 2, is that possible? (I mean same as in prefect 1)

getting server timeout when running the deployment from cloud ui 10:09:41.192 | DEBUG | prefect.agent - Checking for flow runs... 10:09:46.444 | DEBUG | prefect.agent - Checking for flow runs... 10:09:51.687 | DEBUG | prefect.agent - Checking for flow runs... 10:09:56.936 | DEBUG | prefect.agent - Checking for flow runs... 10🔟02.188 | DEBUG | prefect.agent - Checking for flow runs... 10🔟07.439 | DEBUG | prefect.agent - Checking for flow runs... 10🔟12.683 | DEBUG | prefect.agent - Checking for flow runs... 10🔟18.003 | DEBUG | prefect.agent - Checking for flow runs... 10🔟23.248 | DEBUG | prefect.agent - Checking for flow runs... 10🔟28.530 | DEBUG | prefect.agent - Checking for flow runs... 10🔟28.709 | INFO | prefect.agent - Submitting flow run '62df0689-3a3d-4bb0-bcaa-a16fb215df67' 10🔟29.536 | ERROR | prefect.agent - Flow runner failed to submit flow run '62df0689-3a3d-4bb0-bcaa-a16fb215df67' Traceback (most recent call last): File "/usr/local/lib/python3.8/site-packages/prefect/agent.py", line 169, in submit_run await self.task_group.start(submit_flow_run, flow_run, infrastructure) File "/usr/local/lib/python3.8/site-packages/anyio/_backends/_asyncio.py", line 701, in start return await future File "/usr/local/lib/python3.8/site-packages/prefect/infrastructure/submission.py", line 48, in submit_flow_run return await infrastructure.run(task_status=task_status) File "/usr/local/lib/python3.8/site-packages/prefect/infrastructure/kubernetes.py", line 201, in run job_name = await run_sync_in_worker_thread(self._create_job, manifest) File "/usr/local/lib/python3.8/site-packages/prefect/utilities/asyncutils.py", line 56, in run_sync_in_worker_thread return await anyio.to_thread.run_sync(call, cancellable=True) File "/usr/local/lib/python3.8/site-packages/anyio/to_thread.py", line 28, in run_sync return await get_asynclib().run_sync_in_worker_thread(func, *args, cancellable=cancellable, File "/usr/local/lib/python3.8/site-packages/anyio/_backends/_asyncio.py", line 818, in run_sync_in_worker_thread return await future File "/usr/local/lib/python3.8/site-packages/anyio/_backends/_asyncio.py", line 754, in run result = context.run(func, *args) File "/usr/local/lib/python3.8/site-packages/prefect/infrastructure/kubernetes.py", line 408, in _create_job job = batch_client.create_namespaced_job(self.namespace, job_manifest) File "/usr/local/lib/python3.8/site-packages/kubernetes/client/api/batch_v1_api.py", line 210, in create_namespaced_job return self.create_namespaced_job_with_http_info(namespace, body, **kwargs) # noqa: E501 File "/usr/local/lib/python3.8/site-packages/kubernetes/client/api/batch_v1_api.py", line 309, in create_namespaced_job_with_http_info return self.api_client.call_api( File "/usr/local/lib/python3.8/site-packages/kubernetes/client/api_client.py", line 348, in call_api return self.__call_api(resource_path, method, File "/usr/local/lib/python3.8/site-packages/kubernetes/client/api_client.py", line 180, in __call_api response_data = self.request( File "/usr/local/lib/python3.8/site-packages/kubernetes/client/api_client.py", line 391, in request return self.rest_client.POST(url, File "/usr/local/lib/python3.8/site-packages/kubernetes/client/rest.py", line 275, in POST return self.request("POST", url, File "/usr/local/lib/python3.8/site-packages/kubernetes/client/rest.py", line 234, in request raise ApiException(http_resp=r) kubernetes.client.exceptions.ApiException: (500) Reason: Internal Server Error HTTP response headers: HTTPHeaderDict({'Audit-Id': 'c94033e6-af19-414c-8c50-72811876a885', 'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'X-Kubernetes-Pf-Flowschema-Uid': '1133f237-04af-4269-a466-2f5eb69e6670', 'X-Kubernetes-Pf-Prioritylevel-Uid': 'e6f943c5-ae55-45d1-ab0e-cb0161b8bd0e', 'Date': 'Wed, 03 Aug 2022 10🔟29 GMT', 'Content-Length': '264'}) HTTP response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"The POST operation against Job.batch could not be completed at this time, please try again.","reason":"ServerTimeout","details":{"name":"POST","group":"batch","kind":"Job"},"code":500}

Hi people, Like ShellTask function in Prefect v1 (https://docs-v1.prefect.io/api/latest/tasks/shell.html#shelltask) , Is there anyway to call upon a bash script in Prefect 2.0 using any other function as I cant find any documentation for it. Any Suggestion?

Hi, How I make SSL connection while connecting to postgres db?

I know asyncpg has way to pass sslmode, ssl sertificate

Hi I’ve managed to get a POC for Prefect up and running in Heroku but issue I have now is that when I go to run the flow that run dbt, it doesn’t appear to be picking up the env var for the dbt target and is instead falling back on the dev one. I’m currently creating a task like so

dbt_shell_task = DbtShellTask(
    profiles_dir=str(DBT_PROFILES_DIR),
    environment=str(DBT_TARGET),
    overwrite_profiles=False,
    helper_script=f"cd {DBT_ROOT}",
    return_all=True,
    stream_output=True,
    state_handlers=[post_to_slack],
)

If I run dbt outside Prefect, i.e.

dbt build --target=$DBT_TARGET

it works as expected. Am I using the wrong variable for

target

?

Hi guys, has anyone done testing for mapped flow? I'm trying to write a test to verify if a task is available in the flow but I can't seem to access the tasks that are inside the mapped flow

Hi everyone, With prefect 2.0 : Is it possible to use prefect.inrastructure to run a docker on Azure outside the agent ? My VM where I install the agent have 1Go of RAM, but I want to set up a docker task (like FARGATE on AWS) with more ressources to execute the flow. Or should I go straight to kubernetes ? Someone have tried Kubernetes on Azure for this ?

Hi all, How can I get more descriptive names of tasks like "create_flow_run" & "wait_for_flow" ? Otherwise in prefect cloud it's hard to understand which child flow started or not ...

I am running flows on prefect 1.0 with an ECS Agent. The flow is successfully scheduled/submitted then gets stuck in that state. I looked on ECS and it looks like the container starts then immediately dies. There aren’t any associated logs that I can find. Any recommendations on how to debug this? EDIT - ended up being a 1.0 agent/2.0flow compatibility issue. For brevity the ECS container stop reason was

essential container in task exited

with no generated logs. The entrance command

["/bin/sh", "-c", "prefect execute flow-run"]

was failing because (I think) prefect 2.0 doesn’t have an

execute

command. I resolved this by pinning my prefect dependency to

pip install "prefect[aws, gitlab]==1.3.0"

.

Prefect : 2.0.2 I added the "version" parameter to my flow, but it doesn't show up in the UI. When I go to retrieve the flow model version is not included either.

from prefect import flow, get_run_logger

@flow(name="test", version="1.0beta")
def main():
    logger = get_run_logger()
    <http://logger.info|logger.info>(f"Hello World")

if __name__ == "__main__":
    main()

Flow model details:

id=UUID('120dea46-79e8-4f42-99f0-7e300a2b3cb9') name='test' tags=[]

This is big blocker for me as I want to the

create_flow_run

method, but it errors out after you give it a flow model without a version in it. Any suggestion on what i am doing wrong here?