Sam's Profile

yes, please do. sqlite + pg means sqlite is not profiled

Can you try using latest, I think I sorted this out

All those who were having trouble, can you test again on 0.1.8, quite a few important fixes there

do you happen to have the mysql gem as well in your gem file?

yeah, that is not going to work, you are going to need to pull the whole tree

can you try the latest from github to see if it fixes it?

at the moment there is no support for rack 1.2.5, I am going to see what is involved in backporting

yes, please do, with any relevant logs!

it should work on both, are you whitelisting your requests?

I need to figure out a way to backport some of this to rack 1.2.5, at the moment it depends on a later rack

I have this working on 3.0.14 here, perhaps your version of rack is old, have you tried updating it?

one thing that sticks out is that I did not do much 1.9.1 testing, also is there something about http authentication that you have configured in prd but not in dev?

Interesting, what version of rails/ruby are you running, is there anything in the logs about the failure? Do you mind posting on http://community.miniprofiler.com

I think the core of it was in maintaining the client side code, the server side was re-written pretty much with some similar paradigms

can you post a screen shot at http://community.miniprofiler.com ideally with the type of failure (is it a 404 or 500, what is in the error?)

interesting, @clay what version of the pg gem are your running? We are forced to monkey patch the async version of pg exec, perhaps we should fall back to the non async ones as well

what version of rails/ruby are you running?

what version of rails/ruby are you running?

@dup2, have not tested 3.0.14, will test it out and reply on the community tracker.

Others, will try to respond to all the requests here today, but it would be mighty handy if you can post bugs/questions at http://community.miniprofiler.com

Big thanks Ryan, for the excellent Railscast!