Zanie Blue

Tracking: Improvements to the Cloud login experience

1

This is a tracking pull request for changes to the CLI login experience. ### Changes - #6999 - #7334 ### Planned - Check if the user is logged in and...

Running a deployment with a flow call in it fails

1

### 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. -...

Extend `visit_collection` with support for annotations

1

Extends https://github.com/PrefectHQ/prefect/pull/7248 but solves https://github.com/PrefectHQ/prefect-dask/issues/43 without requiring the changes in https://github.com/PrefectHQ/prefect-dask/pull/45 ### Example ### Checklist - [ ] This pull request references any related issue by including "closes ``" -...

Update `create_cloned_field` to use a global cache

16

Closes https://github.com/tiangolo/fastapi/issues/4644 by instantiating a global dictionary to store cloned fields. This prevents repeated copying of models which can have significant performance affects. Please see the issue for more details....

Fix usage of `install_macos.sh` in README

4

The provided suggestion to run `./install_macos.sh` from the `util` directory fails since the script expects to be relative to the root of the content. ``` ❯ cd util ❯ bash...

`fail_after` deadline is set on initialization not context entry

8

Discussed at https://gitter.im/python-trio/AnyIO?at=63ac6d617de82d261600ea24 When using a `fail_after` context, the deadline is set at "initialization" time rather than `__enter__`. See https://github.com/agronholm/anyio/blob/0cbb84bfadd9078c5dad63bab43907ed0dd555a1/src/anyio/_core/_tasks.py#L112-L114 ```python import anyio async def main(): ctx = anyio.fail_after(5) await...

Add `prefect server status`

4

### First check - [X] I added a descriptive title to this issue. - [X] I used the GitHub search to find a similar request and didn't find it. -...

### First check - [X] I added a descriptive title to this issue. - [X] I used GitHub search to find a similar request and didn't find it 😇 ###...

`fail_after` deadline is set on initialization not context entry

21

This is a duplicate of https://github.com/agronholm/anyio/issues/514 — they are following the convention established here in trio. When using a `fail_after` context, the deadline is set at "initialization" time rather than...

Similar idea to #1356 Attempting to reproduce https://github.com/astral-sh/uv/issues/1521#issuecomment-1949299848