-
### Describe the current behavior
There's not color. It's all white, which is a bit of an adjustment coming from running prefect locally where you get accustomed to distinguishing different logs by t…
-
### Description
Running a Python script that contains `cf.flow` decorator doesn't create a Prefect flow.
Running other scripts with regular Prefect flows in the same terminal window works fine: ad…
-
### Describe the current behavior
Instructions for setting up a worker are always included when deploying a deployment.
```
Successfully created/updated all deployments!
…
-
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the…
-
### Bug summary
I ran into an issue with Prefect while working locally that looks like an endless loop happening on the backend.
I've observed the following behavior locally several times:
1. Aft…
-
### First check
- [X] I added a descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the Prefect documentation for this issue.
…
-
### Describe the current behavior
If you deploy a flow, the 'Flow Name' used on the Deployments UI page is the name of the decorated function, rather than the flow's name from the @flow(name="xyz")…
-
### Bug summary
Not every time, but regularly for failed deployment run, I see such error log:
```
Could not determine exit code for '{{deployment-name}}'.Exit code will be reported as -1.First c…
-
### First check
- [X] I added a descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the Prefect documentation for this issue.
…
-