So extlib/pooling has nothing to with it at all the :length => (1..n) auto_validation for Model.property causes an infinite loop! The original backtrace also supports that: http://www.pastie.org/311534
I removed the offending auto_validation from the docs wiki! As a replacement for :length => (1..n) validates_within :property_name, :set => (1..n) can be used, and works just fine! thx again dkubb and bernerdschaefer for tracking this down! On Nov 11, 1:45 pm, Martin Gamsjaeger <[EMAIL PROTECTED]> wrote: > Hi all, > > Sorry for "spamming" irc, lighthouse and now the group with this > question, but I'm just not able to solve it, and it really totally > blocks my work. > > http://wm.lighthouseapp.com/projects/4819/tickets/647-100-cpu-load-fo... > > I had no need for auto_migrate! for like a month or so, and now (that > i installed merb-1.0) it just doesn't work anymore :/ I tried both > mysql and sqlite3 (with both dm-0.9.6 and dm-0.9.7) on two different > boxes. My OSX Tiger (with loads of gems installed) and a vanilla > ubuntu 8.04 vm with only ruby 1.8.6 and all necessary dependencies for > merb-1.0 (with dm-0.9.6). > > *Any* ideas highly appreciated! > > cheers > snusnu --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DataMapper" 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/datamapper?hl=en -~----------~----~----~----~------~----~------~--~---
