dejan/rails_panel

Panel not working on chrome extension 1.0.1 with the latest meta_request gem 0.8.5

Opened this issue · 4 comments

I just installed the
chrome extension 1.0.1 with the latest
meta_request gem 0.8.5.
On Chrome Browser 130
On macOS 15.1 Sequioa
VScode 1.95.2
Rails s running on 3000

Started the server with Panel open and crashed a page with error
The panel does not show any information.

I'm also running into this issue. Using rails v7.0.8.5.

For some reason, meta_request@0.8.5 isn't adding the X-Meta-Request-Version that RailsPanel uses to know that it should do its thing.

Here's a sample request with v0.8.4:

curl -I http://localhost:3000

HTTP/1.1 302 Found
Location: http://localhost:3000/users/sign_in
Content-Type: text/html; charset=utf-8
Cache-Control: no-cache
Set-Cookie: [...]
X-Meta-Request-Version: 0.8.4
X-Request-Id: 03da8c28-814f-48d8-ab64-e693cd98b2bd
X-Runtime: 0.462956
Content-Length: 0

And with v0.8.5:

curl -I http://localhost:3000

HTTP/1.1 302 Found
Location: http://localhost:3000/users/sign_in
Content-Type: text/html; charset=utf-8
Cache-Control: no-cache
Set-Cookie: [...]
X-Request-Id: 8574c1ba-4699-4c65-919d-ccb368c6dae2
X-Runtime: 0.468565
Content-Length: 0

The weird part is that the tests in the gem seem to specifically check this and they're all passing. There's probably some conflict between gems/middlewares, but I don't have time to investigate further right now.

I'll be sticking to v0.8.4 until a fix comes out or we can figure out what the conflict is and solve it.

Getting the same issue. Works with meta_request@0.8.4.

I can confirm as well. Downgrading meta_request to 0.8.4 works.

Also confirmed that downgrading meta_request to 0.8.4 shows the required headers.