Trove client won't submit min_size, max_size as 0 to ConfigurationParameters

Bug #1398995 reported by Tim Simpson
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mayuri Ganguly

Bug Description

If 0 is passed as the min_size or max_size for a configuration, the Trove client will ignore this value and not place it in the body of a request. 0 is an odd value but is a valid int- the client should not censor this.

Changed in trove:
status: New → Triaged
importance: Undecided → Medium
assignee: nobody → Tim Simpson (tim-simpson)
milestone: none → kilo-1
Changed in trove:
milestone: kilo-1 → kilo-2
Changed in trove:
assignee: Tim Simpson (tim-simpson) → Nikhil Manchanda (slicknik)
milestone: kilo-2 → kilo-3
Changed in trove:
assignee: Nikhil Manchanda (slicknik) → Mayuri Ganguly (mayuri-ganguly)
affects: trove → python-troveclient
Changed in python-troveclient:
milestone: kilo-3 → none
Revision history for this message
Mayuri Ganguly (mayuri-ganguly) wrote :

I looked into it, it seems like there's no such issue. When 0 is passes as a max_size or min_size, it is not getting ignored. 0 min_size/max_size is a valid configuration parameters.

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.