Ruby 2.3.3 released

#1

Post by lucascaton » Mon, Nov 21, 2016, 11:34 AM UTC

Re: Ruby 2.3.3 released

#2

Post by Exuma » Mon, Nov 21, 2016, 2:43 PM UTC

Random question, how is a regression like a 'no method error' possible? Don't the creators of these languages write extremely exhaustive tests? I don't know much about this, just wondering...

Re: Ruby 2.3.3 released

#3

Post by igravious » Mon, Nov 21, 2016, 3:00 PM UTC

Exuma wrote: post #2

Random question, how is a regression like a 'no method error' possible? Don't the creators of these languages write extremely exhaustive tests? I don't know much about this, just wondering...

Looks to be a corner case not covered by existing tests prior to now.

“This release contains a bug fix about Refinements and Module#prepend. The mixture use of Module#refine and Module#prepend to the same Class could cause unexpected NoMethodError. This is a regression on Ruby 2.3.2 released last week. See [Bug #12920] for details.”

Presumably it was discovered in the wild, fixed, test cases written, and that fix was pushed. Time taken: 6 days. https://www.ruby-lang.org/en/news/2016/11/15/ruby-2-3-2-rele...

[Bug #12920] https://bugs.ruby-lang.org/issues/12920

Re: Ruby 2.3.3 released

#4

Post by Exuma » Mon, Nov 21, 2016, 3:01 PM UTC

igravious wrote: post #3

Exuma wrote: post #2

Random question, how is a regression like a 'no method error' possible? Don't the creators of these languages write extremely exhaustive tests? I don't know much about this, just wondering...

Looks to be a corner case not covered by existing tests prior to now. “This release contains a bug fix about Refinements and Module#prepend. The mixture use of Module#refine and Module#prepend to the same Class could cause unexpected NoMethodError. This is a regression on Ruby 2.3.2 released last week. See [Bug #12920] for details.” Presumably it was discovered in the wild, fixed, test cases written, and that fix was…

Ok awesome, thanks for explaining!

Re: Ruby 2.3.3 released

#5

Post by greenail » Mon, Nov 21, 2016, 3:05 PM UTC

Is ruby dead? I would have expected more comments...

Re: Ruby 2.3.3 released

#6

Post by mhd » Mon, Nov 21, 2016, 3:07 PM UTC

greenail wrote: post #5

Is ruby dead? I would have expected more comments...

For a patch release?

Re: Ruby 2.3.3 released

#7

Post by xutopia » Mon, Nov 21, 2016, 3:10 PM UTC

greenail wrote: post #5

Is ruby dead? I would have expected more comments...

It's just a patch release including a fix for a minor edge case.

Re: Ruby 2.3.3 released

#8

Post by base » Mon, Nov 21, 2016, 3:17 PM UTC

greenail wrote: post #5

Is ruby dead? I would have expected more comments...

There was the 2.3.2 release 6 days ago. There is not much to say about this release.

Re: Ruby 2.3.3 released

#9

Post by saltvedt » Mon, Nov 21, 2016, 3:24 PM UTC

Exuma wrote: post #4

igravious wrote: post #3

Earlier quoted context omitted.

Looks to be a corner case not covered by existing tests prior to now. “This release contains a bug fix about Refinements and Module#prepend. The mixture use of Module#refine and Module#prepend to the same Class could cause unexpected NoMethodError. This is a regression on Ruby 2.3.2 released last week. See [Bug #12920] for details.” Presumably it was discovered in the wild, fixed, test cases written, and that fix was…

Ok awesome, thanks for explaining!

Good article explaining complexity of refinements in Ruby: http://blog.headius.com/2012/11/refining-ruby.html

Re: Ruby 2.3.3 released

#10

Post by chrisseaton » Mon, Nov 21, 2016, 3:37 PM UTC

Exuma wrote: post #2

Random question, how is a regression like a 'no method error' possible? Don't the creators of these languages write extremely exhaustive tests? I don't know much about this, just wondering...

It isn't possible to write exhaustive tests - there are an infinite number of possible program states.

Well, finite bound by the width of your pointer type, which doesn't help much.