Closed chrisgoddard closed 1 week ago
Hey @chrisgoddard! Thanks for reporting this. I just did a fresh env on my machine and couldn't reproduce. But no worries, I'm on the case. Can you pip freeze? I have some suspicion that the --pre flag wasn't turned on (that's our fault for omitting in our quickstart if the case) and you might be on an old version of CF.
Sorry, to be more specific, can you share the version of controlflow in your environment?
Hey @chrisgoddard! Thanks for sharing. I see how you hit that code path, and added a guard. It's a weird situation the orchestrator didn't expect -- your workflow must contain tasks in an incomplete state, but the orchestrator believes none are "ready" to run (meaning they have incomplete upstream dependencies) -- is it possible you have a cyclical workflow? We don't explicitly raise errors in that case. #183 should fix the actual error, though.
For Prefect -- it should run happily in its ephemeral mode with zero config, though if you have an existing Prefect environment maybe it tried to talk to your existing server API URL? I'll look at exposing a separate config for CF's Prefect instance to avoid any unwanted cross talk
0.8.1 is released and includes this fix! we'll work on making the Prefect settings more isolated as well.
Yeah I think you're right - I had an old Prefect config from a while back.
Thanks for quick turnaround!
Trying the agent example from the getting started.
Firstly - you don't actually mention configuring Prefect (i.e. starting Prefect server) - that might trip some folks up if they're coming to this for the first time.
Secondly, I'm getting the following error when I run the example:
I have my OpenAPI key set.
What am I missing?