decentraland / builder / 36878583870

57%

master: 57%

Pull #3512

github

docs: name the version a bad rollback order would serve

The comment said zeroing first "opens a gap where a record below the target
serves". `calculateRollout` is more specific than that: it skips records at 0%
and, when no record covers the user, returns the LAST one -- which, with records
sorted descending, is the oldest version still stored.

So the cost of the wrong order is not the next version down, it is the oldest
one on record, and it lasts until the second dispatch lands. On org that waits
on the environment approval gate.

Restoring first remains invisible, since a newer record still sorts ahead and
keeps serving, which is what makes the safe order free.

2637 of 5727 branches covered (46.05%)

Branch coverage included in aggregate %.

7631 of 12288 relevant lines covered (62.1%)

37.27 hits per line