Just to add further, in Rally currently all function classes defined in rally.cli.commands.* have only 1 required argument ( e.g. start function in Task class in rally.cli.commands..task ) and hence the logic of count works great so far!!
However, in case we make > 1 required args in any function in future, then the bug will reproduce. I thought it would be better to harden the validate_args() function and NOT work under the assumption of having only 1 required argument in all functions always.
@Alexander- I'm sorry i did not see your example paste earlier. (http:// paste.openstack .org/show/ 491132/).
Just to add further, in Rally currently all function classes defined in rally.cli. commands. * have only 1 required argument ( e.g. start function in Task class in rally.cli. commands. .task ) and hence the logic of count works great so far!!
However, in case we make > 1 required args in any function in future, then the bug will reproduce. I thought it would be better to harden the validate_args() function and NOT work under the assumption of having only 1 required argument in all functions always.