Zanie Blue
Zanie Blue
Unfortunately you've encountered a bit of an edge case there :) We can track relationships when data is passed, but some types of data are not distinguishable as unique in...
> Maybe this was not always the case and in a previous version tasks returned prefect futures by default? Yeah we had futures by default in the beta but it...
This is surprising. The API should absolutely not allow two processes to enter a running state. Two instances of the infrastructure may start, but the flow run should not run...
What version is your server? I believe we have resolved this with #6852
Sorry that's unreleased! It'll be out today and should close this issue :)
I'm okay with switching to "default" since we're using that elsewhere now. Separately, it seems nice to have a CLI option e.g. `--agent-work-queue ` for this command.
Hm. The `login` method name doesn't make a lot of sense if we are returning a client. I think we'll want to do some refactoring of the capabilities provided by...
We'll want to retain the old methods for backwards compatibility for now but include a deprecation warning. They can just call through to `get_docker_client` after raising a warning. I think...
Perhaps ignore what I said about the base class then, we can address that later.
`future.get_state()` returns the current state. You'd have to poll this very frequently to get the intermediate states a task passes through. I would not recommend it as a pattern. `future.wait()`...