lrdesign / logical-insight Goto Github PK

Speed tracer panel has a number of shortcomings:

The arguments to methods aren't being displayed
It stores way too much data for a reasonable app
It's initial purpose: it doesn't return the right format data for.

The actual AJAX endpoint for old connection data is missing

Rack::Bug should have Rails independant logging that everyone can get to. Should log to Rails.logger if available, but also to its own log file etc.

Maybe comment about "you wouldn't be able to access anyway"

I only see times, not the name of the actual templates. See: http://www.evernote.com/shard/s2/sh/20815967-7539-430b-93cc-18ab30165766/184297887ef9f372baf58b129e3b9881

This is under Rails 3.2.8.

Just the request number and the close button are visible on the bar.
None of the panel links are displayed.

A nil password should == no entry. You want an empty password? :password => '' - that could even be the default option, but if I set the password to nil, you shouldn't be able to get in.

Several panels instrument the application. The means for doing this should be unified. Further, the instrumentation scripts should be based on framework, and the framework to instrument should be a R::B option.

Seems to be related to delayed_job. One of my projects works fine with rack-bug, same rails version, same ruby version. This one doesn't.

NameError: uninitialized constant Syck::Syck
~/.rvm/gems/ruby-1.9.2-p290/gems/rake-0.9.2/lib/rake/ext/module.rb:36:in `const_missing'
~/.rvm/gems/ruby-1.9.2-p290/gems/activesupport-3.0.10/lib/active_support/inflector/methods.rb:124:in `block in constantize'
~/.rvm/gems/ruby-1.9.2-p290/gems/activesupport-3.0.10/lib/active_support/inflector/methods.rb:123:in `each'
~/.rvm/gems/ruby-1.9.2-p290/gems/activesupport-3.0.10/lib/active_support/inflector/methods.rb:123:in `constantize'
~/.rvm/gems/ruby-1.9.2-p290/gems/activesupport-3.0.10/lib/active_support/core_ext/string/inflections.rb:43:in `constantize'
~/.rvm/gems/ruby-1.9.2-p290/gems/delayed_job-2.1.4/lib/delayed/yaml_ext.rb:27:in `yaml_tag_read_class'
~/.rvm/rubies/ruby-1.9.2-p290/lib/ruby/1.9.1/syck.rb:135:in `transfer'
~/.rvm/rubies/ruby-1.9.2-p290/lib/ruby/1.9.1/syck.rb:135:in `node_import'
~/.rvm/rubies/ruby-1.9.2-p290/lib/ruby/1.9.1/syck.rb:135:in `load'
~/.rvm/rubies/ruby-1.9.2-p290/lib/ruby/1.9.1/syck.rb:135:in `load'
~/.rvm/gems/ruby-1.9.2-p290/bundler/gems/rack-bug-c71e943f153b/lib/rack/bug/database.rb:166:in `decode_value'
~/.rvm/gems/ruby-1.9.2-p290/bundler/gems/rack-bug-c71e943f153b/lib/rack/bug/database.rb:170:in `block in retrieve'
~/.rvm/gems/ruby-1.9.2-p290/bundler/gems/rack-bug-c71e943f153b/lib/rack/bug/database.rb:170:in `map'
~/.rvm/gems/ruby-1.9.2-p290/bundler/gems/rack-bug-c71e943f153b/lib/rack/bug/database.rb:170:in `retrieve'
~/.rvm/gems/ruby-1.9.2-p290/bundler/gems/rack-bug-c71e943f153b/lib/rack/bug/database.rb:174:in `for_request'
~/.rvm/gems/ruby-1.9.2-p290/bundler/gems/rack-bug-c71e943f153b/lib/rack/bug/database.rb:32:in `retrieve'
~/.rvm/gems/ruby-1.9.2-p290/bundler/gems/rack-bug-c71e943f153b/lib/rack/bug/panels/templates_panel.rb:50:in `heading_for_request'
headers_fragment:9:in `block in headers_fragment_locals_panels_request_id'
headers_fragment:5:in `each'
headers_fragment:5:in `headers_fragment_locals_panels_request_id'
~/.rvm/gems/ruby-1.9.2-p290/bundler/gems/rack-bug-c71e943f153b/lib/rack/bug/render.rb:20:in `render_template'
~/.rvm/gems/ruby-1.9.2-p290/bundler/gems/rack-bug-c71e943f153b/lib/rack/bug/toolbar.rb:50:in `render'
~/.rvm/gems/ruby-1.9.2-p290/bundler/gems/rack-bug-c71e943f153b/lib/rack/bug/toolbar.rb:34:in `inject_toolbar'
~/.rvm/gems/ruby-1.9.2-p290/bundler/gems/rack-bug-c71e943f153b/lib/rack/bug/toolbar.rb:20:in `call'
~/.rvm/gems/ruby-1.9.2-p290/bundler/gems/rack-bug-c71e943f153b/lib/rack/bug.rb:55:in `call'

Using Logical::Insight in a preprod env using unicorn therefore multiple processes. Our app makes two ajax calls simultaneously back to the host. when this happens at least one of the two ajax requests fails with SQLite3::BusyException (database is locked).

I've already started a SQLite DB for Tracer. That should move up to top-level, it's location should be an option, and it should be available to all panels.

Maybe maybe we should stick with the K/V with Hash fallback, but I'm not convinced.

Needs to refer to Insight::App

/rack_bug/ should route to a R::B info/config page. Included:

checkbox to enable/disable R::B.
checkboxes for panels
Any errors in current config
"You're forbidden from connecting"
[submit]

The RB toolbar will need to update via AJAX so that we can see the data related to R/R's made by AJAX on the current page.

Is it sqlite3 only or is something wrong here ?

Exiting
/usr/local/rvm/gems/ruby-1.9.3-rc1/gems/activesupport-3.1.1/lib/active_support/dependencies.rb:240:in require': cannot load such file -- sqlite3 (LoadError) from /usr/local/rvm/gems/ruby-1.9.3-rc1/gems/activesupport-3.1.1/lib/active_support/dependencies.rb:240:inblock in require'
from /usr/local/rvm/gems/ruby-1.9.3-rc1/gems/activesupport-3.1.1/lib/active_support/dependencies.rb:223:in `block in load_dependency'
from /usr/local/rvm/gems/

The RB toolbar should let us review old connections - the current "this connection" view leaves out AJAX calls. The correct approach, I think, is to let you switch the R/R you are currently viewing. Something about connections related to your browser is probably also sensible.

Instrumentation timing data needs better visualization. Something inspired by the GC-ST pillboxes would be great, but just having bars with relative lengths would be helpful. Unifying timing data would help...

insightEnabled not defined in page.