gmane.comp.lang.ruby.core

[ruby-core:45218] [ruby-trunk - Feature #6478] BasicObject#class

Eregon (Benoit Daloze — 2012-05-24T19:01:03

Issue #6478 has been updated by Eregon (Benoit Daloze).


nobu (Nobuyoshi Nakada) wrote:

But that would include all methods from Kernel with the current behavior of #mix, as `mix ::Kernel` would do.
So you need to opt-out all methods:

    class Foo < BasicObject
      meths = (::Kernel.instance_methods - [:dup])
      mix ::Kernel, meths.each_with_object(dup: :dup) { |m,h| h[m] = nil }
    end

(And Foo.new.dup fails with "undefined method `initialize_dup'")


That behavior of #mix is not very intuitive I think, what do you think about:

diff --git a/class.c b/class.c
index 8e637c0..e9d7a7e 100644
--- a/class.c
+++ b/class.c
< at >< at > -769,8 +769,9 < at >< at > do_mix_method_i(st_data_t key, st_data_t value, st_data_t arg)
     st_table *aliasing = argp->aliasing;
     st_data_t old, alias;

-    if (aliasing && st_lookup(aliasing, ID2SYM(id), &alias)) {
-       if (NIL_P(alias)) return ST_CONTINUE;
+    if (aliasing) {
+       if (!st_lookup(aliasing, ID2SYM(id), &alias) || NIL_P(alias))
+           return ST_CONTINUE;
        id = rb_to_id(alias);
     }
     if (st_lookup(argp->mtbl, id, &old)) {

(and corresponding changes for the three other functions).
That is, if a Hash of methods is given, only import these methods.

----------------------------------------
Feature #6478: BasicObject#__class__
https://bugs.ruby-lang.org/issues/6478#change-26805

Author: trans (Thomas Sawyer)
Status: Feedback
Priority: Normal
Assignee: matz (Yukihiro Matsumoto)
Category: core
Target version: 2.0.0


How else is one supposed to get the class of a subclass of BasicObject?

[ruby-core:45217] [ruby-trunk - Feature #6483] parametric map

prijutme4ty (Ilya Vorontsov — 2012-05-24T18:49:30

Issue #6483 has been updated by prijutme4ty (Ilya Vorontsov).


Eregon (Benoit Daloze) wrote:

It's fine, but in version with PM it look like a hack. However if it'll be implemented in second version - I'd take my words back.
----------------------------------------
Feature #6483: parametric map
https://bugs.ruby-lang.org/issues/6483#change-26804

Author: prijutme4ty (Ilya Vorontsov)
Status: Open
Priority: Normal
Assignee: 
Category: 
Target version: 


I found very common use-case for map: map with parameters and &:meth syntax. For example:
matrix =[[1,2,3],[4,5,6]]
matrix.pmap(' ',&:join).join("\n") # => "1 2 3\n4 5 6
[1,2,3,4,5].pmap(2, &:to_s) # ['1', '10', '11', '100', '101']

[1,2,3,4,5].pmap(&:to_s) # ['1', '2, '3', '4', '5'] # empty parameter list behaves as usual map

Isn't it much better than ugly and verbose code: 
matrix.map{|line| line.join(' ')}.join("\n")

I can write simple implementation 
class Proc
  def curry_except_self(*args)
    Proc.new{|slf| curry[slf,*args] }
  end
end

module Enumerable
  def pmap!(*args,&block)
    map! &block.curry_except_self(*args)
  end
  def pmap(*args,&block)
    dup.pmap!(*args, &block)
  end
end

Use-cases can be rewritten as tests (I can send my own unit-test if needed)


Also I've two related things to discuss.
1) First is &-syntax. Is it possible to change ruby-interpeter in such a way that &:proc could be at any place. matrix.pmap(&:join,' ') is much prettier than matrix.join(' ',&:join) What is the reason behind this restriction? And if one can remove this restriction, we'd have new nice syntax.
2) I'm not very experience in functional programming with curry etc, but it seems to me that currying proc without supplying first argument(self) can be common task when &:meth syntax is in play. If so, may be my curry_except_self(*args) also should be included in ruby.

[ruby-core:45216] [ruby-trunk - Feature #6478] BasicObject#class

nobu (Nobuyoshi Nakada — 2012-05-24T16:14:33

Issue #6478 has been updated by nobu (Nobuyoshi Nakada).


Module#mix is a feature introduced last year, but may be removed from 2.0.
----------------------------------------
Feature #6478: BasicObject#__class__
https://bugs.ruby-lang.org/issues/6478#change-26803

Author: trans (Thomas Sawyer)
Status: Feedback
Priority: Normal
Assignee: matz (Yukihiro Matsumoto)
Category: core
Target version: 2.0.0


How else is one supposed to get the class of a subclass of BasicObject?

[ruby-core:45215] Re: [ruby-trunk - Bug #6489][Open] A File instance changes its class to IO

Yusuke Endoh — 2012-05-24T15:00:26

Hello,

2012/5/24 yimutang (Joey Zhou)

FYI: The rdoc of IO#reopen says:

 *  call-seq:
 *     ios.reopen(other_IO)         -> ios
 *     ios.reopen(path, mode_str)   -> ios
 *
 *  Reassociates <em>ios</em> with the I/O stream given in
 *  <i>other_IO</i> or to a new stream opened on <i>path</i>. This may
 *  dynamically change the actual class of this stream.

[ruby-core:45214] [ruby-trunk - Bug #6489][Rejected] A File instance changes its class to IO

nobu (Nobuyoshi Nakada — 2012-05-24T14:41:33

Issue #6489 has been updated by nobu (Nobuyoshi Nakada).

Status changed from Open to Rejected

OK.
----------------------------------------
Bug #6489: A File instance changes its class to IO
https://bugs.ruby-lang.org/issues/6489#change-26799

Author: yimutang (Joey Zhou)
Status: Rejected
Priority: Normal
Assignee: 
Category: 
Target version: 
ruby -v: ruby 1.9.3p194 (2012-04-20 revision 35410) [i686-linux]


I don't know whether it is a bug, or a feature.

1.9.3p194 :001 > f = open('xxx','w')
 => #<File:xxx> 
1.9.3p194 :002 > f.class
 => File 
1.9.3p194 :003 > f.__id__
 => 80452110 
1.9.3p194 :004 > f.reopen(STDOUT)
 => #<IO:<STDOUT>> 
1.9.3p194 :005 > f.class
 => IO 
1.9.3p194 :006 > f.__id__
 => 80452110 

You see, an object(id:80452110) changes its class from File to IO.
Is it ok?

[ruby-core:45213] [ruby-trunk - Bug #6489][Open] A File instance changes its class to IO

yimutang (Joey Zhou — 2012-05-24T12:28:35

Issue #6489 has been reported by yimutang (Joey Zhou).

----------------------------------------
Bug #6489: A File instance changes its class to IO
https://bugs.ruby-lang.org/issues/6489

Author: yimutang (Joey Zhou)
Status: Open
Priority: Normal
Assignee: 
Category: 
Target version: 
ruby -v: ruby 1.9.3p194 (2012-04-20 revision 35410) [i686-linux]


I don't know whether it is a bug, or a feature.

1.9.3p194 :001 > f = open('xxx','w')
 => #<File:xxx> 
1.9.3p194 :002 > f.class
 => File 
1.9.3p194 :003 > f.__id__
 => 80452110 
1.9.3p194 :004 > f.reopen(STDOUT)
 => #<IO:<STDOUT>> 
1.9.3p194 :005 > f.class
 => IO 
1.9.3p194 :006 > f.__id__
 => 80452110 

You see, an object(id:80452110) changes its class from File to IO.
Is it ok?

[ruby-core:45212] [ruby-trunk - Feature #6483] parametric map

trans (Thomas Sawyer — 2012-05-24T11:34:50

Issue #6483 has been updated by trans (Thomas Sawyer).


FYI https://github.com/raganwald/homoiconic/blob/master/2009-09-22/anaphora.md
----------------------------------------
Feature #6483: parametric map
https://bugs.ruby-lang.org/issues/6483#change-26797

Author: prijutme4ty (Ilya Vorontsov)
Status: Open
Priority: Normal
Assignee: 
Category: 
Target version: 


I found very common use-case for map: map with parameters and &:meth syntax. For example:
matrix =[[1,2,3],[4,5,6]]
matrix.pmap(' ',&:join).join("\n") # => "1 2 3\n4 5 6
[1,2,3,4,5].pmap(2, &:to_s) # ['1', '10', '11', '100', '101']

[1,2,3,4,5].pmap(&:to_s) # ['1', '2, '3', '4', '5'] # empty parameter list behaves as usual map

Isn't it much better than ugly and verbose code: 
matrix.map{|line| line.join(' ')}.join("\n")

I can write simple implementation 
class Proc
  def curry_except_self(*args)
    Proc.new{|slf| curry[slf,*args] }
  end
end

module Enumerable
  def pmap!(*args,&block)
    map! &block.curry_except_self(*args)
  end
  def pmap(*args,&block)
    dup.pmap!(*args, &block)
  end
end

Use-cases can be rewritten as tests (I can send my own unit-test if needed)


Also I've two related things to discuss.
1) First is &-syntax. Is it possible to change ruby-interpeter in such a way that &:proc could be at any place. matrix.pmap(&:join,' ') is much prettier than matrix.join(' ',&:join) What is the reason behind this restriction? And if one can remove this restriction, we'd have new nice syntax.
2) I'm not very experience in functional programming with curry etc, but it seems to me that currying proc without supplying first argument(self) can be common task when &:meth syntax is in play. If so, may be my curry_except_self(*args) also should be included in ruby.

[ruby-core:45211] [ruby-trunk - Feature #6483] parametric map

trans (Thomas Sawyer — 2012-05-24T11:32:17

Issue #6483 has been updated by trans (Thomas Sawyer).


=begin

  p %w[12 45 32].map(&.to_i(9)).map(& * 2)

That's pretty neat. I wonder about its implementation, so basically `&` becomes a special object that returns a proc when method is called on it?

  class Ampersand < BasicObject
    def method_missing(s, *a, &b)
      ::Proc.new{ |x| x.public_send(s, *a, &b) }
    end
  end

  & = Ampersand.new

This is also interesting in that it has an appearance similar to an anaphora (default block argument):

  p %w[12 45 32].map{it.to_i(9)}.map{it * 2}

But despite appearances they are very different in nature.
=end

----------------------------------------
Feature #6483: parametric map
https://bugs.ruby-lang.org/issues/6483#change-26796

Author: prijutme4ty (Ilya Vorontsov)
Status: Open
Priority: Normal
Assignee: 
Category: 
Target version: 


I found very common use-case for map: map with parameters and &:meth syntax. For example:
matrix =[[1,2,3],[4,5,6]]
matrix.pmap(' ',&:join).join("\n") # => "1 2 3\n4 5 6
[1,2,3,4,5].pmap(2, &:to_s) # ['1', '10', '11', '100', '101']

[1,2,3,4,5].pmap(&:to_s) # ['1', '2, '3', '4', '5'] # empty parameter list behaves as usual map

Isn't it much better than ugly and verbose code: 
matrix.map{|line| line.join(' ')}.join("\n")

I can write simple implementation 
class Proc
  def curry_except_self(*args)
    Proc.new{|slf| curry[slf,*args] }
  end
end

module Enumerable
  def pmap!(*args,&block)
    map! &block.curry_except_self(*args)
  end
  def pmap(*args,&block)
    dup.pmap!(*args, &block)
  end
end

Use-cases can be rewritten as tests (I can send my own unit-test if needed)


Also I've two related things to discuss.
1) First is &-syntax. Is it possible to change ruby-interpeter in such a way that &:proc could be at any place. matrix.pmap(&:join,' ') is much prettier than matrix.join(' ',&:join) What is the reason behind this restriction? And if one can remove this restriction, we'd have new nice syntax.
2) I'm not very experience in functional programming with curry etc, but it seems to me that currying proc without supplying first argument(self) can be common task when &:meth syntax is in play. If so, may be my curry_except_self(*args) also should be included in ruby.

[ruby-core:45210] [ruby-trunk - Feature #6478] BasicObject#class

trans (Thomas Sawyer — 2012-05-24T11:10:45

Issue #6478 has been updated by trans (Thomas Sawyer).


That was just one example. Here, you can look at this for more cases:

  https://github.com/rubyworks/ostruct2/blob/master/lib/ostruct2.rb

Just ctrl-f for __class__.

But what's this about "mix"? What Ruby are you running!? This is interesting, b/c I was thinking that I could use `#respond_to?` and I don't see anyway to add it to my BasicObject subclass except the "nasty" approach you demonstrated earlier.

----------------------------------------
Feature #6478: BasicObject#__class__
https://bugs.ruby-lang.org/issues/6478#change-26795

Author: trans (Thomas Sawyer)
Status: Feedback
Priority: Normal
Assignee: matz (Yukihiro Matsumoto)
Category: core
Target version: 2.0.0


How else is one supposed to get the class of a subclass of BasicObject?

[ruby-core:45209] [ruby-trunk - Feature #6483] parametric map

Eregon (Benoit Daloze — 2012-05-24T09:49:30

Issue #6483 has been updated by Eregon (Benoit Daloze).


nobu (Nobuyoshi Nakada) wrote:

For info, this is http://bugs.ruby-lang.org/issues/show/4146 (I had a hard time finding it back).

Another syntax is proposed by Koichi (from what I can understand):

    p %w[12 45 32].map(&PM.to_i(9)).map(&PM * 2)
    p %w[abc def ghi].map(&PM[1])

Which might be simplified to:

    p %w[12 45 32].map(&.to_i(9)).map(& * 2)
    p %w[abc def ghi].map(&[1])

I really like that one.
----------------------------------------
Feature #6483: parametric map
https://bugs.ruby-lang.org/issues/6483#change-26794

Author: prijutme4ty (Ilya Vorontsov)
Status: Open
Priority: Normal
Assignee: 
Category: 
Target version: 


I found very common use-case for map: map with parameters and &:meth syntax. For example:
matrix =[[1,2,3],[4,5,6]]
matrix.pmap(' ',&:join).join("\n") # => "1 2 3\n4 5 6
[1,2,3,4,5].pmap(2, &:to_s) # ['1', '10', '11', '100', '101']

[1,2,3,4,5].pmap(&:to_s) # ['1', '2, '3', '4', '5'] # empty parameter list behaves as usual map

Isn't it much better than ugly and verbose code: 
matrix.map{|line| line.join(' ')}.join("\n")

I can write simple implementation 
class Proc
  def curry_except_self(*args)
    Proc.new{|slf| curry[slf,*args] }
  end
end

module Enumerable
  def pmap!(*args,&block)
    map! &block.curry_except_self(*args)
  end
  def pmap(*args,&block)
    dup.pmap!(*args, &block)
  end
end

Use-cases can be rewritten as tests (I can send my own unit-test if needed)


Also I've two related things to discuss.
1) First is &-syntax. Is it possible to change ruby-interpeter in such a way that &:proc could be at any place. matrix.pmap(&:join,' ') is much prettier than matrix.join(' ',&:join) What is the reason behind this restriction? And if one can remove this restriction, we'd have new nice syntax.
2) I'm not very experience in functional programming with curry etc, but it seems to me that currying proc without supplying first argument(self) can be common task when &:meth syntax is in play. If so, may be my curry_except_self(*args) also should be included in ruby.

[ruby-core:45208] [ruby-trunk - Feature #6483] parametric map

prijutme4ty (Ilya Vorontsov — 2012-05-24T09:21:58

Issue #6483 has been updated by prijutme4ty (Ilya Vorontsov).


nobu (Nobuyoshi Nakada) wrote:

Really cool syntax! I didn't even thought that about such a way. Second version I wrote like that:
class Symbol
  def call(*args)
    obj=Object.new.instance_exec(self,args){|sym,params| < at >sym=sym; < at >args = params; self}
    obj.define_singleton_method :to_proc do
      < at >sym.to_proc.curry_except_self(*< at >args)
    end
    obj
  end
end
Unfortunately symbol isn't cloneable, so I used auxiliary object
In such a way one shouldn't define both tap and map and pleorth of other methods!

But first approach you suggested cannot be implemented in ruby yet. Hope sometimes ruby'll supply such a syntax! I propose it shouldn't even have parentheses for args
----------------------------------------
Feature #6483: parametric map
https://bugs.ruby-lang.org/issues/6483#change-26793

Author: prijutme4ty (Ilya Vorontsov)
Status: Open
Priority: Normal
Assignee: 
Category: 
Target version: 


I found very common use-case for map: map with parameters and &:meth syntax. For example:
matrix =[[1,2,3],[4,5,6]]
matrix.pmap(' ',&:join).join("\n") # => "1 2 3\n4 5 6
[1,2,3,4,5].pmap(2, &:to_s) # ['1', '10', '11', '100', '101']

[1,2,3,4,5].pmap(&:to_s) # ['1', '2, '3', '4', '5'] # empty parameter list behaves as usual map

Isn't it much better than ugly and verbose code: 
matrix.map{|line| line.join(' ')}.join("\n")

I can write simple implementation 
class Proc
  def curry_except_self(*args)
    Proc.new{|slf| curry[slf,*args] }
  end
end

module Enumerable
  def pmap!(*args,&block)
    map! &block.curry_except_self(*args)
  end
  def pmap(*args,&block)
    dup.pmap!(*args, &block)
  end
end

Use-cases can be rewritten as tests (I can send my own unit-test if needed)


Also I've two related things to discuss.
1) First is &-syntax. Is it possible to change ruby-interpeter in such a way that &:proc could be at any place. matrix.pmap(&:join,' ') is much prettier than matrix.join(' ',&:join) What is the reason behind this restriction? And if one can remove this restriction, we'd have new nice syntax.
2) I'm not very experience in functional programming with curry etc, but it seems to me that currying proc without supplying first argument(self) can be common task when &:meth syntax is in play. If so, may be my curry_except_self(*args) also should be included in ruby.

[ruby-core:45207] [ruby-trunk - Bug #6488][Open] String#slice example has a syntax error

amorsen (Benny Lyne Amorsen — 2012-05-24T08:39:11

Issue #6488 has been reported by amorsen (Benny Lyne Amorsen).

----------------------------------------
Bug #6488: String#slice example has a syntax error
https://bugs.ruby-lang.org/issues/6488

Author: amorsen (Benny Lyne Amorsen)
Status: Open
Priority: Normal
Assignee: 
Category: 
Target version: 1.9.3
ruby -v: ruby 1.9.3p0 (2011-10-30) [x86_64-linux]


http://www.ruby-doc.org/core-1.9.3/String.html#method-i-slice has a syntax error:

a[%r[aeiou](.)\11//]      #=> "ell"
a[%r[aeiou](.)\11//, 0]   #=> "ell"
a[%r[aeiou](.)\11//, 1]   #=> "l"
a[%r[aeiou](.)\11//, 2]   #=> nil

Oh, I have just realized that similar problems exist in the other regexp examples on the page, not just for slice.

[ruby-core:45206] [ruby-trunk - Feature #6483] parametric map

nobu (Nobuyoshi Nakada — 2012-05-24T08:13:51

Issue #6483 has been updated by nobu (Nobuyoshi Nakada).


I proposed a different approach, symbol with arguments syntax.

  (1..5).map(&:to_s(2)) #=> ['1', '10', '11', '100', '101']

And another proposed Symbol#call in the same thread, instead.

  (1..5).map(&:to_s.(2)) #=> ['1', '10', '11', '100', '101']
----------------------------------------
Feature #6483: parametric map
https://bugs.ruby-lang.org/issues/6483#change-26792

Author: prijutme4ty (Ilya Vorontsov)
Status: Open
Priority: Normal
Assignee: 
Category: 
Target version: 


I found very common use-case for map: map with parameters and &:meth syntax. For example:
matrix =[[1,2,3],[4,5,6]]
matrix.pmap(' ',&:join).join("\n") # => "1 2 3\n4 5 6
[1,2,3,4,5].pmap(2, &:to_s) # ['1', '10', '11', '100', '101']

[1,2,3,4,5].pmap(&:to_s) # ['1', '2, '3', '4', '5'] # empty parameter list behaves as usual map

Isn't it much better than ugly and verbose code: 
matrix.map{|line| line.join(' ')}.join("\n")

I can write simple implementation 
class Proc
  def curry_except_self(*args)
    Proc.new{|slf| curry[slf,*args] }
  end
end

module Enumerable
  def pmap!(*args,&block)
    map! &block.curry_except_self(*args)
  end
  def pmap(*args,&block)
    dup.pmap!(*args, &block)
  end
end

Use-cases can be rewritten as tests (I can send my own unit-test if needed)


Also I've two related things to discuss.
1) First is &-syntax. Is it possible to change ruby-interpeter in such a way that &:proc could be at any place. matrix.pmap(&:join,' ') is much prettier than matrix.join(' ',&:join) What is the reason behind this restriction? And if one can remove this restriction, we'd have new nice syntax.
2) I'm not very experience in functional programming with curry etc, but it seems to me that currying proc without supplying first argument(self) can be common task when &:meth syntax is in play. If so, may be my curry_except_self(*args) also should be included in ruby.

[ruby-core:45205] [ruby-trunk - Feature #6483] parametric map

prijutme4ty (Ilya Vorontsov — 2012-05-24T07:59:57

Issue #6483 has been updated by prijutme4ty (Ilya Vorontsov).


Also I propose similar approach for tap method.

class Object
  def ptap(*args,&block)
    tap &block.curry_except_self(*args)
  end
end

So instead of 
lines = File.read('filename.txt');
lines.delete('')
or
lines = File.read('filename.txt').tap{|x|x.delete ''}

I can use
lines = File.read('filename.txt').tap('', &:delete)
----------------------------------------
Feature #6483: parametric map
https://bugs.ruby-lang.org/issues/6483#change-26791

Author: prijutme4ty (Ilya Vorontsov)
Status: Open
Priority: Normal
Assignee: 
Category: 
Target version: 


I found very common use-case for map: map with parameters and &:meth syntax. For example:
matrix =[[1,2,3],[4,5,6]]
matrix.pmap(' ',&:join).join("\n") # => "1 2 3\n4 5 6
[1,2,3,4,5].pmap(2, &:to_s) # ['1', '10', '11', '100', '101']

[1,2,3,4,5].pmap(&:to_s) # ['1', '2, '3', '4', '5'] # empty parameter list behaves as usual map

Isn't it much better than ugly and verbose code: 
matrix.map{|line| line.join(' ')}.join("\n")

I can write simple implementation 
class Proc
  def curry_except_self(*args)
    Proc.new{|slf| curry[slf,*args] }
  end
end

module Enumerable
  def pmap!(*args,&block)
    map! &block.curry_except_self(*args)
  end
  def pmap(*args,&block)
    dup.pmap!(*args, &block)
  end
end

Use-cases can be rewritten as tests (I can send my own unit-test if needed)


Also I've two related things to discuss.
1) First is &-syntax. Is it possible to change ruby-interpeter in such a way that &:proc could be at any place. matrix.pmap(&:join,' ') is much prettier than matrix.join(' ',&:join) What is the reason behind this restriction? And if one can remove this restriction, we'd have new nice syntax.
2) I'm not very experience in functional programming with curry etc, but it seems to me that currying proc without supplying first argument(self) can be common task when &:meth syntax is in play. If so, may be my curry_except_self(*args) also should be included in ruby.

[ruby-core:45204] [ruby-trunk - Feature #6478] BasicObject#class

nobu (Nobuyoshi Nakada — 2012-05-24T05:56:14

Issue #6478 has been updated by nobu (Nobuyoshi Nakada).


Seems what you want is dup, not __class__.

  class Foo < BasicObject
    mix ::Kernel, dup: :dup, clone: :clone
  end

----------------------------------------
Feature #6478: BasicObject#__class__
https://bugs.ruby-lang.org/issues/6478#change-26790

Author: trans (Thomas Sawyer)
Status: Feedback
Priority: Normal
Assignee: matz (Yukihiro Matsumoto)
Category: core
Target version: 2.0.0


How else is one supposed to get the class of a subclass of BasicObject?

[ruby-core:45203] [ruby-trunk - Bug #6487][Open] io_strip_bom does not take in to account short files

tenderlovemaking (Aaron Patterson — 2012-05-24T01:31:56

Issue #6487 has been reported by tenderlovemaking (Aaron Patterson).

----------------------------------------
Bug #6487: io_strip_bom does not take in to account short files
https://bugs.ruby-lang.org/issues/6487

Author: tenderlovemaking (Aaron Patterson)
Status: Open
Priority: Normal
Assignee: 
Category: 
Target version: 
ruby -v: ruby 1.9.3p125 (2012-02-16 revision 34643) [x86_64-darwin11.3.0]


If a file is too short, io_strip_bom will raise an exception because it's trying to convert nil to an integer.

Here is an example:

irb(main):001:0> File.open('foo', 'wb') {}
=> nil
irb(main):002:0> File.new('foo', 'r:bom|utf-8').close
TypeError: no implicit conversion from nil to integer
from (irb):2:in `initialize'
from (irb):2:in `new'
from (irb):2
from /Users/aaron/.local/bin/irb:12:in `<main>'
irb(main):003:0>

I've attached tests, but I'm not sure the best way to fix.  It seems like a pain. :-/

[ruby-core:45202] [ruby-trunk - Bug #4413] Segmentation fault when using deliver for GMAIL SMTP

hectormalot (Dennis de Reus — 2012-05-23T15:17:37

Issue #4413 has been updated by hectormalot (Dennis de Reus).


I'm using MacPorts OpenSSL, version 1.0.1c, May 2012

$ which openssl
/opt/local/bin/openssl

$ openssl version
OpenSSL 1.0.1c 10 May 2012

$ /usr/bin/openssl version
OpenSSL 0.9.8r 8 Feb 2011

1.9.3p194 :004 > OpenSSL::OPENSSL_VERSION
 => "OpenSSL 1.0.1c 10 May 2012" 

----------------------------------------
Bug #4413: Segmentation fault when using deliver for GMAIL SMTP
https://bugs.ruby-lang.org/issues/4413#change-26784

Author: mhenrixon (Mikael Henriksson)
Status: Rejected
Priority: Normal
Assignee: sorah (Shota Fukumori)
Category: core
Target version: 1.9.2
ruby -v: ruby 1.9.2p136 (2010-12-25 revision 30365) [x86_64-darwin10.6.0]


=begin
 Hi,
 
 First of all please advise me if I make any mistakes in this post. I've done ruby and rails for about a month.
 
 On my local machine I have a problem with sending email through SMTP. Any time I create a new mail and try to send it with the method deliver it crashes. I "think" it crashes in the net/smtp class somewhere and was told in another couple of places to turn to hear since it is supposedly part of the core somehow (and maybe already fixed in some patch)
 
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/mail-2.2.15/lib/mail/core_extensions/smtp.rb:14:
 [BUG] Segmentation fault
 ruby 1.9.2p136 (2010-12-25 revision 30365) [x86_64-darwin10.6.0]
 -- control frame ----------
 c:0084 p:---- s:0442 b:0442 l:000441 d:000441 CFUNC :connect
 c:0083 p:0069 s:0439 b:0439 l:000438 d:000438 METHOD
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/mail-2.2.15/lib/mail/core_extensions/smtp.rb:14
 c:0082 p:0255 s:0434 b:0433 l:0022b0 d:0022b0 METHOD
 /Users/mhenrixon/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/net/smtp.rb:566
 c:0081 p:0047 s:0425 b:0425 l:000424 d:000424 METHOD
 /Users/mhenrixon/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/net/smtp.rb:525
 c:0080 p:0491 s:0418 b:0418 l:000417 d:000417 METHOD
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/mail-2.2.15/lib/mail/network/delivery_methods/smtp.rb:127
 c:0079 p:0031 s:0408 b:0408 l:000407 d:000407 METHOD
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/mail-2.2.15/lib/mail/message.rb:1967
 c:0078 p:0009 s:0404 b:0404 l:000380 d:000403 BLOCK
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/mail-2.2.15/lib/mail/message.rb:228
 c:0077 p:0021 s:0402 b:0402 l:000384 d:000401 BLOCK
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/actionmailer-3.0.4/lib/action_mailer/base.rb:403
 c:0076 p:0017 s:0399 b:0399 l:000389 d:000398 BLOCK
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/activesupport-3.0.4/lib/active_support/notifications.rb:52
 c:0075 p:0032 s:0397 b:0397 l:000396 d:000396 METHOD
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/activesupport-3.0.4/lib/active_support/notifications/instrumenter.rb
 c:0074 p:0036 s:0390 b:0390 l:000389 d:000389 METHOD
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/activesupport-3.0.4/lib/active_support/notifications.rb:52
 c:0073 p:0021 s:0385 b:0385 l:000384 d:000384 METHOD
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/actionmailer-3.0.4/lib/action_mailer/base.rb:401
 c:0072 p:0039 s:0381 b:0381 l:000380 d:000380 METHOD
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/mail-2.2.15/lib/mail/message.rb:228
 c:0071 p:0077 s:0378 b:0378 l:000377 d:000377 METHOD
 /Users/mhenrixon/projects/diglife_rx/app/controllers/orders_controller.rb:35
 c:0070 p:0012 s:0375 b:0375 l:000374 d:000374 METHOD
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/actionpack-3.0.4/lib/action_controller/metal/implicit_render.rb:4
 c:0069 p:0015 s:0370 b:0370 l:000369 d:000369 METHOD
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/actionpack-3.0.4/lib/abstract_controller/base.rb:150
 c:0068 p:0041 s:0365 b:0365 l:000364 d:000364 METHOD
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/actionpack-3.0.4/lib/action_controller/metal/rendering.rb:11
 c:0067 p:0012 s:0361 b:0361 l:002178 d:000360 BLOCK
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/actionpack-3.0.4/lib/abstract_controller/callbacks.rb:18
 c:0066 p:0124 s:0359 b:0359 l:000358 d:000358 METHOD
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/activesupport-3.0.4/lib/active_support/callbacks.rb:445
 c:0065 p:0113 s:0353 b:0353 l:000352 d:000352 METHOD
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/activesupport-3.0.4/lib/active_support/callbacks.rb:409
 c:0064 p:0024 s:0344 b:0344 l:000343 d:000343 METHOD
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/activesupport-3.0.4/lib/active_support/callbacks.rb:93
 c:0063 p:0015 s:0338 b:0338 l:002178 d:002178 METHOD
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/actionpack-3.0.4/lib/abstract_controller/callbacks.rb:17
 c:0062 p:0012 s:0333 b:0333 l:000314 d:000332 BLOCK
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/actionpack-3.0.4/lib/action_controller/metal/instrumentation.rb:30
 c:0061 p:0017 s:0329 b:0329 l:000319 d:000328 BLOCK
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/activesupport-3.0.4/lib/active_support/notifications.rb:52
 c:0060 p:0032 s:0327 b:0327 l:000326 d:000326 METHOD
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/activesupport-3.0.4/lib/active_support/notifications/instrumenter.rb
 c:0059 p:0036 s:0320 b:0320 l:000319 d:000319 METHOD
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/activesupport-3.0.4/lib/active_support/notifications.rb:52
 c:0058 p:0152 s:0315 b:0315 l:000314 d:000314 METHOD
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/actionpack-3.0.4/lib/action_controller/metal/instrumentation.rb:29
 c:0057 p:0012 s:0309 b:0309 l:000308 d:000308 METHOD
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/actionpack-3.0.4/lib/action_controller/metal/rescue.rb:17
 c:0056 p:0093 s:0304 b:0304 l:000303 d:000303 METHOD
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/actionpack-3.0.4/lib/abstract_controller/base.rb:119
 c:0055 p:0084 s:0298 b:0298 l:000297 d:000297 METHOD
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/actionpack-3.0.4/lib/abstract_controller/rendering.rb:41
 c:0054 p:0048 s:0293 b:0293 l:000292 d:000292 METHOD
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/actionpack-3.0.4/lib/action_controller/metal.rb:138
 c:0053 p:0086 s:0288 b:0288 l:000287 d:000287 METHOD
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/actionpack-3.0.4/lib/action_controller/metal/rack_delegation.rb:14
 c:0052 p:0030 s:0282 b:0282 l:000e78 d:000281 BLOCK
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/actionpack-3.0.4/lib/action_controller/metal.rb:178
 c:0051 p:---- s:0279 b:0279 l:000278 d:000278 FINISH
 c:0050 p:---- s:0277 b:0277 l:000276 d:000276 CFUNC :call
 c:0049 p:0022 s:0273 b:0273 l:000272 d:000272 METHOD
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/actionpack-3.0.4/lib/action_dispatch/routing/route_set.rb:62
 c:0048 p:0094 s:0267 b:0267 l:000266 d:000266 METHOD
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/actionpack-3.0.4/lib/action_dispatch/routing/route_set.rb:27
 c:0047 p:0097 s:0261 b:0261 l:000233 d:000260 BLOCK
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/rack-mount-0.6.13/lib/rack/mount/route_set.rb:148
 c:0046 p:0014 s:0255 b:0255 l:000239 d:000254 BLOCK
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/rack-mount-0.6.13/lib/rack/mount/code_generation.rb:93
 c:0045 p:0189 s:0250 b:0250 l:000249 d:000249 METHOD
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/rack-mount-0.6.13/lib/rack/mount/code_generation.rb:68
 c:0044 p:0198 s:0240 b:0240 l:000239 d:000239 METHOD
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/rack-mount-0.6.13/lib/rack/mount/code_generation.rb:92
 c:0043 p:0092 s:0234 b:0234 l:000233 d:000233 METHOD
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/rack-mount-0.6.13/lib/rack/mount/route_set.rb:139
 c:0042 p:0025 s:0228 b:0228 l:000227 d:000227 METHOD
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/actionpack-3.0.4/lib/action_dispatch/routing/route_set.rb:492
 c:0041 p:0033 s:0224 b:0224 l:000223 d:000223 METHOD
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/haml-3.0.25/lib/sass/plugin/rack.rb:41
 c:0040 p:0014 s:0220 b:0220 l:000211 d:000219 BLOCK
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/warden-1.0.3/lib/warden/manager.rb:35
 c:0039 p:---- s:0218 b:0218 l:000217 d:000217 FINISH
 c:0038 p:---- s:0216 b:0216 l:000215 d:000215 CFUNC :catch
 c:0037 p:0086 s:0212 b:0212 l:000211 d:000211 METHOD
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/warden-1.0.3/lib/warden/manager.rb:34
 c:0036 p:0015 s:0207 b:0207 l:000206 d:000206 METHOD
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/actionpack-3.0.4/lib/action_dispatch/middleware/best_standards_suppo
 c:0035 p:0093 s:0200 b:0200 l:000199 d:000199 METHOD
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/actionpack-3.0.4/lib/action_dispatch/middleware/head.rb:14
 c:0034 p:0155 s:0193 b:0193 l:000192 d:000192 METHOD
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/rack-1.2.1/lib/rack/methodoverride.rb:24
 c:0033 p:0046 s:0187 b:0187 l:000186 d:000186 METHOD
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/actionpack-3.0.4/lib/action_dispatch/middleware/params_parser.rb:21
 c:0032 p:0054 s:0182 b:0182 l:000181 d:000181 METHOD
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/actionpack-3.0.4/lib/action_dispatch/middleware/flash.rb:182
 c:0031 p:0027 s:0175 b:0175 l:000174 d:000174 METHOD
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/actionpack-3.0.4/lib/action_dispatch/middleware/session/abstract_sto
 c:0030 p:0015 s:0164 b:0164 l:000163 d:000163 METHOD
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/actionpack-3.0.4/lib/action_dispatch/middleware/cookies.rb:302
 c:0029 p:0014 s:0156 b:0156 l:001a00 d:000155 BLOCK
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/activerecord-3.0.4/lib/active_record/query_cache.rb:32
 c:0028 p:0019 s:0154 b:0154 l:000153 d:000153 METHOD
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/activerecord-3.0.4/lib/active_record/connection_adapters/abstract/qu
 c:0027 p:0051 s:0150 b:0150 l:000149 d:000149 METHOD
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/activerecord-3.0.4/lib/active_record/query_cache.rb:12
 c:0026 p:0019 s:0146 b:0146 l:001a00 d:001a00 METHOD
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/activerecord-3.0.4/lib/active_record/query_cache.rb:31
 c:0025 p:0015 s:0142 b:0142 l:000141 d:000141 METHOD
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/activerecord-3.0.4/lib/active_record/connection_adapters/abstract/co
 c:0024 p:0029 s:0138 b:0138 l:0004a0 d:000137 BLOCK
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/actionpack-3.0.4/lib/action_dispatch/middleware/callbacks.rb:46
 c:0023 p:0155 s:0136 b:0136 l:000135 d:000135 METHOD
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/activesupport-3.0.4/lib/active_support/callbacks.rb:415
 c:0022 p:0011 s:0126 b:0126 l:0004a0 d:0004a0 METHOD
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/actionpack-3.0.4/lib/action_dispatch/middleware/callbacks.rb:44
 c:0021 p:0015 s:0122 b:0122 l:000121 d:000121 METHOD
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/rack-1.2.1/lib/rack/sendfile.rb:107
 c:0020 p:0049 s:0112 b:0112 l:000111 d:000111 METHOD
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/actionpack-3.0.4/lib/action_dispatch/middleware/remote_ip.rb:48
 c:0019 p:0017 s:0108 b:0108 l:000107 d:000107 METHOD
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/actionpack-3.0.4/lib/action_dispatch/middleware/show_exceptions.rb:4
 c:0018 p:0027 s:0100 b:0100 l:000099 d:000099 METHOD
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/railties-3.0.4/lib/rails/rack/logger.rb:13
 c:0017 p:0032 s:0096 b:0096 l:000095 d:000095 METHOD
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/rack-1.2.1/lib/rack/runtime.rb:17
 c:0016 p:0052 s:0087 b:0087 l:000086 d:000086 METHOD
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/activesupport-3.0.4/lib/active_support/cache/strategy/local_cache.rb
 c:0015 p:0014 s:0083 b:0083 l:000077 d:000082 BLOCK
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/rack-1.2.1/lib/rack/lock.rb:11
 c:0014 p:0019 s:0081 b:0081 l:000080 d:000080 METHOD
 <internal:prelude>:10
 c:0013 p:0054 s:0078 b:0078 l:000077 d:000077 METHOD
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/rack-1.2.1/lib/rack/lock.rb:11
 c:0012 p:0193 s:0073 b:0073 l:000072 d:000072 METHOD
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/actionpack-3.0.4/lib/action_dispatch/middleware/static.rb:30
 c:0011 p:0032 s:0066 b:0066 l:000065 d:000065 METHOD
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/railties-3.0.4/lib/rails/application.rb:168
 c:0010 p:0021 s:0062 b:0062 l:000061 d:000061 METHOD
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/railties-3.0.4/lib/rails/application.rb:77
 c:0009 p:---- s:0057 b:0057 l:000056 d:000056 FINISH
 c:0008 p:0015 s:0055 b:0055 l:000054 d:000054 METHOD
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/railties-3.0.4/lib/rails/rack/log_tailer.rb:14
 c:0007 p:0015 s:0050 b:0050 l:000049 d:000049 METHOD
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/rack-1.2.1/lib/rack/content_length.rb:13
 c:0006 p:0338 s:0042 b:0042 l:000041 d:000041 METHOD
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/rack-1.2.1/lib/rack/handler/webrick.rb:52
 c:0005 p:0257 s:0030 b:0030 l:000029 d:000029 METHOD
 /Users/mhenrixon/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/webrick/httpserver.rb:111
 c:0004 p:0393 s:0020 b:0020 l:000019 d:000019 METHOD
 /Users/mhenrixon/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/webrick/httpserver.rb:70
 c:0003 p:0126 s:0009 b:0009 l:000e18 d:000008 BLOCK
 /Users/mhenrixon/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/webrick/server.rb:183
 c:0002 p:---- s:0004 b:0004 l:000003 d:000003 FINISH
 c:0001 p:---- s:0002 b:0002 l:000001 d:000001 TOP
 ---------------------------
 -- Ruby level backtrace information
 ----------------------------------------
 /Users/mhenrixon/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/webrick/server.rb:183:in
 `block in start_thread'
 /Users/mhenrixon/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/webrick/httpserver.rb:70:in
 `run'
 /Users/mhenrixon/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/webrick/httpserver.rb:111:in
 `service'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/rack-1.2.1/lib/rack/handler/webrick.rb:52:in
 `service'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/rack-1.2.1/lib/rack/content_length.rb:13:in
 `call'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/railties-3.0.4/lib/rails/rack/log_tailer.rb:14:in
 `call'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/railties-3.0.4/lib/rails/application.rb:77:in
 `method_missing'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/railties-3.0.4/lib/rails/application.rb:168:in
 `call'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/actionpack-3.0.4/lib/action_dispatch/middleware/static.rb:30:in
 `call'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/rack-1.2.1/lib/rack/lock.rb:11:in
 `call'
 <internal:prelude>:10:in `synchronize'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/rack-1.2.1/lib/rack/lock.rb:11:in
 `block in call'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/activesupport-3.0.4/lib/active_support/cache/strategy/local_cache.rb:72:in
 `call'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/rack-1.2.1/lib/rack/runtime.rb:17:in
 `call'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/railties-3.0.4/lib/rails/rack/logger.rb:13:in
 `call'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/actionpack-3.0.4/lib/action_dispatch/middleware/show_exceptions.rb:47:in
 `call'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/actionpack-3.0.4/lib/action_dispatch/middleware/remote_ip.rb:48:in
 `call'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/rack-1.2.1/lib/rack/sendfile.rb:107:in
 `call'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/actionpack-3.0.4/lib/action_dispatch/middleware/callbacks.rb:44:in
 `call'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/activesupport-3.0.4/lib/active_support/callbacks.rb:415:in
 `_run_call_callbacks'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/actionpack-3.0.4/lib/action_dispatch/middleware/callbacks.rb:46:in
 `block in call'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/activerecord-3.0.4/lib/active_record/connection_adapters/abstract/connection_pool.rb:354:in
 `call'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/activerecord-3.0.4/lib/active_record/query_cache.rb:31:in
 `call'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/activerecord-3.0.4/lib/active_record/query_cache.rb:12:in
 `cache'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/activerecord-3.0.4/lib/active_record/connection_adapters/abstract/query_cache.rb:28:in
 `cache'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/activerecord-3.0.4/lib/active_record/query_cache.rb:32:in
 `block in call'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/actionpack-3.0.4/lib/action_dispatch/middleware/cookies.rb:302:in
 `call'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/actionpack-3.0.4/lib/action_dispatch/middleware/session/abstract_store.rb:149:in
 `call'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/actionpack-3.0.4/lib/action_dispatch/middleware/flash.rb:182:in
 `call'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/actionpack-3.0.4/lib/action_dispatch/middleware/params_parser.rb:21:in
 `call'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/rack-1.2.1/lib/rack/methodoverride.rb:24:in
 `call'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/actionpack-3.0.4/lib/action_dispatch/middleware/head.rb:14:in
 `call'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/actionpack-3.0.4/lib/action_dispatch/middleware/best_standards_support.rb:17:in
 `call'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/warden-1.0.3/lib/warden/manager.rb:34:in
 `call'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/warden-1.0.3/lib/warden/manager.rb:34:in
 `catch'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/warden-1.0.3/lib/warden/manager.rb:35:in
 `block in call'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/haml-3.0.25/lib/sass/plugin/rack.rb:41:in
 `call'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/actionpack-3.0.4/lib/action_dispatch/routing/route_set.rb:492:in
 `call'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/rack-mount-0.6.13/lib/rack/mount/route_set.rb:139:in
 `call'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/rack-mount-0.6.13/lib/rack/mount/code_generation.rb:92:in
 `recognize'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/rack-mount-0.6.13/lib/rack/mount/code_generation.rb:68:in
 `optimized_each'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/rack-mount-0.6.13/lib/rack/mount/code_generation.rb:93:in
 `block in recognize'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/rack-mount-0.6.13/lib/rack/mount/route_set.rb:148:in
 `block in call'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/actionpack-3.0.4/lib/action_dispatch/routing/route_set.rb:27:in
 `call'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/actionpack-3.0.4/lib/action_dispatch/routing/route_set.rb:62:in
 `dispatch'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/actionpack-3.0.4/lib/action_dispatch/routing/route_set.rb:62:in
 `call'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/actionpack-3.0.4/lib/action_controller/metal.rb:178:in
 `block in action'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/actionpack-3.0.4/lib/action_controller/metal/rack_delegation.rb:14:in
 `dispatch'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/actionpack-3.0.4/lib/action_controller/metal.rb:138:in
 `dispatch'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/actionpack-3.0.4/lib/abstract_controller/rendering.rb:41:in
 `process'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/actionpack-3.0.4/lib/abstract_controller/base.rb:119:in
 `process'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/actionpack-3.0.4/lib/action_controller/metal/rescue.rb:17:in
 `process_action'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/actionpack-3.0.4/lib/action_controller/metal/instrumentation.rb:29:in
 `process_action'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/activesupport-3.0.4/lib/active_support/notifications.rb:52:in
 `instrument'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/activesupport-3.0.4/lib/active_support/notifications/instrumenter.rb:21:in
 `instrument'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/activesupport-3.0.4/lib/active_support/notifications.rb:52:in
 `block in instrument'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/actionpack-3.0.4/lib/action_controller/metal/instrumentation.rb:30:in
 `block in process_action'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/actionpack-3.0.4/lib/abstract_controller/callbacks.rb:17:in
 `process_action'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/activesupport-3.0.4/lib/active_support/callbacks.rb:93:in
 `run_callbacks'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/activesupport-3.0.4/lib/active_support/callbacks.rb:409:in
 `_run_process_action_callbacks'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/activesupport-3.0.4/lib/active_support/callbacks.rb:445:in
 `_run__2852200433127937858__process_action__2416592404725230506__callbacks'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/actionpack-3.0.4/lib/abstract_controller/callbacks.rb:18:in
 `block in process_action'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/actionpack-3.0.4/lib/action_controller/metal/rendering.rb:11:in
 `process_action'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/actionpack-3.0.4/lib/abstract_controller/base.rb:150:in
 `process_action'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/actionpack-3.0.4/lib/action_controller/metal/implicit_render.rb:4:in
 `send_action'
 /Users/mhenrixon/projects/diglife_rx/app/controllers/orders_controller.rb:35:in
 `create'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/mail-2.2.15/lib/mail/message.rb:228:in
 `deliver'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/actionmailer-3.0.4/lib/action_mailer/base.rb:401:in
 `deliver_mail'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/activesupport-3.0.4/lib/active_support/notifications.rb:52:in
 `instrument'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/activesupport-3.0.4/lib/active_support/notifications/instrumenter.rb:21:in
 `instrument'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/activesupport-3.0.4/lib/active_support/notifications.rb:52:in
 `block in instrument'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/actionmailer-3.0.4/lib/action_mailer/base.rb:403:in
 `block in deliver_mail'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/mail-2.2.15/lib/mail/message.rb:228:in
 `block in deliver'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/mail-2.2.15/lib/mail/message.rb:1967:in
 `do_delivery'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/mail-2.2.15/lib/mail/network/delivery_methods/smtp.rb:127:in
 `deliver!'
 /Users/mhenrixon/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/net/smtp.rb:525:in
 `start'
 /Users/mhenrixon/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/1.9.1/net/smtp.rb:566:in
 `do_start'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/mail-2.2.15/lib/mail/core_extensions/smtp.rb:14:in
 `tlsconnect'
 /Users/mhenrixon/.rvm/gems/ruby-1.9.2-p136< at >diglife_rx/gems/mail-2.2.15/lib/mail/core_extensions/smtp.rb:14:in
 `connect'
 -- C level backtrace information
 -------------------------------------------
 [NOTE]
 You may have encountered a bug in the Ruby interpreter or extension
 libraries.
 Bug reports are welcome.
 For details: http://www.ruby-lang.org/bugreport.html
 Abort trap
 
 I have no idea where to start looking. When this happens ruby it self
 stops working so it breaks everything.
 
 I use the exact same credentials on the production site and since that
 works I suppose the credentials bit has nothing to do with things 
 but here goes.
 
 ActionMailer::Base.smtp_settings = {
 :address => "smtp.gmail.com",
 :port => 587,
 :domain => "domain.com",
 :user_name => "us...< at >domain.com",
 :password => "xxx",
 :authentication => "plain",
 :enable_starttls_auto => true
 }
=end

[ruby-core:45201] [ruby-trunk - Bug #6484][Rejected] Segmentation fault using thin on Windows 7

luislavena (Luis Lavena — 2012-05-23T13:31:19

Issue #6484 has been updated by luislavena (Luis Lavena).

Status changed from Open to Rejected

This is a duplicate of #6352
----------------------------------------
Bug #6484: Segmentation fault using thin on Windows 7
https://bugs.ruby-lang.org/issues/6484#change-26783

Author: Froggy (Christoph Hannebauer)
Status: Rejected
Priority: Normal
Assignee: 
Category: 
Target version: 1.9.3
ruby -v: ruby 1.9.3p194 (2012-04-20) [i386-mingw32]


After cloning the git project git.js from https://github.com/danlucraft/git.js and executing rake demo, I receive a Segmentation fault. The output from stderr is attached as well as the output to the console.

I am using Windows 7, 64 Bit. I installed Ruby using the RubyInstaller 1.9.3-p194 from http://rubyinstaller.org . I have attached a list of gems I have installed. I installed those directly via gem from the server repository except eventmachine. I used the procedure described in http://snippets.aktagon.com/snippets/289-How-to-install-thin-rack-and-eventmachine-on-Windows-Cygwin to install eventmachine:

git clone git://github.com/eventmachine/eventmachine.git
cd eventmachine
rake gem
cd pkg
gem install eventmachine-1.0.0.beta.4

[ruby-core:45200] [ruby-trunk - Bug #6484] Segmentation fault using thin on Windows 7

h.shirosaki (Hiroshi Shirosaki — 2012-05-23T11:45:20

Issue #6484 has been updated by h.shirosaki (Hiroshi Shirosaki).


Please see this issue.
https://github.com/eventmachine/eventmachine/issues/319

You will solve it by commenting out line 85 of ext\project.h: #define FD_SETSIZE 1024.
----------------------------------------
Bug #6484: Segmentation fault using thin on Windows 7
https://bugs.ruby-lang.org/issues/6484#change-26782

Author: Froggy (Christoph Hannebauer)
Status: Open
Priority: Normal
Assignee: 
Category: 
Target version: 1.9.3
ruby -v: ruby 1.9.3p194 (2012-04-20) [i386-mingw32]


After cloning the git project git.js from https://github.com/danlucraft/git.js and executing rake demo, I receive a Segmentation fault. The output from stderr is attached as well as the output to the console.

I am using Windows 7, 64 Bit. I installed Ruby using the RubyInstaller 1.9.3-p194 from http://rubyinstaller.org . I have attached a list of gems I have installed. I installed those directly via gem from the server repository except eventmachine. I used the procedure described in http://snippets.aktagon.com/snippets/289-How-to-install-thin-rack-and-eventmachine-on-Windows-Cygwin to install eventmachine:

git clone git://github.com/eventmachine/eventmachine.git
cd eventmachine
rake gem
cd pkg
gem install eventmachine-1.0.0.beta.4

[ruby-core:45199] [ruby-trunk - Bug #6484][Open] Segmentation fault using thin on Windows 7

Froggy (Christoph Hannebauer — 2012-05-23T08:48:22

Issue #6484 has been reported by Froggy (Christoph Hannebauer).

----------------------------------------
Bug #6484: Segmentation fault using thin on Windows 7
https://bugs.ruby-lang.org/issues/6484

Author: Froggy (Christoph Hannebauer)
Status: Open
Priority: Normal
Assignee: 
Category: 
Target version: 1.9.3
ruby -v: ruby 1.9.3p194 (2012-04-20) [i386-mingw32]


After cloning the git project git.js from https://github.com/danlucraft/git.js and executing rake demo, I receive a Segmentation fault. The output from stderr is attached as well as the output to the console.

I am using Windows 7, 64 Bit. I installed Ruby using the RubyInstaller 1.9.3-p194 from http://rubyinstaller.org . I have attached a list of gems I have installed. I installed those directly via gem from the server repository except eventmachine. I used the procedure described in http://snippets.aktagon.com/snippets/289-How-to-install-thin-rack-and-eventmachine-on-Windows-Cygwin to install eventmachine:

git clone git://github.com/eventmachine/eventmachine.git
cd eventmachine
rake gem
cd pkg
gem install eventmachine-1.0.0.beta.4

[ruby-core:45198] [ruby-trunk - Feature #6483][Open] parametric map

prijutme4ty (Ilya Vorontsov — 2012-05-23T08:46:44

Issue #6483 has been reported by prijutme4ty (Ilya Vorontsov).

----------------------------------------
Feature #6483: parametric map
https://bugs.ruby-lang.org/issues/6483

Author: prijutme4ty (Ilya Vorontsov)
Status: Open
Priority: Normal
Assignee: 
Category: 
Target version: 


I found very common use-case for map: map with parameters and &:meth syntax. For example:
matrix =[[1,2,3],[4,5,6]]
matrix.pmap(' ',&:join).join("\n") # => "1 2 3\n4 5 6
[1,2,3,4,5].pmap(2, &:to_s) # ['1', '10', '11', '100', '101']

[1,2,3,4,5].pmap(&:to_s) # ['1', '2, '3', '4', '5'] # empty parameter list behaves as usual map

Isn't it much better than ugly and verbose code: 
matrix.map{|line| line.join(' ')}.join("\n")

I can write simple implementation 
class Proc
  def curry_except_self(*args)
    Proc.new{|slf| curry[slf,*args] }
  end
end

module Enumerable
  def pmap!(*args,&block)
    map! &block.curry_except_self(*args)
  end
  def pmap(*args,&block)
    dup.pmap!(*args, &block)
  end
end

Use-cases can be rewritten as tests (I can send my own unit-test if needed)


Also I've two related things to discuss.
1) First is &-syntax. Is it possible to change ruby-interpeter in such a way that &:proc could be at any place. matrix.pmap(&:join,' ') is much prettier than matrix.join(' ',&:join) What is the reason behind this restriction? And if one can remove this restriction, we'd have new nice syntax.
2) I'm not very experience in functional programming with curry etc, but it seems to me that currying proc without supplying first argument(self) can be common task when &:meth syntax is in play. If so, may be my curry_except_self(*args) also should be included in ruby.