patron gem install issues
this error prevents me from deploying. Has any experienced this? Installing patron (0.4.10) with native extensions /usr/ruby1.8.7/lib/ruby/site_ruby/1.8/rubygems/installer.rb:483:in `build_extensions': ERROR: Failed to build gem native extension. (Gem::Installer::ExtensionBuildError) /usr/ruby1.8.7/bin/ruby extconf.rb checking for curl-config... yes checking for rb_thread_blocking_region()... no creating Makefile make gcc -I. -I. -I/usr/ruby1.8.7/lib/ruby/1.8/x86_64-linux -I. -fPIC -O2 -fno-strict-aliasing -Wall -c session_ext.c session_ext.c: In function ‘Init_session_ext’: session_ext.c:531: error: ‘CURLPROXY_HTTP_1_0’ undeclared (first use in this function) session_ext.c:531: error: (Each undeclared identifier is reported only once session_ext.c:531: error: for each function it appears in.) make: *** [session_ext.o] Error 1 Gem files will remain installed in /disk1/tmp/build_16496_23515118229180/.bundle/gems/ruby/1.8/gems/patron-0.4.10 for inspection. Results logged to /disk1/tmp/build_16496_23515118229180/.bundle/gems/ruby/1.8/gems/patron-0.4.10/ext/patron/gem_make.out from /usr/ruby1.8.7/lib/ruby/site_ruby/1.8/rubygems/installer.rb:446:in `each' from /usr/ruby1.8.7/lib/ruby/site_ruby/1.8/rubygems/installer.rb:446:in `build_extensions' from /usr/ruby1.8.7/lib/ruby/site_ruby/1.8/rubygems/installer.rb:198:in `install' from /usr/ruby1.8.7/lib/ruby/gems/1.8/gems/bundler-1.0.3/lib/bundler/source.rb:100:in `install' from /usr/ruby1.8.7/lib/ruby/gems/1.8/gems/bundler-1.0.3/lib/bundler/installer.rb:55:in `run' from /usr/ruby1.8.7/lib/ruby/gems/1.8/gems/bundler-1.0.3/lib/bundler/spec_set.rb:12:in `each' from /usr/ruby1.8.7/lib/ruby/gems/1.8/gems/bundler-1.0.3/lib/bundler/spec_set.rb:12:in `each' from /usr/ruby1.8.7/lib/ruby/gems/1.8/gems/bundler-1.0.3/lib/bundler/installer.rb:44:in `run' from /usr/ruby1.8.7/lib/ruby/gems/1.8/gems/bundler-1.0.3/lib/bundler/installer.rb:8:in `install' from /usr/ruby1.8.7/lib/ruby/gems/1.8/gems/bundler-1.0.3/lib/bundler/cli.rb:221:in `install' from /usr/ruby1.8.7/lib/ruby/gems/1.8/gems/bundler-1.0.3/lib/bundler/vendor/thor/task.rb:22:in `send' from /usr/ruby1.8.7/lib/ruby/gems/1.8/gems/bundler-1.0.3/lib/bundler/vendor/thor/task.rb:22:in `run' from /usr/ruby1.8.7/lib/ruby/gems/1.8/gems/bundler-1.0.3/lib/bundler/vendor/thor/invocation.rb:118:in `invoke_task' from /usr/ruby1.8.7/lib/ruby/gems/1.8/gems/bundler-1.0.3/lib/bundler/vendor/thor.rb:246:in `dispatch' from /usr/ruby1.8.7/lib/ruby/gems/1.8/gems/bundler-1.0.3/lib/bundler/vendor/thor/base.rb:389:in `start' from /usr/ruby1.8.7/lib/ruby/gems/1.8/gems/bundler-1.0.3/bin/bundle:13 from /usr/ruby1.8.7/bin/bundle:19:in `load' from /usr/ruby1.8.7/bin/bundle:19 FAILED: http://docs.heroku.com/bundler ! Heroku push rejected, failed to install gems via Bundler -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Asynchronous Solr indexing not working
rails 3.0.1 and those gems (I also had trouble with the one mentionned in the docs. could me because of my setup though) gem 'sunspot', '1.2rc2' gem 'sunspot_rails', '1.2rc2' 2010/10/25 Graeme Simpson gra...@simmo.gs Thanks for the info Guillaume. I'll try that. Nick - I'm currently using Rails 2.3.10 (although I was recently on 2.3.8 with the same problem) and Sunspot 1.1. On Oct 25, 1:19 am, Nick Zadrozny n...@onemorecloud.com wrote: Hi Graeme and Guillame, What versions of Rails and Sunspot are you two using? -- Nick Zadrozny -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Asynchronous Solr indexing not working
I had the exact same issue. so I replaced handle_asynchronously :solr_index with: after_save :sunspot_commit def sunspot_commit send_later :index_and_solr_index end def index_and_solr_index index! solr_index end and I know have what I expect. not sure why this needs to be done that way and not the doc way, though 2010/10/22 Graeme Simpson gra...@simmo.gs Howdy, I've recently signed up to heroku and I'm having a little trouble with Solr. I'm trying to index news articles as I am collecting them, approx 350 per minute. They are checked, processed and then saved. I followed the instructions on the heroku docs, and I have... handle_asynchronously :solr_index ...at the bottom of my model, along with a couple of workers running to handle the indexing along with the import tasks. But it doesn't seem to be doing any indexing! Looking at the heroku logs, the delayed job process does seem to be running. * [Worker(host:railgun64.38351 pid:14550)] acquired lock on Article#solr_index_without_send_later * [JOB] host:railgun64.38351 pid:14550 completed after 0.0289 If I leave it running for a while and run a full text search I get no results. But if I trigger a manual index of the model by running 'Model.index', the search works fine afterwards. At the moment I've got the index process running every ten minutes, which is probably a horrible way of doing it. How do I kick the asynchronous indexing into action? Many thanks, Graeme -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Compiled Slug size not changing after removing large gems from Gemfile
I was actually going to write support about this issue for my app, but I ll try here first the slug size of my app has slowly been increasing after each commit, now up to 73Mb. This is definitely not a big application, so I believe something wrong is happening. Could easily be my fault, off course. as heroku mentions here http://docs.heroku.com/slug-compiler, if I want to try and estimate the slugsize of my app, I do a fresh clone of the rep, delete the .git dir, and a du -hsc shows me 23Mb. big difference. on top of that, if I also delete directories mentionned in my .slugignore, it gets down to 6Mb. so I dont understand why there is such a difference. Could it be from the gemfile? Mine looks like this: (I dont think there is that many dependencies) source :gemcutter gem 'rails', '3.0.0' gem 'pg' gem 'awesome_print', '0.2.0' gem 'aws-s3' gem 'devise', '1.1.1' gem 'delayed_job' gem 'formtastic', '~ 1.1.0' gem 'haml' gem 'heroku-autoscale' gem 'hoptoad_notifier','2.3.6' gem 'memcached-northscale', '0.19.5.3' gem 'nokogiri' gem 'oauth' gem 'recurly' gem 'sunspot', '1.2rc2'#, :require = 'sunspot' gem 'sunspot_rails', '1.2rc2'#, :git = ' http://github.com/outoftime/sunspot.git'#, :branch = v1.2 gem 'will_paginate', :git = git://github.com/mislav/will_paginate.git, :branch = rails3 gem 'warden', '0.10.7' group :development do # looks like removing them can free 5-6 Mo of slug size gem 'compass', '= 0.10.2' gem 'ruby-debug', '0.10.3' gem yui-compressor gem 'closure-compiler' gem 'heroku' gem 'heroku_san' end anyone has any idea how to reduce it? I feel I could easily get stuck in 6-8 weeks where I could reach the 100Mb limit. 2010/10/12 Chris Hanks christopher.m.ha...@gmail.com According to the Heroku docs (http://docs.heroku.com/slug-compiler), the git repository is not included in the slug. I've had the same experience as Stephen - I'd specify gems in my Gemfile that would push the slug size up, and then remove them without any effect to the slug size. Then I could destroy the app, create a new one from the same git repository and wind up with a smaller slug size than I'd had before. On Oct 11, 11:52 pm, Keenan Brock kee...@thebrocks.net wrote: Hi Stephen, If you checked in a gem into git Then you deleted the gem from git. Git still has the gem. It is not showing up for today, but git log will show when you added it and removed it. Guess I do not know if you are checking in your bundle dir and gems into git. 1. So are you saying your repo is 17mb, or your slug is 17mb? I'd imagine that the slug would be smaller on your change to the Gemfile. But you stating that your slug is big suggests that maybe the .git directory is included in the slug? The slug size does affect the speed in which a dyno is started / compiles / restarts. But I agree with Chris, I can't imagine it would slow it down too much. --Keenan On Oct 12, 2010, at 12:48 AM, Chris Hanks wrote: Yeah, this has happened to me before, too. I'm pretty sure the problem is on Heroku's end. I don't worry that much about it, though, since the max slug size is 100 MB. On Oct 11, 8:57 pm, stephen murdoch stephenjamesmurd...@gmail.com wrote: I have encountered a few strange problems with Heroku this evening. My repo size somehow managed to bloat to 17mb so I removed some gems from my Gemfile (ran bundle install, git add Gemfile.lock etc etc) and found that my repo was still 17mb. I removed all my gems (apart from rails and pg) and the repo didn't get any smaller. My app is no bigger than 2mb. So I deleted my app (along with my .git and .bundle directories) and created everything from scratch. This seemed to fix the problem, until just now, when I tried to remove 4 large gems from my Gemfile and didn't see any change in the size of my compiled slug on Heroku. Is this something that other people are experiencing? FWIW, I've tried everything I can think of, including removing Gemfile.lock, .bundle etc etc -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@googlegroups.com . For more options, visit this group athttp:// groups.google.com/group/heroku?hl=en. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.comheroku%2bunsubscr...@googlegroups.com . For more options, visit this group at http://groups.google.com/group/heroku?hl=en. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this
