Rudder

We can reproduce it in homepage, on Rudder 4.1, by inputing the following value to `homePage` js function:

homePage(
   [0.0, 0.0, 63.95, 0.96, 0.08, 0.0, 14.06, 20.15, 0.5, 0.0, 0.29, 0.02, 0.0, 0.0]

, 62
, {"labels": ["Good (> 75%)", "Average (> 50%)", "Poor (< 50%)"]
  , "values": [4, 1, 2]
  , "colors": ["#9bc832", "#f0ad4e", "#c9302c"]
  }
, {"Poor (< 50%)": "#c9302c", "Average (> 50%)": "#f0ad4e", "Good (> 75%)": "#9bc832"}
, {"pending": null, "active": 7}
);

So it must be a problem in the bar algorithm.

The problem is that the last bar is too large to be contained in the bar and goes on line.

It is because we are using float to calculate a number of pixel, and float are the worst thing ever. I mean, we must only use algorithme that work with int. If it does not work with int, it will lead to that kind of problems (or worse: #10773).

PR https://github.com/Normation/rudder/pull/1942

PR https://github.com/Normation/rudder/pull/1944

Applied in changeset rudder|8c2abadf63d53920505dd63a729f31e069f8bd0f.

This bug has been fixed in Rudder 4.1.12, 4.2.6 and 4.3.1 which were released today.

• 4.1.12: Announce Changelog
• 4.2.6: Announce Changelog
• 4.3.1: Announce Changelog
• Download: https://www.rudder-project.org/site/get-rudder/downloads/