Hi Eduardo, This looks like it could be a bug in IronRuby... or possibly the ActiveRecord adapter. That exception that is being thrown is from a Hashtable or Dictionary; a value is being inserted with an existing key. Typical Ruby code won't ever use a .NET specific type such as Hashtable or Dictionary (of course), which makes me think that this might be a bug in IronRuby... or possibly your ActiveRecord adapter (assuming it's tailor made for IronRuby).
I'd hate to make you jump through hoops, but it would be great if you could lend me a hand in figuring this one out. If you could send me a small repro, that would be great; baring that, I have some questions for you: What sort of AR adapter are you using? Could you give me the "actual" stack trace for this exception? This should do the trick: begin # ... the line of code that throws ... rescue Exception => e # use the following to get the actual .NET/System.Exception stack trace: puts e.StackTrace end Thanks, Charles On Sun, Sep 5, 2010 at 5:59 PM, Eduardo Blumenfeld <li...@ruby-forum.com>wrote: > Hi all, > > I finally solved the issue: > By calling another procedure and within that procedure do the eval, it > works perfectly. > > However, this seems to be a bug anyways... > > Regards, > > Eduardo > -- > Posted via http://www.ruby-forum.com/. > _______________________________________________ > Ironruby-core mailing list > Ironruby-core@rubyforge.org > http://rubyforge.org/mailman/listinfo/ironruby-core >
_______________________________________________ Ironruby-core mailing list Ironruby-core@rubyforge.org http://rubyforge.org/mailman/listinfo/ironruby-core
