Zanie Blue
Zanie Blue
This behavior is intentional. All agents can be stopped/started without affecting their flow runs. I'm not sure I agree that this agent should kill its runs on shutdown.
> Ok, but if I restart the agent, the flow does not continue and still in Running state It's possible when the agent is killed the flow crashes but does...
Great thanks! It's weird that the SIGINT sent to the parent process isn't forwarded to the child process in a way that lets our interrupt detection report the flow run...
> the flow run should send an “is alive” signal periodically to the server, allowing the server to check which flow runs are RUNNING and mark the ones that are...
Hey @argibbs I'm not working on this project anymore but there's definitely some people thinking about the right way to make this better! cc @WillRaphaelson / @billpalombi
> could `(async )with self._state_lock:` move under `_state_housekeeping` function? I agree, it's always used.
For those following, https://github.com/astral-sh/uv/issues/3347 is tracking the lock file work in progress.
The classifiers are for all supported versions, right? This should already be available via `requires-python`, with the exception of whether or not the latest version is supported in some cases?
Fair enough :) Thanks for the report.