@Marvin - I am having some challenges with typechecking on my tasks when I use

.submit()

. My task function is annotated as returning an

int

but when I pass the result from

task.submit()

to another task function the expects an int, the type checker complains that I am not passing an

int

I am passing a

PrefectFuture[int]

.

It sounds like you're encountering an issue related to how Prefect handles task execution and typing in your version. Prefect uses futures to handle results of asynchronous task execution, which means when you call

.submit()

on a task, it returns a

PrefectFuture

object rather than the literal return type of the task function. To address this, let's determine your Prefect version and find the best resources or solutions for you. I'll search Prefect's documentation and GitHub issues to find more detailed information on this topic. Please give me a moment. Oops! It seems I encountered a bit of a hiccup in the search process (it happens even to the best of us). Let me make sure I provide you with the right guidance. Your issue stems from the fact that when you submit a task using

.submit()

, Prefect returns a

PrefectFuture

instead of an

int

. You need to resolve or unwrap this future to get the actual result before passing it to another function expecting an

int

. Here's what you can do: 1. Use

future.result()

to get the actual result from the

PrefectFuture

. 2. Ensure you handle this appropriately, possibly inside another task, especially if you're maintaining asynchronous execution. For more specific advice or further questions about Prefect's handling of futures and typing, I recommend checking: - Prefect documentation - GitHub issues related to your version of Prefect. You might find examples or patterns shared by the community that can offer better insights into handling these scenarios effectively. And remember, every future has its purpose—it just needs a little time to fulfill it!