Rails 5.0.1 has been released • Hacker News Board

Re: Rails 5.0.1 has been released

#11

Post by Haydos585x2 » Wed, Dec 21, 2016, 6:20 AM UTC

sfilargi wrote: post #9

jph wrote: post #6

TLDR: Definitely worth upgrading. Approximately hundreds of small bug fixes, across much of Rails. The fixes include some important ones for database types, time comparisons, thread issues, record reloading, etc. IMHO these fixes address dozens of bugs that could cause major puzzlement for a typical Rails developer. Thanks to all the contributors for excellent work on this release.

> IMHO these fixes address dozens of bugs that could cause major puzzlement for a typical Rails developer. That has been the reason I always avoid huge frameworks like RoR. If I was to hit a bug like this, I wouldn't know where to start debugging. How do people deal with obscure bugs in the framework with something like RoR?

They probably do it with all the spare time they have from using a framework to handle so many other features.

Re: Rails 5.0.1 has been released

#12

Post by Sivart13 » Wed, Dec 21, 2016, 6:24 AM UTC

If anyone's been holding off on upgrading to 5.x because of the deprecation warnings you get about requiring `params` as w keyword argument in keyword tests, I wrote a gem that could help: https://github.com/tjgrathwell/rails5-spec-converter

Re: Rails 5.0.1 has been released

#13

Post by faitswulff » Wed, Dec 21, 2016, 6:25 AM UTC

avitzurel wrote: post #8

jph wrote: post #6

TLDR: Definitely worth upgrading. Approximately hundreds of small bug fixes, across much of Rails. The fixes include some important ones for database types, time comparisons, thread issues, record reloading, etc. IMHO these fixes address dozens of bugs that could cause major puzzlement for a typical Rails developer. Thanks to all the contributors for excellent work on this release.

One of the best (or worst) bugs fixed was the aborted transaction for PGsql. I am pretty sure hundreds of Rails developers are battling it every day and don't understand where it's coming from. Even if you don't upgrade, this is something you should backport using a monkeypatch.

I think that might be a 5.0.0 change, not a 5.0.1 change, if you're referring to:

> Restore aborted transaction state when disable_referential_integrity fails due to missing permissions.

Re: Rails 5.0.1 has been released

#14

Post by sfilargi » Wed, Dec 21, 2016, 6:27 AM UTC

Haydos585x2 wrote: post #11

sfilargi wrote: post #9

Earlier quoted context omitted.

> IMHO these fixes address dozens of bugs that could cause major puzzlement for a typical Rails developer. That has been the reason I always avoid huge frameworks like RoR. If I was to hit a bug like this, I wouldn't know where to start debugging. How do people deal with obscure bugs in the framework with something like RoR?

They probably do it with all the spare time they have from using a framework to handle so many other features.

If you are lucky enough to hit it during development or testing, then yes, fair point.

If you hit however in production and only under load or some corner cases, it must be a real bitch to try to debug code that you haven't wrote yourself.

But since my original post is being seen as a troll, I think I will just shut-up and go hide under a rock or something. :D

Re: Rails 5.0.1 has been released

#15

Post by flukus » Wed, Dec 21, 2016, 6:33 AM UTC

jph wrote: post #6

TLDR: Definitely worth upgrading. Approximately hundreds of small bug fixes, across much of Rails. The fixes include some important ones for database types, time comparisons, thread issues, record reloading, etc. IMHO these fixes address dozens of bugs that could cause major puzzlement for a typical Rails developer. Thanks to all the contributors for excellent work on this release.

> Approximately hundreds of small bug fixes, across much of Rails

Bugs from 5.0.0 or from 4.whatever? If it's the latter then bug fixes should be going there, not in a new major release.

Re: Rails 5.0.1 has been released

#16

Post by reitanqild » Wed, Dec 21, 2016, 6:42 AM UTC

sfilargi wrote: post #14

Haydos585x2 wrote: post #11

Earlier quoted context omitted.

They probably do it with all the spare time they have from using a framework to handle so many other features.

