forked from e621ng/e621ng
33013e0a44
Rails is VERY opaque about which query timed out when reviewing backtraces for code that loads relations. Often it becomes difficult to tell exactly which query was generated. This interrogates the exceptions for these and pulls out the SQL and bind params for further debugging. Automatic unwrapping of rails template exceptions is done, as a majority of these seem to be triggered in production by relations that are lazily loaded through templates, or template code. Also I cleaned up the backtrace display a little bit while I was messing with this code. Usually it isn't relevant to see the 130 lines of rails relationship loader code. Full traces are still saved so that in the event something happens inside a gem/framework file it can still be easily located. |
||
|---|---|---|
| .. | ||
| active_record_api_extensions.rb | ||
| application_controller_renderer.rb | ||
| backtrace_silencers.rb | ||
| cache_store.rb | ||
| content_security_policy.rb | ||
| cookies_serializer.rb | ||
| core_extensions.rb | ||
| cors.rb | ||
| delayed_jobs.rb | ||
| elasticsearch.rb | ||
| ffmpeg.rb | ||
| filter_parameter_logging.rb | ||
| inflections.rb | ||
| mailgun.rb | ||
| mechanize_patch.rb | ||
| mime_types.rb | ||
| new_framework_defaults_6_0.rb | ||
| new_framework_defaults_6_1.rb | ||
| permissions_policy.rb | ||
| rakismet.rb | ||
| recaptcha.rb | ||
| secret_token.rb | ||
| serialization_method.rb | ||
| session_store.rb | ||
| sidekiq.rb | ||
| simple_form.rb | ||
| unicorn.rb | ||
| wrap_parameters.rb | ||
| z_action_mailer.rb | ||