The server reports the end of every queue with two dicts,
nodepack_result and model_result, keyed by the id of each task. The
Model Manager read model_result as an array, so result.length was
undefined, the guard for an empty result never held, and the end of
any queue ended its pending install. After a model install request
that the server refused, the end of the next queue, such as a node
pack install, asked to click Refresh and raised the notice that all
model downloads were completed, although no model had been installed.
- Count the keys of model_result in the guard and in the status text
- Hide the Stop button when the install is completed, not at the end
of every queue
- When a queue ends without a model result, ask the server what is
left: while tasks are left the install stays pending, and with none
left the dialog returns to idle without a message. An install that
started while the server was asked is left alone
- Show the Stop button only while the install that was queued is
still pending; a queue can end before its start request is answered
- Add tests that run the shipped handlers in node
- Add a CHANGELOG entry
The change for manager-v4, which tells the batches apart by their id,
is #3536.