Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rails_panel/meta_request blocks better_errors and binding_of_caller from displaying #76

Open
JezC opened this issue Jul 26, 2014 · 1 comment
Assignees

Comments

@JezC
Copy link

JezC commented Jul 26, 2014

Hi, I'm seeing that BetterErrors and more important BindingOfCaller, are not having their right hand panels when I have the Chrome JS inspector open, and the gem 'meta_request' present and RailsPanel installed.

Latest Chrome 36.0.1985.126 (ChromeBook)
RailsPanel 0.2.1
meta_requests 0.3.3
binding_of_caller 0.7.2
better_errors 1.1.0
Ruby 1.9.3 p547
Rails 4.1.4

The test case that I'm using is to deny access to the database in a freshly installed Rails 4.1.4. Definitely raises an error, that one. ;)

If I have all enabled and the Developer Tools open, then I can't see the right panels and the REPL.

If I comment out meta_request - it works

If I close the Developer Tools pane - it works

When Chrome Dev Tools is open, with RailsPanel, and meta_request, then BetterErrors and BindingOfCaller don't appear.

I haven't tried removing RailsPanel itself... Because the issue appears to be tied to interaction with meta_request. No meta_request, no problem with RailsPanel (other than no data, of course).

Happy to push a repo of my test case - https://github.com/JezC/RailsPanelBlocksBetterErrors. I have a basic Rails 4.1.4 project, Ruby 1.9.3p547, running on Nitrous. I know one shouldn't run BetterErrors on public facing servers, so I use a passworded SSL connection for development, and I've opened up the ports on that assumption...

My basic holy trinity of better_errors/binding_of_caller/railspanel is wonderful for developing and investigating. What else can I do to help resolve this?

@dejan
Copy link
Owner

dejan commented Jul 27, 2014

Thanks for the demo of the issue. I'll investigate.

@dejan dejan self-assigned this Jul 27, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants