-
Notifications
You must be signed in to change notification settings - Fork 4
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
fireslurprb error #3
Comments
Hey Mike. Make sure you've run |
Thank you! bundle exec ruby fireslurp.rb --help works as expected Now when I run bundle exec ruby fireslurp.rb --instagram-key=mykey springsfire01 I get: Faraday: you may want to install system_timer for reliable timeouts Thanks again, Mike On Thu, Aug 7, 2014 at 3:06 PM, Ken-ichi [email protected] wrote:
|
That doesn't sound right. What version of ruby are you using? I'm using 1.9.3 p484, but maybe something changed in Ruby 2+? I don't think it should have http://ruby-doc.org/core-2.0/Proc.html#method-i-yield. Can you try switching Ruby versions (assuming you're using RVM)? |
ruby 1.9.3p194 (2012-04-20 revision 35410) [x86_64-linux] On Thu, Aug 7, 2014 at 4:36 PM, Ken-ichi [email protected] wrote:
|
My mistake, wrong machine. ruby 1.8.7 (2010-08-16 patchlevel 302) [i486-linux] I'll update and let you know. Thanks! Mike On Thu, Aug 7, 2014 at 4:48 PM, Mike Maki [email protected] wrote:
|
I apologize if this is not the right place to report this. We would like to start using changebrackets for the Springs Fire recovery in the Santa Monica Mountains.
I'm trying to run fireslurp.rb --help on Debian squeeze. Everything installed without error, ruby rubygems, and bundler. When I run ruby fireslurp.rb --help it I get:
/var/lib/gems/1.8/gems/faraday-0.8.9/lib/faraday/request/multipart.rb:4: warning: already initialized constant DEFAULT_BOUNDARY
/usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in
gem_original_require': no such file to load -- instagram (LoadError) from /usr/lib/ruby/1.8/rubygems/custom_require.rb:31:in
require'from fireslurp.rb:8
Thanks,
Mike
The text was updated successfully, but these errors were encountered: