I had someone recently getting the same issue as you, and it was
because of the vendored version of BlankSlate in Rails (though he
was using a much older version of Rails, so I'm not yet convinced
it's the same problem we're facing). I've just removed the
BlankSlate reference from TS 1.x, just haven't released a new
version with that change.
Arg, I get an error when trying to deploy to Heroku. When bundler runs I
Using thinking-sphinx (1.4.10) from
git://github.com/freelancing-god/thinking-sphinx.git (at e87898b)
Installing flying-sphinx (0.6.1)
Installing haml (3.1.4)
Installing hoe (2.12.4)
`install': hoe requires RubyGems version >= 1.4. Try 'gem update
--system' to update RubyGems itself. (Gem::InstallError)
from /usr/ruby1.8.7/bin/bundle:19:in `load'
! Heroku push rejected, failed to install gems via Bundler
I'll try to add an older version of hoe and see if that fixes it...
FYI. Hoe is definitely coming in with flying sphinx (maybe a dependency
of a dependency?). To verify I just removed flying_sphinx (and the hoe
reference) from my Gemfile and there is no hoe in my Gemfile.lock. When
I add fs back to the Gemfile it reappears and is referenced by 'mash' if
that is any help...
Running bundle update will rebuild your snapshot
from scratch, using only
the gems in your Gemfile, which may resolve the conflict.
[production][~/code/planet-documentary] bundle update Updating
Fetching source index for http://rubygems.org/
Bundler could not find compatible versions for gem
flying-sphinx (= 0.6.1) ruby depends on
activerecord (< 3.0.0, >= 1.15.6) ruby
rails (~> 3.1.3) ruby depends on
But I also have the error about indexes on Riddle in production
(but not development)
using config file
indexing index 'documentary_core'...
ERROR: index 'documentary_core': sql_range_query: ERROR: syntax
error at or near ","
LINE 1: ...entaries"."title", "documentaries"."description", , ,
(DSN=pgsql://hzciydhmkw:***@127.0.0.1:10314/hzciydhmkw). total 0
docs, 0 bytes
total 0.121 sec, 0 bytes/sec, 0.00 docs/sec
skipping non-plain index 'documentary'...
total 0 reads, 0.000 sec, 0.0 kb/call avg, 0.0 msec/call avg
total 0 writes, 0.000 sec, 0.0 kb/call avg, 0.0 msec/call avg
From the index logs
It worked in development (ts:index) ... fs:index gave memory
allocation error but seemed to run fine in production:
[production][~/code/planet-documentary] heroku run rake cron
Running rake cron attached to terminal... up, run.7
Starting Index Request
Index Request has completed.