Hi, I'm new to Prefect and installed a local server. Last week everything seemed to work and I started to write my first flows. They were executed as expected, also the UI worked great. However today morning, I tried to continue working on my flows, but for some reason the UI was frozen and I just restarted the containers through docker-compose (down and up again). After that I experienced a curious / weird output in the Postgres logfile (I will explain below). Even the UI was working fine again, the logfile of Postgres was quite confusing. So I thought, that something has messed up with my agent or other communication issues between Prefect server and the database. I decided to make a new clean setup in a new clean virtual environment. I also setup a path to a new database, and deleted the .prefect folder in the home directory. But even with the clean setup the weird behavior of Postgres started right away: ==> More details in thread

Hello, I’m new to Prefect and I need some help getting started. I’m currently struggling with two issues: 1. I’m setting up Prefect server on EKS using Helm. After

helm upgrade

ran successfully, I get commands such as

1 Run the following command to get the UI URL:

  UI_HOST=$( \
    kubectl get svc \
    --namespace prefect \
    --template "{{ range (index .status.loadBalancer.ingress 0) }}{{.}}{{ end }}" \
    prefect-server-ui \
  ) \
  && echo "UI available at: http://$UI_HOST:8080"...

when I run the above command, I get an error saying

error: error executing template "{{ range (index .status.loadBalancer.ingress 0) }}{{.}}{{ end }}": template: output:1:10: executing "output" at <index .status.loadBalancer.ingress 0>: error calling index: index of untyped nil

Then I have to run

kubectl port-forward <name of the service> <port>:<port>

to get ui and apollo servers running. Is there a way to run this without port forwarding? 2. I’m trying to run a hello world example flow on prefect server on my EKS cluster. I tried to trigger it from my command line by creating a project and running

prefect register --project test-project -p hello/

. The registering seem to run successfully but I don’t see the flow on the ui. I’m also not able to manually create flow project using ui. Am I interacting with two different prefect engine here? How do I register prefect flow so that it is running on my prefect server on EKS cluster?

@Marvin When I try to start my local prefect server, it fails with the following error: alembic.util.exc.CommandError: Can't locate revision identified by 'c63a0a6dc787' And that is not a revision from my project. How can I fix it?

Hi all, prefect 2.0. I am getting the following error while building a deployment.

ValueError: Unable to find block document named mini1 for block type RemoteFileSystem

Hi! I am working on setting up a simple CI/CD process that registers new flows each time a push is made to main. My folder structure is inspired by the gitlab data team so at the root of my project i have a folder orchestrate. Within that folder i have a folder tasks - within this there are subdirectories that contain custom modules that store tasks we use throughout our flows. While registering flows via the GitHub action, the Prefect CI is complaining about not being able to find a module in the tasks folder. When I run this locally, I do not get any issues. I am pretty sure it is related to my PYTHONPATH setup within the GitHub flow but I have not had any luck troubleshooting. Has anyone out there run into a similar issue?

Hi all! I was wondering how we can change the UI port from 8080 to something else. I have changed the

PREFECT__SERVER__UI__PORT

and

PREFECT__SERVER__UI__HOST_PORT

to try and follow the config.toml, but the UI service is still launching and saying “👾👾👾 UI running at localhost:8080 👾👾👾” and I dont know what else to change in the UI service 😞 As a follow up, what is the difference between the UI port and the UI host port? EDIT: I see echo

UI running at localhost:8080

is hardcoded in ./start_server.sh in the UI service, is this meant to be the case?

Hi everyone! I’m working with a local Prefect server and wanted to get some insights on deployment methods. I’ve been using the CLI with the

prefect deploy

command, but I’m curious if there are other methods that are easier or more commonly used within the community. Any suggestions or best practices would be greatly appreciated!

@Marvin How do I configure the prefect dashboard to run on http://0.0.0.0:4200? and it to use "http://0.0.0.0:4200/api" as well

Hello @Marvin I just upgraded my Prefect package from 3.0.3 to 3.0.7, and I’m encountering a few issues: 1. UI Problems: Work Pools no longer display, and creating new ones isn’t possible—the types aren’t available (see attached image). 2. Library Errors: When using the Python library (which wraps the API), I get a

json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

error. 3. Flow Deployment Issues: Deploying a flow to a non-existent Work Pool doesn’t trigger a 404 error; instead, I get a 200 response with a 404 HTML page. - Example:

WorkPool.model_validate(response.json())

fails as the server returns HTML instead of JSON. 4. Client Issues: Using

prefect.client.orchestration.get_client

with

create_work_pool

sends requests that result in HTML responses, causing JSON parsing failures. - Example:

<Request('GET', '<http://127.0.0.1:4200/csrf-token?client=6bd93e79-f5a8-46b2-b99f-b88891b2d3e0>')>

What version to use? Should I consider building a custom REST API client instead?

Hi, how can I pass environment variables to Docker agent without restarting? is there any options to set it in flow, for example pass the path for *.env file or make visible variables from current terminal session to Local agent?