If you are lucky enough to hit it during development or testing, then yes, fair point. If you hit however in production and only under load or some corner cases, it must be a real bitch to try to debug code that you haven't wrote yourself. But since my original post is being seen as a troll, I think I will just shut-up and go hide under a rock or something. :D

Definitely not a troll I think. I guess downvoted because of disagreement.

I'll also try to explain why:

A few weeks later I have forgotten the specifics about my own code as well.

Also: often there are fewer bugs in library code.

And: getting help (paid or through stackoverflow) is probably easier.

Re: Rails 5.0.1 has been released

#17

Post by Exuma » Wed, Dec 21, 2016, 6:43 AM UTC

avitzurel wrote: post #8

jph wrote: post #6

TLDR: Definitely worth upgrading. Approximately hundreds of small bug fixes, across much of Rails. The fixes include some important ones for database types, time comparisons, thread issues, record reloading, etc. IMHO these fixes address dozens of bugs that could cause major puzzlement for a typical Rails developer. Thanks to all the contributors for excellent work on this release.

One of the best (or worst) bugs fixed was the aborted transaction for PGsql. I am pretty sure hundreds of Rails developers are battling it every day and don't understand where it's coming from. Even if you don't upgrade, this is something you should backport using a monkeypatch.

Do you have a link to that?

Re: Rails 5.0.1 has been released

#18

Post by Exuma » Wed, Dec 21, 2016, 6:46 AM UTC

seanp2k2 wrote: post #10

avitzurel wrote: post #8

Earlier quoted context omitted.

One of the best (or worst) bugs fixed was the aborted transaction for PGsql. I am pretty sure hundreds of Rails developers are battling it every day and don't understand where it's coming from. Even if you don't upgrade, this is something you should backport using a monkeypatch.

Do you have a link to the bug or the fix? We've seen this in prod for sure.

Can you explain more what you saw? What fails, and how does it fail? Does it raise an exception and the transaction undoes all queries, or does a query 'half execute' and save a dirty state to the DB?

Re: Rails 5.0.1 has been released

#19

Post by sfilargi » Wed, Dec 21, 2016, 6:52 AM UTC

reitanqild wrote: post #16

sfilargi wrote: post #14

Earlier quoted context omitted.

If you are lucky enough to hit it during development or testing, then yes, fair point. If you hit however in production and only under load or some corner cases, it must be a real bitch to try to debug code that you haven't wrote yourself. But since my original post is being seen as a troll, I think I will just shut-up and go hide under a rock or something. :D

Definitely not a troll I think. I guess downvoted because of disagreement. I'll also try to explain why: A few weeks later I have forgotten the specifics about my own code as well. Also: often there are fewer bugs in library code. And: getting help (paid or through stackoverflow) is probably easier.

> I guess downvoted because of disagreement.

Fair enough :D

> A few weeks later I have forgotten the specifics about my own code as well.

> Also: often there are fewer bugs in library code.

> And: getting help (paid or through stackoverflow) is probably easier.

I can definitely see your point, especially about being easier to get help. I imagine if you are anything other than a one man shop, you will be in much better position debugging Rails or Django, rather than trying to figure out the mess you ex-employee left.

Re: Rails 5.0.1 has been released

#20

Post by mmanfrin » Wed, Dec 21, 2016, 6:55 AM UTC

sfilargi wrote: post #9

jph wrote: post #6

TLDR: Definitely worth upgrading. Approximately hundreds of small bug fixes, across much of Rails. The fixes include some important ones for database types, time comparisons, thread issues, record reloading, etc. IMHO these fixes address dozens of bugs that could cause major puzzlement for a typical Rails developer. Thanks to all the contributors for excellent work on this release.

> IMHO these fixes address dozens of bugs that could cause major puzzlement for a typical Rails developer. That has been the reason I always avoid huge frameworks like RoR. If I was to hit a bug like this, I wouldn't know where to start debugging. How do people deal with obscure bugs in the framework with something like RoR?

These are bugs from the 5.0.0 release. I can't really think of a time where Rails itself cause issues in my day-to-day (other than missing a timezone which was something I could easily fix).