Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>After I investigate the Rails source code, it seems like the <code>ActionDispatch::ShowExceptions</code> middleware that responsible of raising exception <code>ActionController::RoutingError</code> is missing in the test environment. Confirmed by running <code>rake middleware</code> and <code>rake middleware RAILS_ENV=test</code>.</p> <p>You can see that in <a href="https://github.com/josh/rack-mount/blob/master/lib/rack/mount/route_set.rb#L152" rel="nofollow">https://github.com/josh/rack-mount/blob/master/lib/rack/mount/route_set.rb#L152</a> it's returning <code>X-Cascade =&gt; 'pass'</code> header, and it's <code>ActionDispatch::ShowExceptions</code>'s responsibility to pick it up (in <a href="https://github.com/rails/rails/blob/master/actionpack/lib/action_dispatch/middleware/show_exceptions.rb#L52" rel="nofollow">https://github.com/rails/rails/blob/master/actionpack/lib/action_dispatch/middleware/show_exceptions.rb#L52</a>)</p> <p>So the reason you're seeing that your test case is passing because <code>rack-mount</code> is returning "Not Found" text, with status 404.</p> <hr> <p>I'll git blame people and get it fix for you. It's this conditional here: <a href="https://github.com/rails/rails/blob/master/railties/lib/rails/application.rb#L159" rel="nofollow">https://github.com/rails/rails/blob/master/railties/lib/rails/application.rb#L159</a>. If the setting is true, the error got translated right but we got error page output. If it's false, then this middleware doesn't get loaded at all. Hold on ... </p> <hr> <p><strong>Update</strong>: To clearify the previous block, you're hitting the dead end here. If you're setting <code>action_dispatch.show_exceptions</code> to <code>false</code>, you'll not get that middleware loaded, resulted in the 404 error from <code>rack-mount</code> got rendered. Whereas if you're setting <code>action_dispatch.show_exceptions</code> to <code>true</code>, that middleware will got loaded but it will rescue the error and render a nice "exception" page for you.</p>
    singulars
    1. This table or related slice is empty.
    1. PORaising route not found error
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USsikachu
    1. USsikachu
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PORaising route not found error
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COOk it's this legendary commit. https://github.com/rails/rails/commit/d898a4ba425a201827f07a5bb11c8c6bf85159b8 ... best part? It has been edited at the time frame you provided!
      singulars
      1. PO
      1. USsikachu
    2. COIt seems like that commit is supposed to make errors be raised, rather than rendered. Did it somehow do the opposite?
      singulars
      1. PO
      1. USAndy Lindeman
    3. CO@Andy so it raises the error for every other case, except for this edge case that `X-Cascade => pass` which was handled by that particular middleware. Must be something that they had overlooked.
      singulars
      1. PO
      1. USsikachu
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload