Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Rails 3.2.13 - Performance regressions and major bugs

blog.bugsnag.com

Post reply on HN
Print view View original

51–60 of 76 posts

Re: Rails 3.2.13 - Performance regressions and major bugs

#51

Post by tvongaza »

steveklabnik wrote: post #46
ChrisInEdmonton wrote: post #43

There's been a few people suggesting that, if you are bitten by a bug, you fix it and submit a pull request. That's a good idea. I did exactly this to a regression introduced in 3.2.9, complete with a unit test and a pull request against 3-2-stable and one against master. It took two months to get anyone to look at it, and while one of the two pull requests has a thumbs-up, it's still not been merged. Admittedly, thi…

I personally read every single issue and comment filed against rails/rails. I often don't comment if it's not a part of the codebase I'm not familiar with, and it's the same with merging. Can you point me to the specific ones so I can look at them again?

Pretty sure Chris is talking about: https://github.com/rails/rails/issues/8856

Re: Rails 3.2.13 - Performance regressions and major bugs

#52

Post by steveklabnik »

tvongaza wrote: post #51
steveklabnik wrote: post #46

Earlier quoted context omitted.

I personally read every single issue and comment filed against rails/rails. I often don't comment if it's not a part of the codebase I'm not familiar with, and it's the same with merging. Can you point me to the specific ones so I can look at them again?

Pretty sure Chris is talking about: https://github.com/rails/rails/issues/8856

Ah yes, ActiveRecord is one of those parts I am _not_ an expert in.

Re: Rails 3.2.13 - Performance regressions and major bugs

#54

Post by RegEx »

emidln wrote: post #36
sergiotapia wrote: post #27

Earlier quoted context omitted.

I'm a polyglot. I don't encase myself in any 1-thing. I use Mac at work, Windows at home for media and games, and Linux Mint 13 on my laptop for Ruby/Rails. I only used Linux because of Rails, but since I'm switching back (I have Visual Studio 2012 downloading as I type this), I'll have no need for Linux on my end-user machines anymore.

If you do not know your language/framework well enough to adapt it to your circumstances, you certainly are not well qualified enough with said software to list it as something you "know". This is one of the largest lies perpetuated on this site. If you know just enough of something to follow some tutorials and crank out cookie-cutter sites using Rails/Django/Asp/Grails/CodeIgniter/etc, but fail the moment you encoun…

I don't know who you are, but this comment embodies the bad side of HN. "You" is in the above comment 15+ times - it's so personally insulting and unnecessary. Belittling some stranger's worth to their team is unproductive, toxic behavior. I'm upset I can't downvote this into completely matching the site's bg color.

Re: Rails 3.2.13 - Performance regressions and major bugs

#55

Post by ChrisInEdmonton »

steveklabnik wrote: post #46
ChrisInEdmonton wrote: post #43

There's been a few people suggesting that, if you are bitten by a bug, you fix it and submit a pull request. That's a good idea. I did exactly this to a regression introduced in 3.2.9, complete with a unit test and a pull request against 3-2-stable and one against master. It took two months to get anyone to look at it, and while one of the two pull requests has a thumbs-up, it's still not been merged. Admittedly, thi…

I personally read every single issue and comment filed against rails/rails. I often don't comment if it's not a part of the codebase I'm not familiar with, and it's the same with merging. Can you point me to the specific ones so I can look at them again?

Yeah, tvongaza is correct. Admittedly, it's not a _big_ issue, and perhaps I'm going about things the wrong way. If you could tell me a better way of getting this issue fixed, I'd love to hear it. The only other time I tried, it took more than two years. Luckily, it was pretty easy to monkey-patch our own code to deal with this, once it broke our live site.

Re: Rails 3.2.13 - Performance regressions and major bugs

#56

Post by martinced »

RegEx wrote: post #54
emidln wrote: post #36

Earlier quoted context omitted.

If you do not know your language/framework well enough to adapt it to your circumstances, you certainly are not well qualified enough with said software to list it as something you "know". This is one of the largest lies perpetuated on this site. If you know just enough of something to follow some tutorials and crank out cookie-cutter sites using Rails/Django/Asp/Grails/CodeIgniter/etc, but fail the moment you encoun…

