Chris White

Default badges for pools & queues

1

At this moment, all work pools come with a "default" queue that is the one work is placed in if no other queue is specified. The only way to identify...

Work Pool Queue creation headers are noisy

8

Right now when you go to create a work pool queue, most fields are optional; providing "(Optional)" on each field seems excessive and redundant - ideally there is some visual...

Below I have provided two separate deployment YAML files: - "optional.yaml" below creates a deployment with an _optional_ parameter called `could_be_null` - "required.yaml" below creates a deployment with a _required_...

Results docs

1

Polishes up docs on result persistence; I think we over-explained things previously, and a few things have changed. My goal is to put a strong foundation in place that is...

Fix labeler job

1

I noticed that the labeler job was failing on contributor PRs ([example here](https://github.com/PrefectHQ/prefect/actions/runs/10584311321/job/29328278417?pr=15070)). I did some reading and found two things that needed fixing: - we need to check out...

3.0 analogue of #15113 - see description there

Don't persist exceptions

1

There's really no need to persist exceptions attached to Failed states - they should be logged, and get re-raised in-process, but otherwise they don't need to be stored and retrieved....

### Bug summary Currently when cutting a release, we build and publish the `prefect-client` package from [this workflow](https://github.com/PrefectHQ/prefect/blob/main/.github/workflows/prefect-client-publish.yaml). As you can see, this workflow uses [the verification workflow here](https://github.com/PrefectHQ/prefect/blob/main/.github/workflows/prefect-client.yaml). This...

[This test](https://github.com/PrefectHQ/prefect/blob/4da5da207b126639998917cb1e246f7b15484405/tests/results/test_result_fetch.py#L18) fails on occasion, e.g., https://github.com/PrefectHQ/prefect/actions/runs/10462489553/job/28972815597 ``` FAILED tests/results/test_result_fetch.py::test_async_result_warnings_are_not_raised_by_engine - TypeError: unsupported operand type(s) for +: 'int' and 'NoneType' ```

### Describe the current behavior Currently, Prefect supports many user interfaces that we attempt to maintain as compatible with both *synchronous* execution as well as *asynchronous* execution. [A popular example...