This project is archived and is in readonly mode.
periodically_call_remote in 2.3.3
Reported by phlegx | August 6th, 2009 @ 03:29 PM
I use periodically_call_remote in one of my views like that:
<%=periodically_call_remote(:url => { :action => 'check'},
:with => "'id=#{name}'")%>
I have a for loop within the view that calls
periodically_call_remote like for about 10 times.
Now in 2.3.2 all works fine and no errors do appear.
However in 2.3.3 I get three different error messages more or less
frequently. The errors happens always on different
periodically_call_remote calls and I really can't say when and on
which one it will occur.
Those are the error messages that I get (on some items on some calls):
- Expected x.rb to define X error
- A copy of XX has been removed from the module tree but is still active!
- and sometimes a database error that happens frequently!
While switching between the two versions Code remained unchanged, and as I said in 2.3.2 everything worked like a charm: no single error message.
Could this be a bug?
cheers
martin
Comments and changes to this ticket
-
Ryan Bigg June 16th, 2010 @ 11:36 PM
- State changed from “new” to “stale”
It would be helpful to know what x.rb is. It's probably a part of your code trying to load a constant which is undefined, then autoloading kicks in attempting to load a file that doesn't define that constant. Closing as stale.
-
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
<h2 style="font-size: 14px">Tickets have moved to Github</h2>
The new ticket tracker is available at <a href="https://github.com/rails/rails/issues">https://github.com/rails/rails/issues</a>
Jeremy Kemper
phlegx
Ryan Bigg