如何获得“应用程序跟踪”？而不是在Rails中进行详细的回溯？ [英] How to get "Application Trace" instead of full verbose backtrace in Rails?

问题描述

在开发环境的Rails默认错误页面中，您可以查看三个回溯，即1.应用程序跟踪，2。框架跟踪和3.完整跟踪。

In Rails default error page of development environment, you can view three backtraces, 1. Application Trace, 2. Framework Trace and 3. Full Trace.

但是如何我可以在Rails控制器中获得应用程序跟踪。完全跟踪（exception.backtrace）对我来说太多了。
现在我是这样的：

But how can I get "Application Trace" in Rails controllers. Full Trace (exception.backtrace) is too much for me. Now I'm doing like this:

exception.backtrace.select {|line| line =~ /myappname/i }

这是正确的方法吗？还是有其他更酷的方法来获取它？

Is this a correct way? Or are there other cooler ways to get it?

推荐答案

我查看了rails源代码以了解其实现方式。 ActionSupport 具有类 BacktraceCleaner ，我想这是可以自我描述的。使用Rails会将过滤器添加到回溯中：在 ActionDispatch :: ExceptionWrapper 中：

I looked up rails sources to see how it is implemented. ActionSupport has class BacktraceCleaner, which is self describable I guess. Using it Rails adds filters to backtraces: in ActionDispatch::ExceptionWrapper :

def application_trace
  clean_backtrace(:silent)
end

def framework_trace
  clean_backtrace(:noise)
end

def full_trace
  clean_backtrace(:all)
end

clean_backtrace 原来是在 BacktraceCleaner 实例上调用 clean 方法（适用于 Rails.backtrace_cleaner ），然后仅应用过滤器。您可以阅读 rails / active_support / lib / active_support / backtrace_cleaner.rb 了解其实现方式，我向您保证，它非常简单。

clean_backtrace turns out to be calling clean method on instance of BacktraceCleaner (available for users in Rails.backtrace_cleaner), which, in turn, just applies filters. You can read rails/active_support/lib/active_support/backtrace_cleaner.rb to see how it is implemented, I can assure you it's very simple.

用于应用程序回溯的实际过滤器在 railties / lib / rails / backtrace_cleaner.rb 中定义：

Actual filters for application backtrace are defined in railties/lib/rails/backtrace_cleaner.rb:

module Rails
  class BacktraceCleaner < ActiveSupport::BacktraceCleaner
    APP_DIRS_PATTERN = /^\/?(app|config|lib|test)/
    RENDER_TEMPLATE_PATTERN = /:in `_render_template_\w*'/

    def initialize
      super
      add_filter   { |line| line.sub("#{Rails.root}/", '') }
      add_filter   { |line| line.sub(RENDER_TEMPLATE_PATTERN, '') }
      add_filter   { |line| line.sub('./', '/') } # for tests

      add_gem_filters
      add_silencer { |line| line !~ APP_DIRS_PATTERN }
    end

    private
      def add_gem_filters
        gems_paths = (Gem.path | [Gem.default_dir]).map { |p| Regexp.escape(p) }
        return if gems_paths.empty?

        gems_regexp = %r{(#{gems_paths.join('|')})/gems/([^/]+)-([\w.]+)/(.*)}
        add_filter { |line| line.sub(gems_regexp, '\2 (\3) \4') }
      end
  end
end

然后 add_silencer ，检查 APP_DIRS_PATTERN = / ^ \ /？（app | config | lib | test）/ 告诉我们您非常接近:)不要被过滤器所迷惑：它们只是剪切文件的完整路径。

And add_silencer, checking for APP_DIRS_PATTERN = /^\/?(app|config|lib|test)/ tells us that you was pretty much close :) don't be confused by filters: they just cut full path to files.

很遗憾，我建议您对作业使用 Rails.backtrace_cleaner 。您正在寻找的一种更酷的方式

Having sad that, I suggest you use Rails.backtrace_cleaner for the job. It is cooler way that you are looking for

这篇关于如何获得“应用程序跟踪”？而不是在Rails中进行详细的回溯？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！