Error responses are now always part of a dict with lowercase error as
key.
Files are cached across restarts by url. Likely needs additional
testing for checkpoints.
Fixed an error where booleans could not be eserialized as part of the
change to sign file uploads.
Responses to orchestration are now wrapped and contain always contain a
message id to keep requests syncronized.
On connection failure, a reconnection is attempted.
Execution time is tracked and included in response data.
Response urls are now signed
Responsiveness has been a point of major frustration when debugging.
In an attempt to isolate performance issues and move closer to the end
goal of sophisticated orchestration, an additional means of control has
been added where workers connect to a control server and open a
websocket for two-way communications
With improved logging, I believe I misinterpreted the original error
message. The version of comfy used inside the current container is out
of date, and has fewer args for call_on_start.
Orchestration code (mostly endpoints for probes) was intended as a
seperate plugin, but given the tight tying of asynchronous dependency
code, it has been included in this history and will likely be branched
off as a dedicated repo not available for non client/server
architectures.
much of the execution wrapping code has been moved into a wrapper on
execute instead of recursive executed. This cleans up logic and fixes
issues with collecting all outputs when multiple output nodes exist