Thanks for the quick fix. Is working good in my tests and now able to use the 
new features =)

On May 15, 2011, at 1:29 AM, Pat Allan wrote:

> Okay, edge riddle on Github now supports 2.0.1/2.0.2 - the problem was I had 
> two ints around the wrong way. Silly mistake, but didn't realise 2.0.2 was 
> around.
> 
> Will get a new gem release out soon.
> 
> -- 
> Pat
> 
> On 13/05/2011, at 12:31 PM, Pat Allan wrote:
> 
>> Ah, I'll give 2.0.2 a try - thanks for pointing that out Curtis, and good to 
>> know switching back to 1.10 keeps everything working smoothly as well.
>> 
>> Expect patches soon.
>> 
>> -- 
>> Pat
>> 
>> On 13/05/2011, at 12:25 PM, Curtis Hatter wrote:
>> 
>>> If you're developing on a Mac then it'll segfault when you start up 
>>> searchd. You can download the trunk from googlecode (it's 2.0.2):
>>> 
>>> svn co http://sphinxsearch.googlecode.com/svn/trunk sphinxsearch-read-only
>>> 
>>> It'll start like it's supposed to on Mac but still get the same issues 
>>> (after changing auto_version.rb to look for /2.0.\d/.
>>> 
>>> Here's my define_index:
>>> 
>>> define_index do
>>> indexes parties
>>> indexes content
>>> end
>>> 
>>> I've had it more complex with facets before but stripped it down as much as 
>>> possible to try and make it work.
>>> 
>>> I had to do, version: "1.10" (added in quotes), in my yaml but yes doing 
>>> that allowed it to work for me.
>>> 
>>> Thanks,
>>> Curtis
>>> 
>>> On May 12, 2011, at 7:27 PM, Pat Allan wrote:
>>> 
>>>> Can everyone let me know what version of Sphinx they're using, and what 
>>>> their define_index block looks like? I'll do my best to reproduce it then 
>>>> fix it.
>>>> 
>>>> Paul, can you try downgrading to 1.10-beta? I can't actually get 2.0.1 
>>>> working on my machine, so that may actually be the problem (since I can't 
>>>> test against it properly):
>>>> http://sphinxsearch.com/forum/view.html?id=7496
>>>> 
>>>> -- 
>>>> Pat
>>>> 
>>>> On 13/05/2011, at 7:25 AM, Paul wrote:
>>>> 
>>>>> I to am getting this error under Rails 3.0.7 / TW 2.0.4 / Riddle
>>>>> 1.3.2 / Sphinx 2.0.1-beta.  Performing CLI searches using the "search"
>>>>> tool return results with no issue (it appears to be an issue within
>>>>> Riddle, but I haven't figured out what yet).
>>>>> 
>>>>> Running the following right at the console:
>>>>> client = Riddle::Client.new
>>>>> client.match_mode = :extended
>>>>> client.query "keyword" gets:
>>>>> 
>>>>> Riddle::ResponseError: searchd error (status: 1): bad multi-query
>>>>> count 0 (must be in 1..32 range)
>>>>>   from /usr/local/lib/ruby/gems/1.8/gems/riddle-1.3.2/lib/riddle/
>>>>> client.rb:663:in `request'
>>>>>   from /usr/local/lib/ruby/gems/1.8/gems/riddle-1.3.2/lib/riddle/
>>>>> client.rb:226:in `run'
>>>>>   from /usr/local/lib/ruby/gems/1.8/gems/riddle-1.3.2/lib/riddle/
>>>>> client.rb:333:in `query'
>>>>> 
>>>>> Is there a missing parameter somewhere that is causing a multi-query
>>>>> count of 0 (I'm trying to migrate from Ferret, so I'm not all that
>>>>> familiar with Sphinx yet)
>>>>> 
>>>>> 
>>>>> On May 12, 11:03 am, Curtis Hatter <[email protected]>
>>>>> wrote:
>>>>>> I get the same stacktrace as well. This is with TS 2.0.4 and Riddle 
>>>>>> 1.3.2.  I also tried using the master branch of Riddle using the 
>>>>>> following:
>>>>>> 
>>>>>> gem 'riddle',
>>>>>> :git => 'git://github.com/freelancing-god/riddle.git',
>>>>>> :branch => 'master'
>>>>>> 
>>>>>> gem 'thinking-sphinx',
>>>>>> :git => 'git://github.com/freelancing-god/thinking-sphinx.git',
>>>>>> :branch => 'rails3'
>>>>>> 
>>>>>> That didn't work either.
>>>>>> 
>>>>>> Thanks,
>>>>>> Curtis
>>>>>> 
>>>>>> On May 12, 2011, at 10:35 AM, ka8725 wrote:
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>>> I have same problems:
>>>>>>> Riddle::ResponseError: searchd error (status: 1): badmulti-query
>>>>>>> count 0 (must be in 1..32 range)
>>>>>>>    from /home/andrey/projects/indeal/vendor/bundler/ruby/1.8/gems/
>>>>>>> riddle-1.3.2/lib/riddle/client.rb:663:in `request'
>>>>>>>    from /home/andrey/projects/indeal/vendor/bundler/ruby/1.8/gems/
>>>>>>> riddle-1.3.2/lib/riddle/client.rb:226:in `run'
>>>>>>>    from /home/andrey/projects/indeal/vendor/bundler/ruby/1.8/gems/
>>>>>>> riddle-1.3.2/lib/riddle/client.rb:333:in `query'
>>>>>>>    from /home/andrey/projects/indeal/vendor/bundler/ruby/1.8/gems/
>>>>>>> thinking-sphinx-1.4.5/lib/thinking_sphinx/search.rb:389:in `populate'
>>>>>>>    from /usr/lib/ruby/1.8/benchmark.rb:308:in `realtime'
>>>>>>>    from /home/andrey/projects/indeal/vendor/bundler/ruby/1.8/gems/
>>>>>>> thinking-sphinx-1.4.5/lib/thinking_sphinx/search.rb:388:in `populate'
>>>>>>>    from /home/andrey/projects/indeal/vendor/bundler/ruby/1.8/gems/
>>>>>>> thinking-sphinx-1.4.5/lib/thinking_sphinx/search.rb:540:in `call'
>>>>>>>    from /home/andrey/projects/indeal/vendor/bundler/ruby/1.8/gems/
>>>>>>> thinking-sphinx-1.4.5/lib/thinking_sphinx/search.rb:540:in
>>>>>>> `retry_on_stale_index'
>>>>>>>    from /home/andrey/projects/indeal/vendor/bundler/ruby/1.8/gems/
>>>>>>> thinking-sphinx-1.4.5/lib/thinking_sphinx/search.rb:385:in `populate'
>>>>>>>    from /home/andrey/projects/indeal/vendor/bundler/ruby/1.8/gems/
>>>>>>> thinking-sphinx-1.4.5/lib/thinking_sphinx/search.rb:167:in
>>>>>>> `method_missing'
>>>>>>>    from /usr/lib/ruby/1.8/irb.rb:310:in `output_value'
>>>>>>>    from /usr/lib/ruby/1.8/irb.rb:159:in `eval_input'
>>>>>>>    from /usr/lib/ruby/1.8/irb.rb:271:in `signal_status'
>>>>>>>    from /usr/lib/ruby/1.8/irb.rb:155:in `eval_input'
>>>>>>>    from /usr/lib/ruby/1.8/irb.rb:154:in `eval_input'
>>>>>>>    from /usr/lib/ruby/1.8/irb.rb:71:in `start'
>>>>>>>    from /usr/lib/ruby/1.8/irb.rb:70:in `catch'
>>>>>>>    from /usr/lib/ruby/1.8/irb.rb:70:in `start'
>>>>>> 
>>>>>>> On 12 май, 11:35, Pat Allan <[email protected]> wrote:
>>>>>>>> Okay, Riddle 1.3.2 is out, along with Thinking Sphinx 2.0.4 (Rails 3) 
>>>>>>>> and 1.4.5 (Rails 1 & 2). Let me know if you hit any further problems.
>>>>>> 
>>>>>>>> --
>>>>>>>> Pat
>>>>>> 
>>>>>>>> On 12/05/2011, at 6:05 PM, Pat Allan wrote:
>>>>> 
>>>>> -- 
>>>>> You received this message because you are subscribed to the Google Groups 
>>>>> "Thinking Sphinx" group.
>>>>> To post to this group, send email to [email protected].
>>>>> To unsubscribe from this group, send email to 
>>>>> [email protected].
>>>>> For more options, visit this group at 
>>>>> http://groups.google.com/group/thinking-sphinx?hl=en.
>>>>> 
>>>> 
>>>> -- 
>>>> You received this message because you are subscribed to the Google Groups 
>>>> "Thinking Sphinx" group.
>>>> To post to this group, send email to [email protected].
>>>> To unsubscribe from this group, send email to 
>>>> [email protected].
>>>> For more options, visit this group at 
>>>> http://groups.google.com/group/thinking-sphinx?hl=en.
>>>> 
>>> 
>>> -- 
>>> You received this message because you are subscribed to the Google Groups 
>>> "Thinking Sphinx" group.
>>> To post to this group, send email to [email protected].
>>> To unsubscribe from this group, send email to 
>>> [email protected].
>>> For more options, visit this group at 
>>> http://groups.google.com/group/thinking-sphinx?hl=en.
>>> 
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Thinking Sphinx" group.
>> To post to this group, send email to [email protected].
>> To unsubscribe from this group, send email to 
>> [email protected].
>> For more options, visit this group at 
>> http://groups.google.com/group/thinking-sphinx?hl=en.
>> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Thinking Sphinx" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to 
> [email protected].
> For more options, visit this group at 
> http://groups.google.com/group/thinking-sphinx?hl=en.
> 

-- 
You received this message because you are subscribed to the Google Groups 
"Thinking Sphinx" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/thinking-sphinx?hl=en.

Reply via email to