headers
Nobuyoshi Nakada | 9 Feb 17:50
Favicon
Gravatar

[ruby-core:42460] [ruby-trunk - Feature #5992][Open] DL and fiddle should support intrinsic types, size_t, ptrdiff_t and intptr_t


Issue #5992 has been reported by Nobuyoshi Nakada.

----------------------------------------
Feature #5992: DL and fiddle should support intrinsic types, size_t, ptrdiff_t and intptr_t
https://bugs.ruby-lang.org/issues/5992

Author: Nobuyoshi Nakada
Status: Open
Priority: Normal
Assignee: Aaron Patterson
Category: ext
Target version: 2.0.0

size_t and ptrdiff_t can be resulted by built-in operators, so they should be provided as well as other
primitive types.

Also ruby often needs uintptr_t as VALUE.

Patch attached.

--

-- 
http://bugs.ruby-lang.org/
Permalink | Reply | 0 comments |
headers
Nobuyoshi Nakada | 9 Feb 16:38
Favicon
Gravatar

[ruby-core:42458] [ruby-trunk - Bug #5991][Assigned] fiddle/conversion.c ignores unsigned qualifier


Issue #5991 has been reported by Nobuyoshi Nakada.

----------------------------------------
Bug #5991: fiddle/conversion.c ignores unsigned qualifier
https://bugs.ruby-lang.org/issues/5991

Author: Nobuyoshi Nakada
Status: Assigned
Priority: Normal
Assignee: Aaron Patterson
Category: ext
Target version: 2.0.0
ruby -v: r34519

In value_to_generic(), signed_p seems to be ignored except for
TYPE_LONG, and NUM2LONG() is used even if signed_p is not set.
NUM2INT() and NUM2UINT() have different value ranges, so I
think they should be separated.

And in generic_to_value(), signed_p is ignored only for
TYPE_LONG_LONG, and I can't see any reason to make the
diffrence.

Patch is attached.

--

-- 
http://bugs.ruby-lang.org/
(Continue reading)

Permalink | Reply | 0 comments |
headers
Blair Silverberg | 9 Feb 11:10
Picon
Gravatar

[ruby-core:42456] [ruby-trunk - Bug #5990][Open] Random Segmentation Fault when running on Linux Fedora


Issue #5990 has been reported by Blair Silverberg.

----------------------------------------
Bug #5990: Random Segmentation Fault when running on Linux Fedora
https://bugs.ruby-lang.org/issues/5990

Author: Blair Silverberg
Status: Open
Priority: Normal
Assignee: 
Category: 
Target version: 
ruby -v: 1.9.2p290

I am parsing a large library of html documents with ruby mechanize/nokogiri. Randomly, I encounter a
segmentation fault.

This happens on both ruby 1.9.2 (ruby 1.9.2p290 (2011-07-09 revision 32553) [x86_64-linux]) and 1.9.3
(ruby 1.9.3p0 (2011-10-30 revision 33570) [x86_64-linux])

I am running Linux Fedora Laughlin 16 on rackspace

Linux 2.6.35.6-45.fc14.x86_64 #1 SMP Mon Oct 18 23:57:44 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux

Fedora release 14 (Laughlin)
Kernel \r on an \m (\l)

/root/code/myteam/classes/profile_page_scraper.rb:116: [BUG] Segmentation fault
ruby 1.9.2p290 (2011-07-09 revision 32553) [x86_64-linux]
(Continue reading)

Permalink | Reply | 1 comment |
headers
Yura Sokolov | 9 Feb 06:15
Picon
Gravatar

[ruby-core:42455] [ruby-trunk - Bug #5989][Open] Keyword spash is syntax error when there are no explicit keyword arguments


Issue #5989 has been reported by Yura Sokolov.

----------------------------------------
Bug #5989: Keyword spash is syntax error when there are no explicit keyword arguments
https://bugs.ruby-lang.org/issues/5989

Author: Yura Sokolov
Status: Open
Priority: Normal
Assignee: 
Category: core
Target version: 2.0.0
ruby -v: ruby 2.0.0dev (2012-02-09 trunk 34505) [i686-linux]

    $ ruby -e 'def a(a:1, **h); p h; end; a(b: 1)'
    {:b=>1}
    $ ruby -e 'def a(**h); p h; end; a(b: 1)'
    -e:1: syntax error, unexpected tPOW, expecting ')'
    def a(**h); p h; end
            ^

--

-- 
http://bugs.ruby-lang.org/
Permalink | Reply | 0 comments |
headers
Dylan Markow | 8 Feb 22:00
Picon
Gravatar

[ruby-core:42448] [ruby-trunk - Bug #5988][Open] Time class interprets "2012-02-30" as "2012-03-01"


Issue #5988 has been reported by Dylan Markow.

----------------------------------------
Bug #5988: Time class interprets "2012-02-30" as "2012-03-01"
https://bugs.ruby-lang.org/issues/5988

Author: Dylan Markow
Status: Open
Priority: Normal
Assignee: 
Category: 
Target version: 
ruby -v: ruby 2.0.0dev (2012-02-09 trunk 34499) [x86_64-darwin11.3.0]

=begin
The time class seems to accept any number from 1-31 as a valid day for any month of the year, even if the month
has less than 31 days. If the day exceeds the number of days, it just spills over into the following month;
"2012-02-30" become "2012-03-01", "2012-04-31" becomes "2012-05-01", and so on. It's not until you try
32 as a day number that you get the expected Argument Error. This happens with Time.new, Time.parse,
Time.local, Time.utc, etc.

 irb(main):002:0> RUBY_DESCRIPTION
 => "ruby 2.0.0dev (2012-02-09 trunk 34499) [x86_64-darwin11.3.0]"
 irb(main):003:0> Time.parse "2012-02-30"
 => 2012-03-01 00:00:00 -0800
 irb(main):004:0> Time.new 2012, 2, 30
 => 2012-03-01 00:00:00 -0800
 irb(main):005:0> Time.local 2012, 2, 30
 => 2012-03-01 00:00:00 -0800
(Continue reading)

Permalink | Reply | 3 comments |
headers
Hal Brodigan | 8 Feb 20:25
Picon
Gravatar

[ruby-core:42445] [ruby-trunk - Bug #5987][Open] IPAddr#initialize should display the invalid address when raising ArgumentError


Issue #5987 has been reported by Hal Brodigan.

----------------------------------------
Bug #5987: IPAddr#initialize should display the invalid address when raising ArgumentError
https://bugs.ruby-lang.org/issues/5987

Author: Hal Brodigan
Status: Open
Priority: Normal
Assignee: 
Category: core
Target version: 
ruby -v: ruby 1.9.3p0 (2011-10-30 revision 33570) [x86_64-linux]

I noticed that when IPAddr#initialize raises an ArgumentError on invalid addresses, it does not include
the offending address in the exception message. This makes debugging difficult.

--

-- 
http://bugs.ruby-lang.org/
Permalink | Reply | 1 comment |
headers
Luis Matta | 8 Feb 20:12
Picon
Favicon
Gravatar

[ruby-core:42444] [ruby-trunk - Bug #5986][Open] Segmentation Fault


Issue #5986 has been reported by Luis Matta.

----------------------------------------
Bug #5986: Segmentation Fault
https://bugs.ruby-lang.org/issues/5986

Author: Luis Matta
Status: Open
Priority: Urgent
Assignee: 
Category: core
Target version: 1.9.3
ruby -v: ruby 1.9.3p68 (2012-02-08 revision 34493) [x86_64-linux]

Simply trying to render the home page of active-admin.

I have tested this on Ubuntu 10.04 LTS 64bits, using rvm ruby 1.9.3-head (with and without "rvm pkg install
openssl"), and 1.9.2-head.
The structure: Nginx 1.0.11 (using ppa), RVM, Thin 1.3.1, Rails 3.2.1, ActiveAdmin 0.4, and stuff.
I am using SSL with a custom self-signed Certification Authority.

Thanks
(Since this broke my new production environment I have set it to Urgent - apologies if it is an abuse)

--

-- 
http://bugs.ruby-lang.org/
Permalink | Reply | 4 comments |
headers
Eric Wong | 8 Feb 20:05

[ruby-core:42443] [ruby-trunk - Bug #5985][Open] miniruby skews "make benchmark" results


Issue #5985 has been reported by Eric Wong.

----------------------------------------
Bug #5985: miniruby skews "make benchmark" results
https://bugs.ruby-lang.org/issues/5985

Author: Eric Wong
Status: Open
Priority: Low
Assignee: 
Category: build
Target version: 2.0.0
ruby -v: ruby 2.0.0dev (2012-02-08 trunk 34493) [x86_64-linux]

miniruby has fewer objects and a smaller heap than the normal "ruby",
benchmarks that are affected by GC performance is skewed heavily.
This is most noticeable with the vm3_gc benchmark using the same
Ruby revision/build but different executables (miniruby vs ruby):

$ make
$ make install
$ make benchmark-each ITEM=vm3_gc
ruby ../benchmark/driver.rb -v \
	            --executables="ruby; ./miniruby -I../lib -I. -I.ext/common  ../tool/runruby.rb --extout=.ext  --
--disable-gems" \
	            --pattern=vm3_gc --directory=../benchmark 
total: 1 trial(s) (1 trial(s) for 1 benchmark(s))
2012-02-08 18:57:12 +0000
target 0: ruby 2.0.0dev (2012-02-08 trunk 34493) [x86_64-linux]
(Continue reading)

Permalink | Reply | 0 comments |
headers
Benoit Daloze | 8 Feb 17:07
Favicon

[ruby-core:42440] [ruby-trunk - Bug #5984][Open] Pathname binread test is testing read


Issue #5984 has been reported by Benoit Daloze.

----------------------------------------
Bug #5984: Pathname binread test is testing read
https://bugs.ruby-lang.org/issues/5984

Author: Benoit Daloze
Status: Open
Priority: Normal
Assignee: 
Category: lib
Target version: 2.0.0
ruby -v: ruby 2.0.0dev (2012-01-12 trunk 34279) [x86_64-darwin10.8.0] 

Hello,

I noticed the 'binread' test in test/pathname/test_pathname.rb calls read instead of binread:

diff --git a/test/pathname/test_pathname.rb b/test/pathname/test_pathname.rb
index dcbcd49..1631403 100644
--- a/test/pathname/test_pathname.rb
+++ b/test/pathname/test_pathname.rb
@@ -710,7 +710,7 @@ class TestPathname < Test::Unit::TestCase
   def test_binread
     with_tmpchdir('rubytest-pathname') {|dir|
       open("a", "w") {|f| f.write "abc" }
-      assert_equal("abc", Pathname("a").read)
+      assert_equal("abc", Pathname("a").binread)
     }
(Continue reading)

Permalink | Reply | 0 comments |
headers
Rodrigo Rosenfeld Rosas | 8 Feb 15:28
Picon
Gravatar

[ruby-core:42438] [ruby-trunk - Feature #4172] Named arguments/parameters support


Issue #4172 has been updated by Rodrigo Rosenfeld Rosas.

I wouldn't say this was rejected, but implemented/accepted instead ;)
----------------------------------------
Feature #4172: Named arguments/parameters support
https://bugs.ruby-lang.org/issues/4172

Author: Rodrigo Rosenfeld Rosas
Status: Rejected
Priority: Low
Assignee: Yukihiro Matsumoto
Category: 
Target version: 

=begin
 It is usual in the Ruby community to use the idiom

 def method(options={})
   param1, param2 = options.values_at(:param1, :param2) # or {param1: 'default1', param2:
2}.collect{|k, v| options[k] || v }
   ...
 end

 instead of

 def method(param1, param2)
   ...
 end
(Continue reading)

Permalink | Reply | 0 comments |
headers
Eric Hodel | 8 Feb 07:38
Favicon
Gravatar

[ruby-core:42433] [ruby-trunk - Feature #707] Documentation for Enumerator chaining


Issue #707 has been updated by Eric Hodel.

Priority changed from Low to Normal

I will work on it, thank you.
----------------------------------------
Feature #707: Documentation for Enumerator chaining
https://bugs.ruby-lang.org/issues/707

Author: Brian Candler
Status: Assigned
Priority: Normal
Assignee: Eric Hodel
Category: DOC
Target version: 2.0.0

=begin
 Enumerators now support a horizontal filter/chaining pattern:

   generator.filter1 { ... }.filter2 { ... }.filter3 { ... }.consumer

 The overall pattern for a filter is:

   Enumerator.new do |y|
     source.each do |input|     # filter INPUT
       ...
       y << output              # filter OUTPUT
     end
   end
(Continue reading)

Permalink | Reply | 0 comments |

Gmane