Hi, is ist just me that Prefect has been extremely slow at the moment?

is there anyway to add

PREFECT_API_KEY

to self hosted prefect? I already have

PREFECT_API_KEY

configured in my docker compose but my local env is able to successfully able to execute flows on my self hosted prefect WITHOUT providing API key in any way.

@Marvin I'm still struggling with the return value of the wait() method of tasks. I always get None. Can you tell me what is wrong with the following minimal example:

import time
from prefect import flow, task, get_run_logger

@task
def wait_task(t):
    time.sleep(t)
    return_value = f'Waited for {t} seconds'
    get_run_logger().info(f'Now returning the following sentence: {return_value}')
    return return_value

@flow
def minimal_wait():
    logger = get_run_logger()
    status = wait_task.submit(5).wait(10)
    <http://logger.info|logger.info>(f'Status when waiting 5 s with time limit 10 s: {status}')
    status = wait_task.submit(15).wait(10)
    <http://logger.info|logger.info>(f'Status when waiting 15 s with time limit 10 s: {status}')


minimal_wait()

I also get the following Warning: A future was garbage collected before it resolved. Please call

.wait()

or

.result()

on futures to ensure they resolve. See https://docs.prefect.io/latest/develop/task-runners for more details.

Hi there! Back again- I've been building a fun little data ecosystem with prefect as our primary gardener. We're approaching a tipping point of turning some of these tools into user-facing products- The biggest bugbear though is that the prefect workers I run on our machines will occasionally (although reliably) crash once every couple of weeks, requiring a manual reboot. I'm only running them manually in tmux windows, as opposed to as systemd services- just while I've been in dev phase- but I wanted to get some insight into what might be going on here. I'll copy the error in the thread:

@Marvin I'm seeing a strange issue when using threading with python. A flow runs successfully for a couple of minutes and then gets errors like.

asyncio - Exception in callback SubprocessStreamProtocol.pipe_data_received(1, b'accepted: 0...pted: 1 (1)\n')
handle: <Handle SubprocessStreamProtocol.pipe_data_received(1, b'accepted: 0...pted: 1 (1)\n')>
Traceback (most recent call last):
  File "/usr/lib/python3.11/asyncio/events.py", line 84, in _run
    self._context.run(self._callback, *self._args)
  File "/usr/lib/python3.11/asyncio/subprocess.py", line 72, in pipe_data_received
    reader.feed_data(data)
  File "/usr/lib/python3.11/asyncio/streams.py", line 498, in feed_data
    assert not self._eof, 'feed_data after feed_eof'
           ^^^^^^^^^^^^^
AssertionError: feed_data after feed_eof

what is going wrong?

hey there, I'm trying to migrate a deployment that's in an S3 block to following the master branch of a GitLab repo. I have the

prefect.yaml

in place and and when I run

prefect deploy

I get the interactive menu in the terminal to choose from and when I do I get an error saying

prefect: error: unrecognized arguments: deploy

. I have

prefect=2.19.4

. Any ideas at what could be going on?

@Marvin I'm getting this error using a prefect cloud push work pool, it was working yesterday but hasn't worked for any flows today. I either get this error or they get stuck in the awaiting retry/late state What could be causing this?

Flow run could not be submitted to infrastructure: Google Cloud Run Service Agent <mailto:service-850000352187@serverless-robot-prod.iam.gserviceaccount.com|service-850000352187@serverless-robot-prod.iam.gserviceaccount.com> must have permission to read the image, us-east1-docker.pkg.dev/prefect-org-github-actions/dockerhub-mirror/prefecthq/prefect:2-python3.9. Ensure that the provided container image URL is correct and that the above account has permission to access the image. If you just enabled the Cloud Run API, the permissions might take a few minutes to propagate. Note that the image is from project [prefect-org-github-actions], which is not the same as this project [prefect-prd-mex-cloudrun-8]. Permission must be granted to the Google Cloud Run Service Agent <mailto:service-850000352187@serverless-robot-prod.iam.gserviceaccount.com|service-850000352187@serverless-robot-prod.iam.gserviceaccount.com> from this project.

@Marvin Do tasks within a flow run on multiple open workers by default? Can I see via the dashboard which docker worker they ran on?

@Marvin What is the best way to add kerberos authentication to an image being used by a prefect worker to run a job?

Hi All, I keep getting the below Timeout error while fetching data using graphql in a python code for Prefect 1.0 prefect.exceptions.ClientError: [{'path': ['flow_run'], 'message': 'Operation timed out', 'extensions': {'code': 'API_ERROR'}}] Is there any solution to avoid this?