Job progress doughnut renders funny when target node count is less than running nodes

[chrisalexander]

Description

Imagine you have many tasks running. You then scale down your pool to 1 node, set "Current Task Action" to "Task Completion" and hit OK.

In this scenario:
CurrentNodes = hundreds
RunningJobs = hundreds
Target nodes = 1

And the doughnut wraps around itself a few times as it doesn't understand this scenario very well:

Version of BatchLabs(For bugs)

Latest

[timotheeguerin]

Hhm, I believe then that using the currentNodes instead of targetNodes should fix that problem