I don't know who you are, but this comment embodies the bad side of HN. "You" is in the above comment 15+ times - it's so personally insulting and unnecessary. Belittling some stranger's worth to their team is unproductive, toxic behavior. I'm upset I can't downvote this into completely matching the site's bg color.

+1 to you and -1 to the aggressive and insulting comment that prompted you to comment.

I see this a lot on HN too: people who've experience some level of success (as pg would say the first thing you learn when you get rich is that there are many levels of rich : ) and who hence think they know it all about everything and can constantly try to diminish others.

There's a lot of negativity here but, thankfully, there are also others who are here to share, educate and learn.

Re: Rails 3.2.13 - Performance regressions and major bugs

#57

Post by badgar »

jrochkind1 wrote: post #18

Okay, some of these problems are (unintended) direct side effects of the security fix bugs. Like I the one about scopes that effected Github -- github quoted [this commit]( https://github.com/rails/rails/commit/f980289fd2c1b9073a94b5... ) as introducing the bug, which is the commit meant to address CVE-2013-1854. So, okay, bugs happen, even with security fixes, I can forgive bugs. But others of those performance regr…

AFAICT Rails does point releases by just taking whatever's at head on the 3.x master branch, building a release candidate there, and iterating until nobody is reporting bugs.

This isn't a security patch - a stable branch with deliberately cherrypicked fixes - it's just a plain old "point release." And as is to be expected with Rails at this point, point releases break apps.

Re: Rails 3.2.13 - Performance regressions and major bugs

#58

Post by martinced »

I'm sure that Rails is great and powers many websites and that many devs loves it.

I'm also sure that people are working hard to fix these recent security issues and perfs issues.

But as a non-Rails dev I can tell you one thing: with all the attention that Rails got lately I'm sure I'll never be learning Ruby / Rails.

I'm into Clojure right now. Next target is Go.

Sadly all these Rails exploits do have a negative effect for Rails: I'm not saying this to criticize Rails. I'm saying this because I'm honestly 100% sure I'll never ever be doing anything serious with Rails and I know I'm not the only one in this case.

So, Rails devs, fix this and fix this rather sooner than later because every exploit is missed opportunities.

Re: Rails 3.2.13 - Performance regressions and major bugs

#59

Post by timdorr »

jrochkind1 wrote: post #18

Okay, some of these problems are (unintended) direct side effects of the security fix bugs. Like I the one about scopes that effected Github -- github quoted [this commit]( https://github.com/rails/rails/commit/f980289fd2c1b9073a94b5... ) as introducing the bug, which is the commit meant to address CVE-2013-1854. So, okay, bugs happen, even with security fixes, I can forgive bugs. But others of those performance regr…

This is a weird comparison, but they should adopt the same release policies as Drupal. Security releases are done separate from maintenance releases, even if they are released at the same time.

That allows you to provide the security releases as a separate patch file so you can apply individually. You can skip maintenance releases that cause problems but still keep things secure.

Re: Rails 3.2.13 - Performance regressions and major bugs

#60

Post by JohnBooty »

narrator wrote: post #45
eduardordm wrote: post #7

Earlier quoted context omitted.

I've been running Java and Rails since 2006 in my company (large), we use C# for a small number of desktop applications. This will come out harsh, but I'm being honest: If you are not willing to fix/adapt/improve the framework you are using, you better not be using ASP.NET also (try a google search on asp.net issues), or any framework at all. In fact, developing larger more complex software might not even be possible…

It's really nice being able to trace into the guts of hibernate, spring, etc to see what the heck is actually going on and fix it if it's broken. When I used to do Microsoft stuff, I'd run into bugs in the stack that I couldn't fix. This was enormously frustrating and time wasting. The typical advice given out by support was re-install or buy the latest upgrade. There were also a lot of deliberately imposed architect…

The open-source situation at Microsoft has really improved. Source is available for a lot of their web stack, contributions are accepted, and there are some nice open-source frameworks (like Nancy, MIT-licensed, inspired by Sinatra) that run on IIS or another Owin-compatible server these days.

I generally prefer Ruby-based things myself - this post isn't trying to sway anybody to the MS side; just wanted to give a bit of credit where it's due and perhaps a bit of news to those who haven't looked over onto that side of the fence in a long time.

Post reply on HN