Just a quick update - the reproduction steps I was given last night was to do 
with running TS via Merb. Same bug, but as far as I can tell, not quite the 
same cause.

I'm currently trying to reproduce the issue with Rails 2.1.2, but no luck as 
yet... whether it be in production or development (and I'm quite certain that's 
the reason for the bug on ubuntu for Forrest - it's a production environment 
issue, and most likely related to cached_classes being set to true).

If anyone can reproduce it on any version of Rails locally, I'd love to know 
how you did it - a test app or instructions would be fantastic. I'll spend some 
more time tomorrow night looking into it.

-- 
Pat

On 20/12/2009, at 2:16 PM, peter wrote:

> Thanks Pat. Hope we can get to bottom of this one.
> 
> On Dec 18, 11:42 pm, Pat Allan <[email protected]> wrote:
>> I've had someone create an issue on GitHub listing how I can reproduce the 
>> issue - I'll try to spend some time on this tonight, see if I can determine 
>> the cause and figure out a fix.
>> 
>> --
>> Pat
> 
> --
> 
> 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