set the channel description: https://github.com/PrefectHQ/ui

Hi Team, I believe I have found a bug on the prefect cloud UI, when you want to add a label to a label less flow, saving the a new label does not work. example:

Is there a way I can see what agent ran my flow? I can't seem to find that in the UI.

Hi guys, i was new to prefect, i ran a very basic code flow, and then i want to see it in UI, but i am getting error like this, "ValueError: Project my_first_flow not found. Run

client.create_project("my_first_flow")

to create it." And here is my basic code

from prefect import task, Flow

@task def hello_world(): return "hello prefect" @task def prefect_say(s:str): print(s) with Flow("my_first_flow") as f: r = hello_world() s = prefect_say(r) # f.run() f.visualize() f.register("my_first_flow")

thanks in advance.

Hi All, we are doing PoC for Prefect Core Server in our firm and were looking at putting Prefect Core server behind NGINX so that NGINX can do Authentication and Authorisation which looks all good but I was not sure how can I control the UI feature to stop people who are not authorise to restart task or change the state (may be by disabling the restart button or so based on some config), thanks.

Hello 🙂 I just started messing around a bit with prefect, and i have an issue in the UI (not sure if it’s caused maybe by some extension i have installed?) It seems all the “cards” have a place for a scroll bar (or maybe some other gap) when not needed , here are some examples - Just to test i disabled the “overflow: scroll” and it looks better

Should I open an issue in the UI repo?

Hi everyone! I’m looking for guidance on the following scenario. Currently playing around with Prefect Cloud. I have my execution environment for this exercise setup to be an EC2 instance and I’m using file based storage via Github. What’s the best practice for running the

.py

file locally to test that it works as intended before pushing to GH without changing any code? From my understanding you shouldn’t have

flow.run()

in your file when using Prefect cloud, but that’s how I started off running things locally Simple hello world script for reference

import prefect

from prefect import task, Flow
from prefect.environments.storage import GitHub


@task
def hello_task():
    logger = prefect.context.get("logger")
    <http://logger.info|logger.info>("Hello world!")


hello_flow = Flow("gh_storage_flow", tasks=[hello_task])

hello_flow.storage = GitHub(
    repo="{redacted}",
    path="{redacted}",
    secrets=["{redacted}"]
)

# Basically, I want the functionality of the below line so I can run this locally via Pycharm and then push to GH, merge to main branch, register, etc, and schedule via the UI to execute in our dedicated execution environment, but when you aren't running this as a script my understanding is that you need to remove the following line
hello_flow.run()

Just had a weird UI bug, seems to be a small CSS issue on the page to manually run a flow.

Hi there! Quick question: can someone help me understand why the Cloud UI shows me the

.info

log, but not the

debug

log in this snippet? (Using the logging example from the docs here: https://docs.prefect.io/core/concepts/logging.html)

@task
def my_task(data):
    from prefect import context
    logger = context.get("logger")
    <http://logger.info|logger.info>("info log inside mytask")
    logger.debug("debug log inside mytask")

quick question - are there any plans to add a scheduling/calendar/agenda type component to the cloud UI? a view that essentially gives you a nice visual outlining all your flows and what they time of execution expectations are

Is there a list somewhere of companies that are using Prefect? Not looking for a comprehensive list, just sometimes product pages say "Used by these top companies..." Was curious

After upgrading from 0.13.14 to 0.13.16 UI incorrectly shows Summary and Failed flows aggregations. Looks like they always show stats for maximum time scale regardless of range specified. Graphql query for these stats fetch flow runs based on

updated

field. So does that mean that after upgrade all my flows runs two week old got updated for some reason?

Noticed that the duration ticker continues to tick up indefinitely for a task that was skipped due to a conditional case statement. The state of the task is correctly listed as "Skipped", but for some reason the duration ticker continues to tick.

Hi, 👋 Nice update to the new Prefect UI!: ) I thought it would be quite cool and useful if on hover it would show the average time it took for mapped jobs. Does anyone else share this view? : )

Hi there! I reported this issue awhile back but I wasn’t sure if a bug was filed. Does anyone know about this? https://prefect-community.slack.com/archives/CL09KU1K7/p1601577210329700?thread_ts=1601558767.283400&cid=CL09KU1K7

[resolved] Run Flows Never Starting Here's an issue I keep running into: 1. Run and register a flow from the terminal 2. Click "QuickRun" from cloud.prefect.io 3. Wait 4. Eventually the run flow shows up as "Late" If I run a super simple example, the flow runs fine from the browser. But when I add real work into it, the run flow never shows up as being started.

