Free trial · 14 days · Cancel anytimeGet started

Critical fix (found in production testing): the scale-app command had never worked, since…

v0.19.2-beta
  • Critical fix (found in production testing): the scale-app command had never worked, since its introduction in 0.19.0-beta. The agent's WebSocket frame router (transport/client.go) keeps its own list of accepted command types, separate from the dispatcher that executes them — scale-app had been added on the dispatcher side but never to that routing list. As a result every scale attempt was silently dropped ("drop unknown frame type=scale-app" in the agent logs), never reaching the handler nor returning an error — the hub then waited for the answer until its own timeout, exposing the user to a raw gateway error page. scale-app is added to the list. The existing guard test (TestDispatchInbound_RoutesAllDispatcherCommands, written for this precise kind of drift) also had a stale list that did not cover scale-app (nor restore-backup/push-backup) — fixed to reflect every dispatcher command.