Upgraded to Rails 5 Development Mode Gives Production Error Page

13 views
Skip to first unread message

Allen

unread,
Jul 23, 2016, 3:47:10 PM7/23/16
to Ruby on Rails: Talk
I recently tried to upgrade a rails 4.2 app to Rails 5, but had a weird problem where whenever I ran bin/rails s and tried to make a request, the page would show the default "Something went wrong" and the development.log just showed that I accessed the page and nothing else. any ideas on how to debug what's wrong?

Hassan Schroeder

unread,
Jul 24, 2016, 10:30:20 AM7/24/16
to rubyonrails-talk
I would expect to see failing tests -- how good is your test coverage?

And if the answer is "uh, well..." then go back to the 4.2 version and
write some, at least for the area that you're seeing issues with :-)

--
Hassan Schroeder ------------------------ hassan.s...@gmail.com
http://about.me/hassanschroeder
twitter: @hassan
Consulting Availability : Silicon Valley or remote

Allen Wyma

unread,
Jul 24, 2016, 10:33:14 AM7/24/16
to rubyonrails-talk
Hi Hassan,

Test coverage is quite low as its just pulling data from an API source. I'll fix up the test coverage in a bit. Since the development logs don't say much you think I can find the answer in the test environment?

Thanks,
Allen
--
You received this message because you are subscribed to a topic in the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/rubyonrails-talk/frTPK5GC1EY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to rubyonrails-ta...@googlegroups.com.
To post to this group, send email to rubyonra...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/CACmC4yBLZoEftvVsKQDwLpNEE8OwP8c2uD6i1Uqvwm0yuMG20w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Colin Law

unread,
Jul 24, 2016, 10:49:48 AM7/24/16
to Ruby on Rails: Talk
Literally nothing else?

Can you post that bit of the log? Also the the o/p from the terminal
window running the server, from server startup to the request.

Colin

Colin

>
> --
> You received this message because you are subscribed to the Google Groups
> "Ruby on Rails: Talk" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to rubyonrails-ta...@googlegroups.com.
> To post to this group, send email to rubyonra...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/rubyonrails-talk/f8a4904c-b78e-4254-b04d-fd6cde3ac449%40googlegroups.com.

Hassan Schroeder

unread,
Jul 24, 2016, 10:50:34 AM7/24/16
to rubyonrails-talk
On Sun, Jul 24, 2016 at 7:32 AM, Allen Wyma <allen...@gmail.com> wrote:

> Test coverage is quite low as its just pulling data from an API source. I'll
> fix up the test coverage in a bit. Since the development logs don't say much
> you think I can find the answer in the test environment?

Having full test coverage of that area will, at the very least, speed
up the process of elimination :-)

Allen Wyma

unread,
Jul 24, 2016, 12:50:42 PM7/24/16
to rubyonrails-talk
Well ain’t that a B… just tried to update again, and this time it seems to be working? hmm… Next time I’ll try to put everything down for you guys in a gist. It was like 4am at that time, so wasn’t thinking clearly. That also may have been the problem. :)

--
You received this message because you are subscribed to a topic in the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/rubyonrails-talk/frTPK5GC1EY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to rubyonrails-ta...@googlegroups.com.
To post to this group, send email to rubyonra...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages