Hey guys, I’m running a flow with a DaskTaskRunner that spawns a task that takes around 20seconds and apparently it’s running sequentially?! My machine has 16 threads and I see in the UI each task only being run after another one finishes. Any inputs?

23:04:54.057 | INFO    | prefect.engine - Created flow run 'optimal-snail' for flow 'test1'
23:04:54.057 | INFO    | prefect.task_runner.dask - Creating a new Dask cluster with `distributed.deploy.local.LocalCluster`
23:04:55.980 | INFO    | prefect.task_runner.dask - The Dask dashboard is available at <http://127.0.0.1:8787/status>
23:05:00.371 | INFO    | Flow run 'optimal-snail' - Created task run 'Execute values of the query-8165e3c8-0' for task 'Execute values of the query'
23:05:00.372 | INFO    | Flow run 'optimal-snail' - Executing 'Execute values of the query-8165e3c8-0' immediately...
23:05:24.612 | INFO    | Task run 'Execute values of the query-8165e3c8-0' - Finished in state Completed()
23:05:26.370 | INFO    | Flow run 'optimal-snail' - Created task run 'Execute values of the query-8165e3c8-1' for task 'Execute values of the query'
23:05:26.370 | INFO    | Flow run 'optimal-snail' - Executing 'Execute values of the query-8165e3c8-1' immediately...
23:05:42.533 | INFO    | Task run 'Execute values of the query-8165e3c8-1' - Finished in state Completed()
23:05:44.295 | INFO    | Flow run 'optimal-snail' - Created task run 'Execute values of the query-8165e3c8-2' for task 'Execute values of the query'
23:05:44.296 | INFO    | Flow run 'optimal-snail' - Executing 'Execute values of the query-8165e3c8-2' immediately...
23:06:09.538 | INFO    | Task run 'Execute values of the query-8165e3c8-2' - Finished in state Completed()

As you see in these logs it’s not really spawning more tasks. I was under the impression that the call to a function with the

@task

decorator would be non-blocking if made within a flow

@flow

which uses DaskTaskRunner

