Skip to content
GitHub

HotLoop Flow 2.10.0 release notes

HotLoop Flow 2.10.0 brings FlowLab a long way toward a real bench: instruments you can talk to, a case structure, waveforms, shared record types, sub-diagrams, log rotation, and the diagram error list in CI. An agent can now list, read, deploy and roll back flows over MCP. It also fixes a way the durable MQTT output could send one message twice.

  • Flow’s own MCP tools. Seven built-in tools at the same /mcp, beside the flows’ own: list_flows, get_flows, get_flow, deploy_flows, list_deployments, rollback_deployment and inject_node. Each runs the admin API’s own handler as the caller the endpoint authenticated, so a deploy from an agent meets everything a deploy from the editor does: the revision check, typed wires, plugin refusals, and failing flow tests. A caller needs mcp.call and the tool’s own permission (flows.read, flows.write or inject.write), and a tool it may not call is not in its list. They stay across a deploy, and a flow cannot serve one of their names. The README has the table.
  • Instruments. Instrument sessions over a raw socket or a serial port, a query node, and SCPI parsers, so a diagram can ask a meter for a reading and parse the answer.
  • Case structure. dia-case runs only the body its selector picks: a boolean, a number, a string or an enum, with a default case. A value no case names, with no default, is an error on the error wire, and deploy warns when there is no default.
  • Waveforms. A waveform is a block of samples that knows when it started and how far apart they are. dia-wave builds one and dia-wave-parts takes one apart. A size cap cuts a waveform at 1,048,576 samples by default and counts what it dropped. The analysis nodes accept a waveform where they take an array and use its step, and the TDMS log writes wf_start_time, wf_increment, wf_samples and its attributes.
  • Shared record types. Name a record type once on a diagram tab and set shape on a dia-bundle or dia-field to use it. Rename a field in the type and every use that still has the old name is a problem at the next deploy. A bundle holds each value to its field’s kind when it runs. A type is available as JSON Schema.
  • Sub-diagrams. dia-sub is a diagram used as a node, with named inputs and outputs. A name ending in ? is optional, and one ending in ~ is recommended, which warns at deploy when it has no wire. POST /diagrams/{id}/sub takes a flow file and a selection and gives the flow file back with those nodes cut out into a sub-diagram, the connector worked out from the wires that cross the edge.
  • Log rotation and retention. The text and TDMS log nodes can start a new file at rotateMB megabytes or rotateHours hours and keep the newest keep finished files. The finished file takes the log’s name with the time it closed before the extension.
  • The diagram error list in CI. hotloop-flow test and the deploy gate run the editor’s check on every diagram in the flow file and list each one that cannot run, with its diagram, node and input.
  • hotloop-flow test can now fail a file whose tests all pass. If a diagram in the flow file cannot run (an input nobody wired, a body that never says stop), the file fails, in the text output, the JSON, the JUnit report and the deploy gate. A flow file with no diagrams behaves as before. Warnings are listed and never fail.
  • Flow holds its heap to the container’s memory limit. At start Flow reads its cgroup memory limit and caps the Go heap at 85% of it, so a large flow file collects before it reaches the limit instead of being OOM-killed. A GOMEMLIMIT in the environment still wins, and the boot log says which limit applies. Seen on a plant with 13,727 nodes in 74 tabs, which was restarting at a 2Gi limit with a live heap near 800 MiB.
  • A durable MQTT output no longer sends a message twice after a reconnect. After a reconnect the client marks the link up before it replays its store, and a publish handed over in that gap went out twice with no unconfirmed send behind the second. The output now waits until the replay has taken its snapshot. MQTT 5 connections were checked and do not have the gap.

On the log nodes: rotateMB, rotateHours and keep, all off by default. On dia-wave: maxSamples, 1,048,576 by default. On dia-bundle and dia-field: shape. On dia-sub: body, ins and outs.

A plain helm upgrade to the 2.10.0 image and chart, or the new tag in your Quadlet unit. Nothing happens on first start and nothing needs migrating. Flow files from 2.9.1 load and save byte for byte. Check any CI job that runs hotloop-flow test against a flow file with diagrams in it: a diagram that could not run now fails the file.

Image: ghcr.io/hotloop-io/hotloop-flow:2.10.0, linux/amd64 first, with arm64 following in 2.10.1. Chart: https://hotloop.io/hotloop-flow/. The README at this tag has the rest, with pictures: https://github.com/HotLoop-io/hotloop-flow/blob/v2.10.0/README.md