Hi All, Has anyone been able to install prefect on centos7 box, I am trying to install prefect on centos7 box, but its failing saying that it needs sqlite3, I have installed latest version available for sqlite on the same centos7 box, but it doesn’t like it, if anyone have experienced such an issue before, please comments your workarounds or solutions

Hello! I'm trying to create a flow of flows in which some child flows depend on others. When trying to make 2 of them run sequentially using the following code snippet,

wait_for_flow_run

fails by throwing

TypeError: Object of type FlowRunView is not JSON serializable

. Am I passing the wrong object type as input?

from prefect.tasks.prefect import create_flow_run, wait_for_flow_run

with Flow("run-pipeline") as flow:
    flow_a_id = create_flow_run(flow_name=flow_a.name, ...[SOME INPUT PARAMS])
    flow_a_wait = wait_for_flow_run(flow_a_id)

(I'm using prefect 1.0.0)

hi guys, when i hit run on a prefect ui on the cloud, its creating a separate run rather than just restarting the run i had just started. • is there a way to run it just once? • Another thing is, if i run a deployment file with many deployments, like 30, its kind of painful to manually go to the UI and hit run on all of them. there must be some ability in the deployment spec to ensure a file thats not on a schedule gets run immediately upon deployment. • i want the ability to constantly check if a task is running and if its not, to initiate a run. a signal or whatever. • ability to email my team and I in case something crashes on the prefect side that was not picked up on the linux side

Hey all - Is there a way to make archived version of the flow active again? I have a flow that runs on a K8s agent, the image is stored in a container registry. I push new version to production and find a bug - I delete this new version. How do I now run the previous version of the flow, w/o creating a new Docker image?

Hello, I’m experiencing another issue during the deployment of the prefect helm chart.

Error from server (BadRequest): container “graphql” in pod “prefect-poc-graphql-76462537d4-4v7c6” is waiting to start: PodInitializing

All other pods seems to be deployed and running well. Anyone knows why this is happening? Also, my UI is not showing up as well, probably due to this issue.

@Marvin How do I run Prefect within a Docker container that is running FastAPI? I have a post and get. How do I deploy this with prefect locally? Should I have a python file that is pointing to the docker image and have flows in it, and deploy the said Docker file? Please give detailed examples of implementation if possible.

@Marvin Hello, i am deploying a local hoster prefect server and right know im having a problem trying to access the flows tab. The request isnt getting a response. I dunno if it may be a problem but i have changed the api and ui urls due to a kubectl ingress.

@Marvin how can we get the name of the current workspace from the python sdk?

@Marvin: I have a prefect worker and work pool in my own windows server. When I run a flow using this work-pool, I am running into the following error

The flow run will not be marked as failed, but an issue may have occurred.

    | Traceback (most recent call last):
    |   File "lib\site-packages\prefect\utilities\processutils.py", line 314, in stream_text
    |     await sink.write(item)
    |   File "lib\site-packages\anyio\_core\_fileio.py", line 109, in write
    |     return await to_thread.run_sync(self._fp.write, b)
    |   File "\lib\site-packages\anyio\to_thread.py", line 56, in run_sync
    |     return await get_async_backend().run_sync_in_worker_thread(
    |   File "\lib\site-packages\anyio\_backends\_asyncio.py", line 2177, in run_sync_in_worker_thread
    |     return await future
    |   File "lib\site-packages\anyio\_backends\_asyncio.py", line 859, in run
    |     result = context.run(func, *args)
    | OSError: [Errno 22] Invalid argument

@Marvin Is there any way to raise the Failed state while chaining the tasks by

wait_for

with

allow_failure

in Prefect 3.0? This code returns failed state in Prefect 2.0, but it returns Completed state in Prefect 3.0

from os import truncate
from prefect import allow_failure, flow, task
from prefect.states import Failed

@task
def my_prior_task():
    raise Exception('Intended Failed')


@task
def my_final_task():
    return truncate


@flow
def my_intended_failed_flow():
    my_prior_future = my_prior_task.submit()
    my_final_task.submit(wait_for=allow_failure([my_prior_future])).wait()
    return True


if __name__ == '__main__':
    my_intended_failed_flow()