SetCollectionSize upper bound is never reached

Bug #681191 reported by Philip Peitsch
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
NGineer
Fix Released
Medium
Unassigned

Bug Description

The MaxValue in the SetCollectionSize is never actually reached as it use simply used as the upper bound when calling Random.Next. This means that if an upper bound of 0 is set, Random.Next throws an exception

Related branches

Changed in ngineer:
status: New → Confirmed
importance: Undecided → Medium
milestone: none → 0.5
Changed in ngineer:
status: Confirmed → Invalid
milestone: 0.5 → none
status: Invalid → Confirmed
milestone: none → 0.5
Changed in ngineer:
status: Confirmed → Fix Committed
Changed in ngineer:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.