ModuleNotFoundError How do I tell the flow where the library is found? The package I want to use is installed in my virtualenv, and the flow runs from the terminal. But when clicking "QuickRun" from the browser, the same flow complains of ModuleNotFoundError.

Hi all! I’m having a RAM issue when running one of my flows (diagram in thread). Essentially, I have a list of calls I need to make to a source system that I store in a list and the flow is for each item in that list

ping source system for dataset -> send dataset to pandas DF -> store dataset as a file in S3 -> push contents of said file to our datastore

I’m using the

LocalDaskExecutor

to do DFE and that’s helped a ton as the flow used to fail at the first step because it was doing Breadth first and holding all of the datasets in memory. I expected that once the task tree was completed for each dataset that it’d release that memory but that doesn’t seem to be the case. Am I doing something wrong/poorly or is there a way to free up that memory once the terminal task has completed for each branch?

(I incorrectly posted this issue in the server channel and had a thread with @nicholas. Now that I have more information, moving it here.) I can cause a browser crash by visiting the “schematic” tab with a small dag that has 100 root nodes that each have 1 child. I was able to track this down to a very specific d3-dag call. I created a minimal repro and filed it with the author of d3-dag (https://github.com/erikbrinkman/d3-dag/issues/52). What I’d like to know is: is there a work-around or is it possible to get patch for my installation of Prefect? I’m performing an evaluation and this has become a blocking issue, so I’d like to know what’s the right next step (wait for fix? find work around? maybe it will be obviated in the next release?). Thanks!

Hey, I am receiving this error after running. Also the agent serverless kubernetes cluster is not showing up in the Prefect UI dashboard @Scott Zelenka and @Pedro Martins have faced similar issues before linking their previous conversations here https://prefect-community.slack.com/archives/CL09KU1K7/p1596036675380000 and https://prefect-community.slack.com/archives/C014Z8DPDSR/p1607966613290400

$ prefect agent kubernetes install -t <MY_TOKEN> --rbac | kubectl apply -f -

Warning Unhealthy kubelet  Liveness probe failed :8080/api/health Logs of the failing pod made to restart by K8s

Warning LoggingDisabled 48m          fargate-scheduler Disabled logging because aws-logging configmap was not found. configmap "aws-logging" not found

 

Normal  Scheduled    48m          fargate-scheduler Successfully assigned default/prefect-agent-7bcdb4f975-pftnw to fargate-ip-10-0-231-193.ap-southeast-1.compute.internal

 

Normal  Created     43m (x4 over 47m)   kubelet      Created container agent

 

Normal  Started     43m (x4 over 47m)   kubelet      Started container agent

 

Normal  Killing     42m (x2 over 45m)   kubelet      Container agent failed liveness probe, will be restarted

 

Normal  Pulling     41m (x5 over 48m)   kubelet      Pulling image "prefecthq/prefect:0.14.0-python3.6"

 

Normal  Pulled      41m (x5 over 47m)   kubelet      Successfully pulled image "prefecthq/prefect:0.14.0-python3.6"

 

Warning Unhealthy    12m (x13 over 46m)  kubelet      Liveness probe failed: Get <http://10.0.231.193:8080/api/health>: dial tcp 10.0.231.193:8080: connect: connection refused

 

Warning BackOff     3m3s (x113 over 43m) kubelet      Back-off restarting failed container

Does the open-source UI supports team and project settings? Couldn't find a way to delete a project.

Hi team, i have system running some flows using prefect core. I was looking for a UI to make it more user-friendly and also control the start/stop of flows and easily identify failed tasks/flows. Can I follow the steps at https://github.com/PrefectHQ/ui to get the same? Is there anything else that I would need?

Hi team, I am exploring Prefect cloud and Prefect server. I am trying the steps from universal deploy https://cloud.prefect.io/tutorial/Universal-Deploy#universal-deploy to Create an agent token using

prefect auth create-token -n my-runner-token -s RUNNER

I am getting an error

"Error: Auth commands with server are not currently supported."

Also, what is the easiest way to run a sample flow on prefect cloud? I have this flow which i am running using repl.it https://repl.it/@MinakshiChandra/PrefectDemo#main.py and trying to see this flow on prefect cloud

Hi all - Question about the cloud platform. Is it normal the read-only users not have access the the logs of a flow?

hi! where can I find slack notification template editing? I receive bad URL in notifications…

is there a way to clone existing flow and register new one in UI?

hello… I am running prefect server in aptible… because aptible doesnt allow docker-compose I am running each component of the server in its own firewalled service… the issue I’m having is related to CORS