Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Command Tool Exceptions #4

Open
jdgwartney opened this issue Sep 3, 2015 · 2 comments
Open

Command Tool Exceptions #4

jdgwartney opened this issue Sep 3, 2015 · 2 comments

Comments

@jdgwartney
Copy link

[vagrant@centos-6-6 ~]$ flamethrower fire 2000 1 "http://es.com:9200"
/home/vagrant/.rvm/gems/ruby-1.9.3-p551/gems/rubberband_flamethrower-0.5.3/lib/rubberband_flamethrower/data_generator.rb:66:in generate_random_insert_data': wrong number of arguments (0 for 1) (ArgumentError) from /home/vagrant/.rvm/gems/ruby-1.9.3-p551/gems/rubberband_flamethrower-0.5.3/lib/rubberband_flamethrower/flamethrower.rb:38:inblock in fire'
from /home/vagrant/.rvm/gems/ruby-1.9.3-p551/gems/rubberband_flamethrower-0.5.3/lib/rubberband_flamethrower/flamethrower.rb:36:in times' from /home/vagrant/.rvm/gems/ruby-1.9.3-p551/gems/rubberband_flamethrower-0.5.3/lib/rubberband_flamethrower/flamethrower.rb:36:infire'
from /home/vagrant/.rvm/gems/ruby-1.9.3-p551/gems/rubberband_flamethrower-0.5.3/lib/rubberband_flamethrower.rb:13:in block in fire' from /home/vagrant/.rvm/rubies/ruby-1.9.3-p551/lib/ruby/1.9.1/benchmark.rb:280:inmeasure'
from /home/vagrant/.rvm/gems/ruby-1.9.3-p551/gems/rubberband_flamethrower-0.5.3/lib/rubberband_flamethrower.rb:12:in fire' from /home/vagrant/.rvm/gems/ruby-1.9.3-p551/gems/rubberband_flamethrower-0.5.3/bin/flamethrower:14:in<top (required)>'
from /home/vagrant/.rvm/gems/ruby-1.9.3-p551/bin/flamethrower:23:in load' from /home/vagrant/.rvm/gems/ruby-1.9.3-p551/bin/flamethrower:23:in

'
from /home/vagrant/.rvm/gems/ruby-1.9.3-p551/bin/ruby_executable_hooks:15:in eval' from /home/vagrant/.rvm/gems/ruby-1.9.3-p551/bin/ruby_executable_hooks:15:in'

@captainkerk
Copy link

this issue was fixed in this PR: #1

However, it seems it never made it to the gem.

I got around it by changing the file directly after installing the gem

@beachwood23
Copy link

I'm still having issues with this. Any chance the Gem will be updated?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants