Hi! Has anyone experienced that stack traces are missing when exceptions are raised in plugin code? We started having this issue when upgrading from Rails 2.1 to Rails 2.3.2. If I move the code into the application I get the stack trace back. Any ideas what could be causing this? How is Rails interfering with the the stack trace? Any pointers would be appreciated. Thanks! Peter Marklund http://marklunds.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
I can''t replicate this here - I created a dummy class in a plugin, with a method that raised an exception, then called that method in a controller method from the app. I see the stack track in the response. On Apr 3, 9:01 am, Peter Marklund <peter.markl...@gmail.com> wrote:> Hi! > Has anyone experienced that stack traces are missing when exceptions > are raised in plugin code? We started having this issue when upgrading > from Rails 2.1 to Rails 2.3.2. If I move the code into the application > I get the stack trace back. Any ideas what could be causing this? How > is Rails interfering with the the stack trace? Any pointers would be > appreciated. > > Thanks! > > Peter Marklundhttp://marklunds.com--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
Sorry, I hadn''t seen the new BackTraceCleaner class and I was enlightened by a friend about this post: http://afreshcup.com/2008/11/29/rails-23-backtrace-silencing I''m not sure cleaning out plugin backtraces is a good default setting though as others are bound to have debugging nightmares similar to mine. I have never been too bothered by long stacktraces Rails, but I suppose since this feature was introduced, a lot of people have. Cheers Peter On Apr 3, 10:01 am, Peter Marklund <peter.markl...@gmail.com> wrote:> Hi! > Has anyone experienced that stack traces are missing when exceptions > are raised in plugin code? We started having this issue when upgrading > from Rails 2.1 to Rails 2.3.2. If I move the code into the application > I get the stack trace back. Any ideas what could be causing this? How > is Rails interfering with the the stack trace? Any pointers would be > appreciated. > > Thanks! > > Peter Marklundhttp://marklunds.com--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to rubyonrails-core+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---