Not showing in Rails 4

[abuisman]

When I include the gem in my rails app the profiler is not shown. However, the javascript is included and the div is created for the widget, but the final content is empty.

I tried adding Rack::MiniProfiler.authorize_request in a before_filter in my application controller: no dice.

I tried creating an initializer and add require: false in the gem file as described in the README: no profiler.

I am using puma, rails 4.0.1, and ruby ruby 2.0.0p247

Any tips?

[SamSaffron]

I have not seen this reported anywhere else.

Are you seeing JS errors in chrome dev tools?

[abuisman]

No nothing. I just get an empty div:

Could it be because of the bullet gem being present?

[abuisman]

I removed bullet, but it didn't change anything.

[brandonparsons]

hmmmm I also lost rack mini profiler (in production only) when I swapped from unicorn to puma. I'm not sure what else I changed, but nothing else comes to mind.

[ghost]

Same here with Rails 4 rails 4.0.0 and ruby 2.0.0p353

As suggested here, doesn't work either http://stackoverflow.com/questions/17025563/how-to-get-mini-profiler-to-start-in-rails

[brandonparsons]

I think I've tracked my issue down to a log permissions error. I haven't bothered to fix it yet though.

[JoshTGreenwood]

+1

[adiakritos]

I'm having the same issue. Doesn't work in rails 4 for me

[luka-n]

I have the same issue, have tracked it down to having oj_mimic_json in my Gemfile. Anyone else with this issue using the same gem?

[hunterboerner]

@lnovsak same here. oj_mimic_json breaks it.

[krim]

I have same issue. I have oj_mimic_json in my Gemfile. But then i removed it, problem wasn't resolved.

[arthurtalkgoal]

Same problem here. No error found in Firebug

[hakunin]

For me, removing Deflater from config/application.rb and moving it to production fixed the issue.
As suggested here:
http://stackoverflow.com/questions/17025563/how-to-get-mini-profiler-to-start-in-rails

[akshetpandey]

+1, removing oj_mimic_json and following what is mentioned about Rack::Deflater in the README solved the problem. The request for /rack-mini-profiler/result would hang the ruby process, also see my comment in #112 regarding SystemStackError

[pencilcheck]

+1, removing oj_mimic_json works. I don't get hanging of the ruby process though. Hopefully this can be fixed.

[SamSaffron]

this is all very strange can someone write a test case that fails here, somehow ojs json implementation is lacking and its hurting us here.

[akshetpandey]

The issue is that OJ doesn't handle circular reference in objects. For example:
Never mind, the normal json parser doesn't handle it either.

[pencilcheck]

Oj.default_options = {
:mode => :compat,
:use_to_json => true
}

This works for me for circular references

[SamSaffron]

before any of this can someone help isolate the circular ref, so we can remove it, we don't really need it in our persistence structure.

[DavidRagone]

I also had to both remove Deflator and oj_mimic_json to get this to work. Ruby 2.2, Rails 4.2.1

[eggie5]

+1 for removing oj_mimic_json gem.

[kevinjalbert]

Just wanted to chime in that I encountered the same issue. I had to remove the oj_mimic_json gem for this to work.

The solution that @pencilcheck suggested didn't work for me.

[jhubert]

I didn't have the oj_mimic_json gem, but removing heroku-deflator worked for me.

[thatpixguy]

We were missing the badge, and it turned out it was because we were using heroku_rails_deflate. Using heroku-deflater seems to not break the badge.

The problems seem to occur around

rack-mini-profiler/lib/mini_profiler/profiler.rb

Line 378 in f580d60

if String === body

when body turns out not to be a String.

[Ch4s3]

This still happens for me unless I remove oj_mimic_json, which I'd like to use.

[steverob]

Same issue for me. Described more at #134 (comment)

Btw, I do not use oj_mimic_json or heroku_deflator

[steverob]

@SamSaffron Here is a fresh Rails app (4.2.6 / 2.3.1) where this has been reproduced. https://github.com/steverob/miniprofiler-production-test

[dgynn]

@steverob I ran your test app and was not able to reproduce the problem. The mini profiler showed up just fine on the second request.

[steverob]

Really? :( let me check again.

Regards
Steve Robinson

On 03-Jul-2016, at 11:25 PM, Dave Gynn notifications@github.com wrote:

@steverob I ran your test app and was not able to reproduce the problem. The mini profiler showed up just fine on the second request.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

[steverob]

@dgynn yes you're right. Upon second request it shows up. No such luck for my app though. Same environment. Any ideas?

[steverob]

@dgynn sorry my bad. I did not restart server after adding the authorize_request call :(. Code reloading!!

Thanks.

[brand-it]

Here is a way to get around minprofile in development mode. If you are using the oj gem and not the oj_mimic_json which really is just a small bit of code.

oj-mimic-json-1.0.1 (lib/oj_mimic_json.rb)

require 'oj'

Oj.mimic_JSON()
# Requiring json here seems to stop conflicts when requiring json in other files.
begin
  require 'json'
rescue Exception
  # ignore
end

config/initializers/oj.rb

require 'oj'

Oj.default_options = {
  mode: :compat
}

# Should be able to remove this(Rails.env.development?) once a update comes out
# https://github.com/MiniProfiler/rack-mini-profiler/pull/250
Oj.mimic_JSON unless Rails.env.development?

Basically I am turning off the OJ system in development as it is the only time we are using to try and backtrace slow queries.

[nruth]

Disabling Rack::Deflater in development fixed things for me.

WhateverApp::Application.configure do
  config.middleware.insert_before ActionDispatch::Static, Rack::Deflater
end

Commenting that out and restarting rails s made the profiler work in development on rails 4.2.6 ruby 2.3.1 with the Gemfile-only default setup.

[nateberkopec]

Closing as stale. Linking #16.