umh-core
v0.45.2
v0.45.2
Improvements
BYPASS_WRITE_FLOW_VALIDATION=truenow also lets write flows subscribe to topics outside the location of their own bridge, such as a historian bridge that stores data from other sites. These write flows keep running, and the bridge reports degraded with the offending topics in its status. Each topic must still start withumh.v1.and name exactly one data contract- Deploying a bridge while CPU, memory or disk is degraded now fails within a second instead of after 30 seconds. The error says which resource is degraded and how to start bridges anyway, and its error code names the resource:
ERR_BRIDGE_REFUSED_CPU,ERR_BRIDGE_REFUSED_MEMORYorERR_BRIDGE_REFUSED_DISK. As with any failed deploy, the bridge is kept
Fixes
- A bridge whose flow logs an error right after it starts, for example a Beckhoff ADS symbol that does not exist, now shows degraded for 10 minutes after the error, and its status counts down until the error clears. Before, its status switched between degraded and active about once a second, the status said the error clears in 0s, and deploying or editing the bridge could report success despite the error