Hi everyone! Just getting started with orchestrating DBT (CLI) flows using Prefect. Having a weird error where the "trigger_dbt_cli_command" is telling me I'm specifying an invalid project directory because I'm missing a dbt_project.yml file (I'm not). Any idea what's going on? Sample code below:

from prefect import flow
from prefect_dbt.cli.commands import trigger_dbt_cli_command

@flow
def run_dbt() -> str:
    result = trigger_dbt_cli_command("dbt run", project_dir='C:\\Users\\36350admin\\arrow_dbt-1')
    return result

run_dbt()

It even tells me it's running this dbt command, and when I run that by itself in the same working directory, it works as expected!

22:29:08.084 | INFO    | Task run 'trigger_dbt_cli_command-321ca940-0' - Running dbt command: dbt run --profiles-dir C:\Users\36350admin\.dbt --project-dir C:\Users\36350admin\arrow_dbt-1

Hi, it seems like DockerContainer block does not support ECR image yet? My agent is failing to authenticate with ECR. I'm basically doing something like this https://github.com/anna-geller/prefect-docker-deployment/blob/main/blocks/dockerhub_block.py but with ecr

Hi! I have a flow which only calls two subflows (and nothing else). The subflows show up as completed but the main flow is stuck at running... I've had related problems that seemed to be because of memory issues, but my subflows don't return anything so I don't see how they can complete without the main flow completing

Hello. Is it possible to stream task runner initialisation logs to the Cloud UI logs? I am using DaskTaskRunner and user can't see logs about cluster creation and dashboard url.

Hey there, I have a question about the "right way" to run prefect agents. I have the following setup: local environment (where I quickly test flows and tasks), github repo with CI which automatically redeploys new code, remote machine (which clones code from github, runs prefect deployment build and then starts prefect agent). And finally I am using Prefect Cloud for all remaining things. I am wondering that would happen If I redeploy my codebase (adding new flow and deployment for instance) and at the same time I would have some flows running. Would these flows be able to resume at the "right point"? And in general, what is the best practice for redeploying the codebase with prefect if I use only one machine? Thanks a lot! P.S. I used Airflow heavily before Prefect and now I am migrating some jobs to Prefect.

the prefect 2.x documentation regarding infrastructure such as for cloudrun and kubernetes job is way too scarce.

Hello, I have a problem when migrating to prefect cloud 2.0. i have a virtual machine and after running pip install -U prefect, pip doesn't work anymore, any lib I want to install doesn't work and the following message is displayed: AttributeError: module 'lib' has no attribute 'X509_V_FLAG_CB_ISSUER_CHECK' I tried to uninstall prefect and install again with the updated version and still the same error.

Hello! I use prefect 1 for flows that write data in a NFS, with Kubernetes and Docker runs, and docker storage for each flow. It seems that all flows run as root in their container as all files are owned by root when generated by the flow. I need to change the ownership of files generated, is it possible to change the user that flows execute as ? Thanks 🙂

Hi! does anyone know if it is possible to have multiple users and workspaces using a self-hosted prefect orion server? and if so, how could i install this server? thaaanks

When I host the ui locally (Orion) I don't get the opportunity to create new blocks - is this integration only supported in cloud version?

I have a question and an idea with regards to caching: 1. How can I forceful clean up cache without an expiry time? 2. If I have a task dependency: A->B->C and both A and B are cached, will there be any result transfered from A to B? In theory I would be able to only get cached returned values from B and run C. 3. It would be nice to have configurable cache locations by means of env var for each flow run. Currently when using input hash and with multiple users run the same task, prefect will try to fetch the cache from the first users, which raises permission issues depending. As a workaround I can get add the user to the hash function, but that feels complicated. Any thoughts?

Hi All, Am trying to use the prefect-email collection to send a notification via office 365 and getting the below error. Would anyone know how to fix this issue?

File "/usr/local/lib/python3.9/site-packages/prefect_email/credentials.py", line 138, in get_server
    server = SMTP_SSL(smtp_server, smtp_port, context=context)
  File "/usr/lib64/python3.9/smtplib.py", line 1050, in __init__
    SMTP.__init__(self, host, port, local_hostname, timeout,
  File "/usr/lib64/python3.9/smtplib.py", line 255, in __init__
    (code, msg) = self.connect(host, port)
  File "/usr/lib64/python3.9/smtplib.py", line 341, in connect
    self.sock = self._get_socket(host, port, self.timeout)
  File "/usr/lib64/python3.9/smtplib.py", line 1057, in _get_socket
    new_socket = self.context.wrap_socket(new_socket,
  File "/usr/lib64/python3.9/ssl.py", line 501, in wrap_socket
    return self.sslsocket_class._create(
  File "/usr/lib64/python3.9/ssl.py", line 1041, in _create
    self.do_handshake()
  File "/usr/lib64/python3.9/ssl.py", line 1310, in do_handshake
    self._sslobj.do_handshake()
ssl.SSLError: [SSL: WRONG_VERSION_NUMBER] wrong version number (_ssl.c:1129)

This message was deleted.

I'm seeing some odd behavior in the Cloud UI that is not happening locally. I have

2.4.0

installed locally. For example, if I create the deployments

Foo(customer=1)

,

Foo(customer=2)

and

Foo(customer=3

all under the flow name

Foo

, I can go to my local UI, clicked on "Flows" and then "Foo", and I see those deployments. But in the Prefect Cloud 2.0 UI, if I go to "Flows" and click on "Foo", no deployments appear! They do appear if I click on deployments. Is this the expected behavior of the UI? (i.e. is there some criteria for a flow deployment to appear on the flow page?)

Question regarding upgrading Prefect 1.0 -> 2.0 Container Execution: All of my Prefect 1.0 flows run Docker containers, they aren't flows in Docker containers so in the course of upgrading to Prefect 2.0, the Docker Infrastructure block seems counterproductive. Do I need to rewrite all of the Docker Client tasks from Prefect 1.0 to maintain their functionality?

Hi all! I'm currently developing a flow with async and sync tasks. Tasks A and B run successfully but the execution freezes and I even can't see the log for task c, the last log is

Task run 'b' - Completed()

. If I force task c to be async runs without a problem. Is that a current bug? Using Prefect 2.3.1

@task
async def a():
  # do async

@task
async def b():
  # do async

@task
def c():
  # do sync

@flow
async def main():
  a = await a()
  b = await b(wait_for=[a])
  c = c(wait_for=[b])

asyncio.run(main())

Thanks!

is it possible to connect and deploy to prefect through azure when hosted locally like it is with prefect cloud?

Hi, Is this a known issue that there are prefect jobs running, but the "runs in progress" is showing 0? We are running into concurrency limits because some tasks are stuck running for ever, but there is no easy way to find those runs, except digging into each flow one by one. Is there a way I can stop all running flows (even though the dashboard is showing 0 running flows)?

Prefect appears to be trying to launch my Dask cluster 3 times when I run my flow:

2022-09-29 11:50:53 - coiled - INFO - Using existing cluster: 'ghg-demo (id: 83299)'
2022-09-29 11:50:53 - coiled - INFO - Creating Cluster (name: ghg-demo, <https://cloud.coiled.io/abcd1234/clusters/83299/details> ). This might take a few minutes...
2022-09-29 11:50:54 - coiled - INFO - Scheduler: ready                               Workers: 3 ready (of 3)
2022-09-29 11:50:54 - coiled - INFO - Scheduler: ready                               Workers: 3 ready (of 3)
2022-09-29 11:50:59 - coiled - INFO - Using existing cluster: 'ghg-demo (id: 83299)'
2022-09-29 11:50:59 - coiled - INFO - Creating Cluster (name: ghg-demo, <https://cloud.coiled.io/abcd1234/clusters/83299/details> ). This might take a few minutes...
2022-09-29 11:50:59 - coiled - INFO - Scheduler: ready                               Workers: 3 ready (of 3)
2022-09-29 11:50:59 - coiled - INFO - Scheduler: ready                               Workers: 3 ready (of 3)
2022-09-29 11:51:05 - coiled - INFO - Using existing cluster: 'ghg-demo (id: 83299)'
2022-09-29 11:51:05 - coiled - INFO - Creating Cluster (name: ghg-demo, <https://cloud.coiled.io/abcd1234/clusters/83299/details> ). This might take a few minutes...
2022-09-29 11:51:06 - coiled - INFO - Scheduler: ready                               Workers: 3 ready (of 3)
2022-09-29 11:51:06 - coiled - INFO - Scheduler: ready                               Workers: 3 ready (of 3)

The simple flow is decorated as follows:

@flow(
    description = 'Calculates revenues for wells associated with a specific forecast',
    task_runner = CoiledTaskRunner(config_name=WELL_REVENUE_CONFIG)
)
def forecast_well_revenues(request: ForecastJobRequest) -> None:
    # invoke tasks here

Can someone explain why this is happening?

Prefect 1.0 -> 2.0 Question: Is there a reason that

Deployment.build_from_flow

requires a

.prefectignore

file? Currently have all of those flows in a pip installable python module, would be nice to be able to override that rather than need to skip upload in the build, and then separate calls to

apply()

and

upload_to_storage(...)

.

Hi There I'm having undeletable flow run https://app.prefect.cloud/account/a5aa4a76-f2a5-4e07-bb53-f0e7ff684f5b/workspace/f480[…]6-85a65419eb76/flow-run/82337252-1919-4165-b79a-717f313c4b24 is there anything to do? server is always replying with 500

Hello, just this afternoon I’ve started getting a 500 when trying to apply a deployment to my workspace (same deployment worked fine earlier) today)/ I can see there’s been quite a few changes around deployments causing issues with the 2.4.x releases, but is there any way to tell why it’s rejecting it? Output is just a generic 500 error.

i'm also getting 500 internal service errors when im trying to apply deployments

I am trying to run in process on a prefect agent on AKS loading data from azure storage. I am getting this log from the agent pod. I have deployed the pod from the prefect helm chart. I have set the env variable EXTRA_PIP_PACKAGES=adlfs on the pod. Is this error familiar? It clearly has something to do with storage. I wondered if the adlfs package was not being loaded.

2022-09-29T21:22:51.649459194Z 21:22:51.649 | INFO    | prefect.agent - Completed submission of flow run '78a45bb6-5ee3-4d6b-9a34-bf6ca56e496c'
2022-09-29T21:30:52.133263521Z 21:30:52.133 | INFO    | prefect.agent - Submitting flow run 'c716e857-eba0-432a-8561-3f622cff080a'
2022-09-29T21:30:52.859579518Z 21:30:52.859 | INFO    | prefect.infrastructure.process - Opening process 'scrupulous-collie'...
2022-09-29T21:30:52.860369014Z 21:30:52.859 | ERROR   | prefect.agent - Failed to submit flow run 'c716e857-eba0-432a-8561-3f622cff080a' to infrastructure.
2022-09-29T21:30:52.860389714Z Traceback (most recent call last):
2022-09-29T21:30:52.860399114Z   File "/usr/local/lib/python3.10/site-packages/prefect/agent.py", line 233, in _submit_run_and_capture_errors
2022-09-29T21:30:52.860407714Z     result = await infrastructure.run(task_status=task_status)
2022-09-29T21:30:52.860461413Z   File "/usr/local/lib/python3.10/site-packages/prefect/infrastructure/process.py", line 71, in run
2022-09-29T21:30:52.860471313Z     with tempfile.TemporaryDirectory(suffix="prefect") as tmp_dir:
2022-09-29T21:30:52.860480013Z   File "/usr/local/lib/python3.10/tempfile.py", line 819, in __init__
2022-09-29T21:30:52.860488513Z     self.name = mkdtemp(suffix, prefix, dir)
2022-09-29T21:30:52.860497213Z   File "/usr/local/lib/python3.10/tempfile.py", line 357, in mkdtemp
2022-09-29T21:30:52.860526313Z     prefix, suffix, dir, output_type = _sanitize_params(prefix, suffix, dir)
2022-09-29T21:30:52.860534613Z   File "/usr/local/lib/python3.10/tempfile.py", line 126, in _sanitize_params
2022-09-29T21:30:52.860543013Z     dir = gettempdir()
2022-09-29T21:30:52.860551213Z   File "/usr/local/lib/python3.10/tempfile.py", line 299, in gettempdir
2022-09-29T21:30:52.860558913Z     return _os.fsdecode(_gettempdir())
2022-09-29T21:30:52.860567613Z   File "/usr/local/lib/python3.10/tempfile.py", line 292, in _gettempdir
2022-09-29T21:30:52.860575813Z     tempdir = _get_default_tempdir()
2022-09-29T21:30:52.860584713Z   File "/usr/local/lib/python3.10/tempfile.py", line 223, in _get_default_tempdir
2022-09-29T21:30:52.860615012Z     raise FileNotFoundError(_errno.ENOENT,
2022-09-29T21:30:52.860624512Z FileNotFoundError: [Errno 2] No usable temporary directory found in ['/tmp', '/var/tmp', '/usr/tmp', '/opt/prefect']
2022-09-29T21:30:52.861818706Z 21:30:52.861 | INFO    | prefect.agent - Completed submission of flow run 'c716e857-eba0-432a-8561-3f622cff080a'

And now I have the error telling me to install adlfs even though it is in the EXTRA_PIP_PACKAGES env variable.

Traceback (most recent call last):
  File "/root/.Envs/healthgraph/lib/python3.8/site-packages/sqlalchemy/dialects/postgresql/asyncpg.py", line 442, in _prepare_and_execute
    self._rows = await prepared_stmt.fetch(*parameters)
  File "/root/.Envs/healthgraph/lib/python3.8/site-packages/asyncpg/prepared_stmt.py", line 176, in fetch
    data = await self.__bind_execute(args, 0, timeout)
  File "/root/.Envs/healthgraph/lib/python3.8/site-packages/asyncpg/prepared_stmt.py", line 241, in __bind_execute
    data, status, _ = await self.__do_execute(
  File "/root/.Envs/healthgraph/lib/python3.8/site-packages/asyncpg/prepared_stmt.py", line 230, in __do_execute
    return await executor(protocol)
  File "asyncpg/protocol/protocol.pyx", line 201, in bind_execute
asyncpg.exceptions.ActiveSQLTransactionError: ALTER TYPE ... ADD cannot run inside a transaction block

Coming across this error while trying to run a prefect agent and orion. Has anyone come across this before?

Hello, Is there backward compatibility for deployments ? Let's consider the following situations : 1 - Build deployment with prefect 2.0 => Run it with agent prefect 2.4 2 - Build deployment with prefect 2.4 => Run it with agent prefect 2.0 Can we do either of those? Or should we always build and run with the same version ? Because if if it's the latter, it will be really hard to upgrade to a different version in the future

Prefect helm chart results in following read_only error in the docker container running the prefect server Even when tweaking the config settings to run as root user. Is there any solution to this issue by tweaking the values.yaml? Edit: I've tried every possible combinations of # -- set orion containers' security context runAsNonRoot runAsNonRoot: true # -- set orion containers' security context readOnlyRootFilesystem readOnlyRootFilesystem: true # -- set orion containers' security context allowPrivilegeEscalation allowPrivilegeEscalation: false In both the pod and container security context It happens when i set the password for the postgressql subchart ## This is the password for

username

and will be set within the secret at the key

{fullnameOverride}-postgresql-password

. ## This argument is only relevant when using the Postgres database included in the chart. ## For an external postgres connection, you must create and use

existingSecret

instead of

postgresqlPassword

. # -- password for the custom user to create. Ignored if

auth.existingSecret

with key

password

is provided password: password

Hi everyone. We have not migrated to 2.0 because we use results in most of our flows and this feature is not available in 2.0. I understand results (and the ability to restart flows runs) is being worked on. 1) what's the target release date? 2) is there a current workaround (on local infrastructure and ECS), even if restarting is not currently possible? Thanks!