Activity
From 02/20/2012 to 02/26/2012
02/26/2012
-
11:33 PM Feature #6012: Proc#source_location also return the column
- BTW & OT: When is any one going to explain how we format code examples as monospace text on this site?
-
- Would this effect Method#source_location too?
I'm not sure I am really digging this idea. First of all it means I have to go back and fix some code. Secondly it means I have to always worry about the additional piece of data even thou... -
06:26 PM Bug #6089 (Closed): Test suite fails with OpenSSL 1.0.1
- It seems that the patch [1] changes the behavior of openssl and makes the test_x509cert.rb fail:
1) Failure:
test_dsig_algorithm_mismatch(OpenSSL::TestX509Certificate) [test/openssl/test_x509cert.rb:175]:
OpenSSL::X509::Certificat... -
06:23 PM Feature #5958: ThreadGroup#join
- (2012/02/26 17:32), Masaki Matsushita wrote:
> I think `ThreadGroup#join` may be more useful if it catches exceptions from all its threads and handles them like the following.
> ...
This behavior is very confusing for me.
I know it... -
05:32 PM Feature #5958: ThreadGroup#join
- Koichi Sasada wrote:
> What should happen when at least one thread causes an exception?
Under the patch, joining thread also causes the exception if the thread is being joined.
Otherwise, nothing will happen on joining thread.
It b... -
05:28 PM Revision 660a3298 (git): merge revision(s) 34821:
- * regparse.c (add_code_range_to_buf0): wrong condition of duplicated
warnings.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/branches/ruby_1_9_3@34822 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
02:58 PM Bug #6058: Stack overflow in SEGV Handler
- r34817 の修正で私の手元でも直っていることを確認しました（ありがとうございます！）。
一応ご報告しておきます。 -
05:48 AM Bug #6058: Stack overflow in SEGV Handler
- ああ、思い出した。もともと buf[256] をここで使ってなかったのは
・ファイル名、行番号はスクリプト依存なので非常に長いファイル名を故意に生成可能なので二重SEGVを防ぐために上限を決める必要がある。ふつうファイル名は256程度で十分だろう
・fmt引数はRuby本体からわたされるので、長すぎるfmtがわたされたら呼び出し側のバグだろう
という意図でした。なので、256のままでいいのかちょっと自信がありません。たぶん大丈夫だと思いますが -
- workaroundとしてはこれで直りそうですが、元々のSEGVがあんまりなっとくいってないのでしばらく開き続けさせてください。ひまが出来たら追っかける
-
- This issue was solved with changeset r34817.
Narihiro, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
----------
* error.c (report_bug): use buf and snprintf to avoid consumi... -
- warnings.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34821 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
02:08 PM Bug #6066: Fix "control may reach end of non-void function" warnings for clang
- =begin
This patch updates existing (({return Qnil; /* not reached */})) with (({UNREACHABLE;}))
I did not change (({trace_en()})) in variable.c as it seems to return, I think the (({/* not reached */})) should be removed, but can you... -
- This patch updates all -Wreturn-type warning locations to use the UNREACHABLE macro.
-
- Thank you, I will post an updated patch using UNREACHABLE
-
- Eric Hodel wrote:
> If I update to (({assert_raises(EOFError, IOError, Errno::ECONNRESET) {})) may I commit?
Yes, please -
- =begin
If I update to (({assert_raises(EOFError, IOError, Errno::ECONNRESET) {})) may I commit?
=end
-
- > - assert_raises(EOFError) {
> ...
On my environment, EOFError and Errno::ECONNRESET may happen.
Others are ok. -
- Nobuyoshi Nakada wrote:
>sys/uio.hが必要です。
ご指摘とpatchをありがとうございます。
なかださんのpatchを適用して1つにまとめたpatchを添付します。 -
11:26 AM Bug #5966 (Closed): ->{} doesn't work in BasicObject
- This issue was solved with changeset r34819.
Kazuki, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
----------
* compile.c (iseq_compile_each): call on special object instead... -
- Hi,
(2012/02/11 6:56), Nobuyoshi Nakada wrote:
> File 0001-Bug-5966-lambda-in-BasicObject.patch added
> Status changed from Open to Assigned
> Assignee set to Koichi Sasada
Thank you. Please commit it.
> I'm not su... -
07:53 AM Bug #5765: [PATCH] modernize Timeout usage in net/{http,pop,smtp,telnet}
- Eric Hodel <drbrain@segment7.net> wrote:
> I like this patch.
>
> This patch will collide with #6001, though, since I introduce
> Net::HTTP::OpenTimeout as a subclass of Timeout::Error. Should we add
> Net::OpenTimeout inste... -
- The attached patch combines the original patch with the introduction of Net::OpenTimeout.
-
- I like this patch.
This patch will collide with #6001, though, since I introduce Net::HTTP::OpenTimeout as a subclass of Timeout::Error. Should we add Net::OpenTimeout instead of Net::HTTP::OpenTimeout?
See also #6088 where I intr... -
- Koichi Sasada <redmine@ruby-lang.org> wrote:
> Any progress?
Patch still applies to trunk with offsets. I was hoping somebody
else can review it (I never trust anything I write :)
> I think it is good timing that you beco... -
- The attached patch adds Net::ReadTimeout to Net::Telnet.
-
- This relates to #5765 which improves use of timeout in net/ and #6001 which introduces Net::HTTP::OpenTimeout.
This patch introduces Net::ReadTimeout as a subclass of Timeout::Error and raises it when a read operation takes too long. ... -
- I would think these methods should be using `self.class.new` for constructors thus returning the subclass. Although, that might not always possible.
-
06:02 AM Bug #6087 (Closed): How should inherited methods deal with return values of their own subclass?
- Just noticed that we still don't have a consistent way to handle return values:
```ruby
class A < Array
end
a = A.new
a.flatten.class # => A
a.rotate.class # => Array
(a * 2).class # => A
(a + a).class # => Array
```
S... -
-
- Koichi Sasada wrote:
> I want to change this behavior as permitting multiple modules in an ancestors list (option B).
> ...
That would be great.
I'm assuming it be allowed to include a module multiple times in a row too?
~~~ruby
... -
- I want to change this behavior as permitting multiple modules in an ancestors list (option B).
Can I do it? (If I can, I'll implement it after this Apr).
-
- I might have sounded more negative than I intended, so let me say that I also agree that we should allow a comma.
-
- * compile.c (iseq_compile_each): call on special object instead of
self. since stabby lambda is a syntax, so it should not be
affected by the context. [ruby-core:42349][Bug #5966]
* insns.def (send): no spe... -
- self. since stabby lambda is a syntax, so it should not be
affected by the context. [ruby-core:42349][Bug #5966]
* insns.def (send): no special deal for FCALL. self should be put
on TOS instead.
git-svn-id: svn+ssh://ci.ruby-lang... -
- @Xavier Let me "qualify" that ;-) I think your reasoning made very good sense for adding to ActiveSupport. But becoming part of Ruby, there is the opportunity to do it "right", as your last statement concurs.
-
I don't think the name is particularly obvious. Nevertheless, I am hopeful that it won't matter. I think `const_get` can accommodate. In fact, I think it can even be made to handle:
const_get('Foo', 'Bar::Baz') #=> Foo::Bar::Baz
...-
12:58 AM Feature #6065: Allow Bignum marshalling/unmarshalling from C API
- Yusuke Endoh wrote:
> I agree with akr; Martin's proposal depends on the type long, which
> ...
Having something like that would of course be pure luxury :) I really
like it because it is friendly to clients in the sense that
they c... -
- Akira Tanaka wrote:
> 2012/2/25 Martin Bosslet <Martin.Bosslet@googlemail.com>:
> ...
I meant that it would become tightly coupled without further
comment on the expected transfer format. If the internal
representation happens to...
02/25/2012
-
11:42 PM Feature #6070: The scope of for loop variables
- Hi,
> I agree with your opinion regarding the current side effect problems of
> ...
Thanks for your agreement:)
I've updated my patch, whose changes are:
* use NODE_MEMO to avoid memory leak when parsing of expr_value failed.
... -
03:23 AM Feature #6070: The scope of for loop variables - On Fri, Feb 24, 2012 at 02:25:57PM +0900, Shugo Maeda wrote:
>
> Issue #6070 has been updated by Shugo Maeda.
>
> File for_loop_scope_fix_2.diff added
>
> Hi,
>
> Shugo Maeda wrote:
> > There is at least one problem in this... -
- Could you make another ticket ans assign it to Martin Boßlet about openssl?
-
- It seems that the patch [1] changes the behavior of openssl and makes the test_x509cert.rb fail:
1) Failure:
test_dsig_algorithm_mismatch(OpenSSL::TestX509Certificate) [test/openssl/test_x509cert.rb:175]:
OpenSSL::X509::Certific... - 08:37 PM Revision 767848e0 (git): * 2012-02-26
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34818 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- [ruby-dev:45272] [Bug #6058]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34817 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34816 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- Hi,
(12/02/25 13:51), Koichi Sasada wrote:
> I think there are no reason why comma should be rejected.
It's simple.
~~~diff
diff --git a/parse.y b/parse.y
index e47dac4..f55e754 100644
--- a/parse.y
+++ b/parse.y
@@ -979,4... -
- I think there are no reason why comma should be rejected.
-
09:53 AM Feature #6074: Allow alias arguments to have a comma
- Hello,
2012/2/24 Thomas Sawyer <transfire@gmail.com>:
> Btw, is there a reason why `alias` is a keyword and not a method?
Just historical reason, I guess. A keyword-style `alias` was
first introduced, and then alias_metho... -
- Yes, I have almost exclusively used #alias_method in the past, but it's always seems rather silly to have to use the longer term. And I bet it would be an easy adjustment to support a comma.
Btw, I really dislike using the non-symbol ... -
- If that this is your biggest pet peeve, you must really love Ruby!
Just use `alias_method` instead. The `alias` keyword is more general and allows other aliases like global variables; also you don't need to give symbols to `alias`, yo... -
07:46 PM Feature #5690: Module#qualified_const_get
- I wrote qualified_const_get in Active Support. The rationale for that name was: 1) I didn't want to touch const_get. const_get is supposed to raise an exception if the argument is not a valid constant name and "Foo::Bar" is not a valid c...
-
- Please, can we avoid the use such abstract name.
Is the speed hit too great that Ruby's can't just use `#const_get` for this as well? I suspect the Rail's method name was chosen simply to avoid a monkey patch.
Of course, in Facets ... -
- (2011/11/30 12:10), Yehuda Katz wrote:
> It would be great if there was a way to dynamically load a constant path:
>
> ```ruby
> module Foo
> module Bar
> module Baz
> end
> end
> end
>
> Foo.qualifie... -
- I think it's really not such a good idea. Often you'll just end up having to redo it anyway when you finally decide to coerce and/or validate arguments to make your code more robust, e,g,
~~~ruby
def initialize(@name, @age, @location... -
- if my memory serves me right, matz dislikes such a style of arguments.
Matz, could you explain the reason again?
I know some people like this style.
-
- > Binary hackers can handle C structs even if it is a hidden private struct.
> So it should be enough simply to declare "struct RBignunm is not a public API".
I disagree. As far as we consider there is backdoor, every binary
co... -
- Binary hackers can handle C structs even if it is a hidden private struct.
So it should be enough simply to declare "struct RBignunm is not a public API". -
- Now, the struct RBignum which is a definition of Bignum in C is located in include/ruby/ruby.h. It means we can't change implementation of Bignum. For example, using GMP as Bignum representation.
I propose to move the struct RBignum... -
-
- IO objects (e.g. pipes) may have Qnil for fptr->pathv. Calling
RSTRING_PTR on Qnil is unsafe and causes a segmentation fault.
This issue also affects 1.9.3 and will need to be backported.
-
- No, the commit just checks the function, and defines UNREACHABLE macro.
-
- r34784 uses __builtin_unreachable().
-
05:38 PM Bug #5411: Some enum.c doc tweaks
- [removed]
-
- While working on the messages of "wrong number of arguments" error (see #6085), I realized that the new named parameter feature can lead to misleading error messages:
def foo(x: 42)
end
arg = {x: :bar}
foo(arg) # => nil... -
- なかだです。
(12/02/25 13:33), Masaki Matsushita wrote:
> patchを添付します。
sys/uio.hが必要です。
diff --git i/configure.in w/configure.in
index c760c53..67f5a54 100644
--- i/configure.in
+++ w/configure.in
@@ -1144,7 +1144,... -
- io.cのio_binwrite()内で、writev()を用いる事を提案します。
現在のio_binwrite()は、実際にシステムコールを呼ぶ時には渡された文字列がwbufに収まるならばMEMMOVE()で収めてしまってio_fflush()し、
収まらなければfflushした後に再度rb_write_internal()を呼んでいますが、writev()を用いる事でMEMMOVE()の必要がなくなり、
wbufと渡された文字列を結合する事なく一度のシステ... -
- Hi,
Koichi Sasada wrote:
> Any progress on it?
I'm having some problems running all tests, but here is what I've done so far.
The first patches defines various `min_max_arity` functions to get min and max number of (non-ignored... -
- Any progress on it?
-
- For brevity, let me abbreviate:
WNA = "wrong number of arguments"
Ruby could provide more accurate information when raising an ArgumentError for WNA.
Example:
def foo(a, b=42); end
foo # => WNA (0 for 1)
f... -
- 2012/2/25 Koichi Sasada <redmine@ruby-lang.org>:
> I think it is good timing that you become a committer :)
> (I'm sorry if you already are)
An enthusiastic +1.
--
Yusuke Endoh <mame@tsg.ne.jp> -
- Any progress?
I think it is good timing that you become a committer :)
(I'm sorry if you already are)
-
- Hello,
2012/2/25 Masaki Matsushita <glass.saga@gmail.com>:
> Yusuke Endoh wrote:
>> Did you run my program?
>
> Yes. I ran your program in [ruby-core:42683] and I really experienced performance improvement on my environment... -
- Yusuke Endoh wrote:
> Did you run my program?
Yes. I ran your program in [ruby-core:42683] and I really experienced performance improvement on my environment.
Results are in [ruby-core:42684] and they can be reproduced.
I'm wonde... -
- Kosaki-san, can you check [ruby-core:42772]?
Matsushita-san,
I'm not sure if the mechanism you said is right because just
using posix_fadvise did not bring any speed improvement in my
experiment of [ruby-core:42683]. Did you run m... -
- This has already done, only missed to close.
-
- Who should work on it?
-
- Could you show the small reproducible code?
-
03:05 PM Bug #6084 (Rejected): Ruby 1.9.3p125 Segfault while running nanoc compile
- Ruby interpreter segfaults with the compile command of nanoc for Ruby 1.9.3p125 under Windows. My windows version is Windows 7 Professional x64. While having checked with nanoc developer, this error does not appear on 1.9.3p0, and it is ...
-
- What should happen when at least one thread causes an exception?
-
- * file.c (utime_internal): fix a variable missed to replace.
[ruby-core:42864] [Bug #6077]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/branches/ruby_1_9_3@34815 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- This issue was solved with changeset r34800.
Nobuyoshi, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
----------
* ext/dl/dl.c (Init_dl): support intrinsic types, size_t, pt... -
03:28 AM Feature #5992: DL and fiddle should support intrinsic types, size_t, ptrdiff_t and intptr_t
- Nobu,
This looks good. Will you apply please? -
- Christopher Huff wrote:
> VALUE is actively misleading, given that a VALUE can not be constructed by the function, and the writer of the code will most likely not want to return a pre-constructed one. "void *" is the obvious choice, not... -
- Suggestions are welcome!
-
- (2011/12/07 14:26), Martin Dürst wrote:
> This is related to http://redmine.ruby-lang.org/issues/982. In terms of what needs to be done, it may even be "the same" bug, although 982 is about a very long array literal, and this is about... -
- Can you reproduce it on 1.9.3 yet?
3rd party extensions often make such a bug. -
- Shugo Maeda wrote:
> I prefer method annotations to special syntax.
Me too. Any discussion about it?
-
- * dir.c, file.c, io.c: use rb_sys_fail_path.
* error.c: new functions to deal exceptions with string instances.
* dir.c, file.c, io.c (rb_sys_fail_path): use rb_sys_fail_str.
* test/ruby/test_literal.rb (TestRu... -
- * dir.c (dir_initialize): keep path in original encoding.
* error.c (syserr_initialize): prefer the encoding of message over
locale. [ruby-dev:45279][Bug #6071]
* dir.c (dir_inspect), io.c (rb_io_inspect): ke... -
- Hi,
Shouichi KAMIYA wrote:
> Yes Scala's yield feature in for loop is powerful and it'll be good if we can use that feature in Ruby.
> ...
I think it's good to support both each and map/flat_map.
It may be possible to use yield ins... -
10:29 AM Feature #6065: Allow Bignum marshalling/unmarshalling from C API
- 2012/2/25 Martin Bosslet <Martin.Bosslet@googlemail.com>:
>
> One comment, which is also in reply to why I believe it
> could be dangerous to simply promote rb_big_(un)pack to
> public API: rhey are tightly coupled to our intern... -
- Hello,
2012/2/25 Martin Bosslet <Martin.Bosslet@googlemail.com>:
> Kenta Murata wrote:
>> I also believe it is useful that the feature to dump a Bignum to C array.
>
>> I made a patch for realizing the feature.
>> Please ... -
- Kenta Murata wrote:
> I also believe it is useful that the feature to dump a Bignum to C array.
> ...
Great, I would really appreciate that, thank you!
One comment, which is also in reply to why I believe it
could be dangerous to simply... -
09:53 AM Feature #4043: グローバル関数current_classの提案
- きしもとです
On Wed, 15 Feb 2012 18:05:12 +0900
Shyouhei Urabe <shyouhei@ruby-lang.org> wrote:
> Issue #4043 has been updated by Shyouhei Urabe.
>
>
> Makoto Kishimoto wrote:
> > 採用を妨げるものとしては何がありますでしょうか？
>
> やっぱ名前じゃないで... -
- Hello,
2012/2/25 Marc-Andre Lafortune <ruby-core@marc-andre.ca>:
> I feel there is no need for `each_sorted` as it is equivalent to `sort.each` (and 2 characters longer).
Agreed. If we can implement the feature without crea... -
- I feel there is no need for `each_sorted` as it is equivalent to `sort.each` (and 2 characters longer). Try:
{1 => 2, 0 => 4}.sort.each{|k, v| p "#{k} => #{v}"}
-
06:21 AM Feature #6079 (Rejected): Hash#each_sorted
- I often use my own mixin'd Hash#each_sorted that sorts the hash keys and then calls the block with the key and value. It would be useful to be added to Hash. (If this is already in Hash or Enumerable, I didn't see it.)
class Hash
d... -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34812 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- * lib/fileutils.rb: use chomp(?/) instead of sub to optimize and avoid
to regexping invalid string.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/branches/ruby_1_9_3@34811 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- * dir.c (dir_inspect), io.c (rb_io_inspect): keep encoding of path.
[Bug #6072]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/branches/ruby_1_9_3@34810 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- to regexping invalid string.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34809 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
08:07 AM Feature #4890: Enumerable#lazy
- Yusuke Endoh wrote:
>
> ...
Hi,
I've come up with patch in C - just two lazy methods added so far: map and select.
Please, see this PR for more info https://github.com/ruby/ruby/pull/100
The idea is very simple - block that pas... -
- but check.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34808 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34807 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- * complex.c (nucomp_marshal_load): raise error on invalid data.
reported by John Firebaugh [ruby-core:42860] [Bug #6076]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/branches/ruby_1_9_3@34806 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34805 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34804 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- reported by John Firebaugh [ruby-core:42860] [Bug #6076]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34803 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34802 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34801 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- This issue was solved with changeset r34792.
Michael, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
----------
* file.c (utime_internal): fix a variable missed to replace.
... -
04:36 AM Bug #6077 (Closed): Segmentation faults on trunk after r34788
- trunk fails to pass tests due to segmentation fauls, the issue seems to be introduced in r34788 (https://github.com/ruby/ruby/commit/adcb7e9e7b142427c97251fdb6340433f65fe811).
64-bit Linux: https://gist.github.com/7be5c691bcd7a66888d3... -
- and intptr_t. [ruby-core:42460][Feature #5992]
* ext/fiddle/fiddle.c (Init_fiddle): ditto.
* ext/dl/lib/dl/cparser.rb (DL::CParser#parse_ctype): ditto.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34800 b2dd03c8-39d4-4d8f-98ff-823... -
- (2011/08/26 2:45), Aaron Patterson wrote:
> Can we make it use a regular ivar for `path` rather than an ivar with no
> "@"? Using private ivars like this makes life hard for doing
> introspection (like the introspection required ... -
- I've reduced the diff slightly. May I commit this?
-
- =begin
Please check this improved patch.
The new patch separates open and connect errors from response read/write errors. This allows OpenSSL::SSL::SSLError to be rescued only when there is an error in the connection (from SSL_read ... -
04:37 AM Bug #6078 (Closed): The name of a module nested in an anonymous module depends on how it was created
- If a module is nested under an anonymous module, the nested modules name will depend on how the module is created. See below:
$ irb
1.9.3p125 :001 > m = Module.new
=> #<Module:0x000001009e1398>
1.9.3p125 :002 > n = Module.new
=... -
- 返事が遅くなって、ごめんなさい。
YAML のファイルフォーマットは UTF8, UTF16LE, と UTF16BE のみサポートしますが、Psych だけは String をパースする時に文字コードを UTF8 に変換します。
例： https://gist.github.com/1902995
ファイルを使用する場合、ファイルの文字例は以下の UTF8 、UTF16LE 、 UTF16BEの一つのみ使用可能です。
例：https://gis... -
- I've tried, but I can't seem to reproduce this. Christian, are you still seeing these issues? If so, could you post an application that reproduces the problem? I'm happy to do this off-list if it's more convenient.
-
- Curses::VERSION.
* ext/dbm/dbm.c (Init_dbm): ditto for DBM::VERSION.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34799 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- understandable without context.
* ext/dbm/dbm.c (Init_dbm): ditto for DBM::VERSION.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34798 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
02/24/2012
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34797 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- quoted by single quotes. [ruby-dev:45281] [Bug #6069]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34796 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- [Bug #6072]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34795 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- * error.c (syserr_initialize): prefer the encoding of message over
locale. [ruby-dev:45279][Bug #6071]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34794 b2dd03c8-39d4-4d8f-98ff-823fe69b080e - 09:55 PM Revision cc07e34b (git): * 2012-02-25
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34793 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- [ruby-core:42864] [Bug #6077]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34792 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- It seems that the errors are due to updated openssl library: openssl-1.0.1-0.1.beta2.fc17 ... there is a lot of errors around, Python, MySql ...
-
- Akira Tanaka wrote:
> 2012/2/22 Vit Ondruch <v.ondruch@tiscali.cz>:
> ...
Yes, that might be. I just noted that the "TestPathname#test_pathsubext_510" was last entry in my log, so there might be other tests passed, but not flushed yet.... -
- This is one my biggest pet peeves with Ruby. I am always typing:
~~~ruby
alias :foo, :bar
~~~
And getting a damn syntax error.
Btw, is there a reason why `alias` is a keyword and not a method?
-
03:09 PM Feature #6073: Proposal of extending syntax of for loop
- Hi,
Thank you for your quick response.
Shugo Maeda wrote:
> Scala's for expression is more powerful.
> ...
Yes Scala's yield feature in for loop is powerful and it'll be good if we can use that feature in Ruby.
However, it seems... -
- Hi,
Shouichi KAMIYA wrote:
> I propose to extend syntax of for loop which allows us to write multiple loop with guard easily.
> ...
I'm interested in your idea.
# Feature #6070 was preparation for the same proposal.
> for i in 1... -
- Oh and this is my fork on Github.
https://github.com/shouichi/ruby -
- Hi,
I propose to extend syntax of for loop which allows us to write multiple loop with guard easily.
This extension is inspired by Scala. Here is a example
for i in 1..4 when i % 2 == 0
j in 5..8 when j % 4 == 0
puts "#{i}... -
- * lib/ostruct.rb (delete_field): Bug fix so previous value is
returned. Patch by Nick Recobra [Bug #6063]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/branches/ruby_1_9_3@34791 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- Hi,
Shugo Maeda wrote:
> There is at least one problem in this patch. The problem is that it cannot handle
> ...
I've fixed my patch to fix the problem.
By the attached patch, the scope of variables in expr_value is not limited in... -
- Hi,
2012/2/24 Shugo Maeda <redmine@ruby-lang.org>:
> There is at least one problem in this patch. The problem is that it cannot handle
> the following code in mkmf.rb.
> # I suspected that this code was written by nobu, but it wa... -
- Hi,
In Ruby, the scope of a for loop variable is not limited in the for expression,
which means that a for expression counts on side effects.
This sometimes causes unexpected behavior when closing a for loop variable using a closu... -
- I think Timeout::Error is OK since Errno::ECONNRESET or Errno::ECONNABORTED may race with your timeout setting depending upon network behavior.
OpenSSL::SSL::SSLError may be raised due to a temporary issue when reading or writing and ... -
- =begin
Yes, (ID)NULL seems odd to me too.
clang supports __builtin_unreachable():
http://clang.llvm.org/docs/LanguageExtensions.html#__builtin_unreachable
It looks like replacing (({return Qnil; /* NOT REACHED */})) lines with ... - 09:25 AM Revision d77f31b6 (git): * test/zlib/test_zlib.rb (TestZlibGzipReader#test_encoding): Add
- encoding testcases for GzipReader#read. read() emits
Encoding.default_external in contrast to read(size) emits BINARY.
See also: http://bugs.jruby.org/6208
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34790 b2dd03c8-39d4-4d8f... -
-
- Closing this issue due to r34278
-
- Since lib/complex.rb starts with # :enddoc: I chose not to apply your lib/complex.rb patch as it cannot be seen by RDoc.
-
- This issue was solved with changeset r34778.
Sylvain, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
----------
* complex.c (Init_Complex): Document Complex::I. Patch by Sy... -
08:58 AM Revision 79bd9c3e (git): * test/ruby/test_literal.rb (TestRubyLiteral#test_special_const): test for https://bugs.php.net/bug.php?id=61095
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34789 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- Gonzalo, please remove trailing whitespace before submitting patches in the future.
-
- This issue was solved with changeset r34773.
Gonzalo, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
----------
* lib/profiler.rb: Add Profiler documentation by Gonzalo Rodr... -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34788 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34787 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- Daniel, I couldn't use your patch as it was not line-wrapped to 80 columns and was too-specific to String. As Marc-Andre pointed out, the randomization behavior applies to Fixnum, Hash, String, Symbol, Array, etc., so I applied a patch ...
-
- This issue was solved with changeset r34769.
Daniel, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
----------
* object.c (rb_obj_hash): Added note that the hash value is no... -
- I'm not sure that all implementations have to return hash codes that differ from one run to the other. I would also modify `Object#hash`, as all hashes in CRuby are random seeded, not just String. I'd recommend adding the following line ...
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34786 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34785 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- [ruby-core:42849]
* include/ruby/ruby.h (UNREACHABLE): fallback definition.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34784 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- handler callbacks.
* test/psych/test_parser.rb: test to demonstrate leak.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34783 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
03:15 AM Revision 0e896b99 (git): pull request #55 as same as #98
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34782 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34781 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34780 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- upon EOFError or Errno::ECONNRESET where count is reset to 0.
* test/net/http/test_http.rb (class TestNetHTTPKeepAlive): Test for
above.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34779 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- Daubert. [Feature #5623]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34778 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
02/23/2012
-
- * parse.y (parser_tokadd_string, parser_yylex): insert a backslash
if the next character is non-ascii. [ruby-dev:45278] [Bug #6069]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/branches/ruby_1_9_3@34777 b2dd03c8-39d4-4d8f-98f... -
- if the next character is non-ascii. [ruby-dev:45278] [Bug #6069]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34776 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34775 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- 2012/2/23 Martin Bosslet <Martin.Bosslet@googlemail.com>:
> Would it be OK to add #bindump, #binload and rb_big_uminus
> to the public API?
I don't understand rb_big_pack/rb_big_unpack is not enough.
Although rb_big_pac... -
10:59 PM Feature #6065: Allow Bignum marshalling/unmarshalling from C API
- I also believe it is useful that the feature to dump a Bignum to C array.
I made a patch for realizing the feature.
Please check this gist https://gist.github.com/1892968
If Matz approve the patch, I will commit that.
-
- Akira Tanaka wrote:
> 2012/2/23 Tanaka Akira <akr@fsij.org>:
> ...
Yes, you're right, when using (unsigned) longs we have to pay
attention to byte order within the long itself or go through
the pain of normalizing them to some pre-de... -
- 2012/2/23 Tanaka Akira <akr@fsij.org>:
> I think your proposal also rely on machine endianness because
> it use "long" type.
>
> I guess bytes in long type (4 bytes or 8 bytes in usual) is
> native endian. Am I wrong?
... -
- 2012/2/23 Martin Bosslet <Martin.Bosslet@googlemail.com>:
>> > Currently, there's no public C API to create a Bignum.
>> > There is rb_big_pack and rb_big_unpack that will do the
>> > job, but they are not portable.
>>
>... -
- Akira Tanaka wrote:
> 2012/2/23 Martin Bosslet <Martin.Bosslet@googlemail.com>:
> ...
Sorry, "not portable" was probably the wrong wording. I meant
I can't use them e.g. from Rubinius because they're not part
of the public API and th... -
- Yui NARUSE wrote:
> I made such dump API before.
> ...
Great, yes, this looks like what I wanted :) I can
determine whether the number was signed using
RBIGSIGN(), which is public - but for the other
way round, when creating a negat... -
- 2012/2/23 Martin Bosslet <Martin.Bosslet@googlemail.com>:
> Currently, there's no public C API to create a Bignum.
> There is rb_big_pack and rb_big_unpack that will do the
> job, but they are not portable.
How are they no... -
- I made such dump API before.
This dump a bignum as a format for OpenSSL::BN.
diff --git a/bignum.c b/bignum.c
index 3145f24..9141dc8 100644
--- a/bignum.c
+++ b/bignum.c
@@ -405,6 +405,90 @@ rb_big_unpack(unsigned long *buf, long... -
- Currently, there's no public C API to create a Bignum.
There is rb_big_pack and rb_big_unpack that will do the
job, but they are not portable.
Could we offer public functionality that is independent
of the internal representation... -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34774 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- [Bug #5816]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34773 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- rather than user configuration.
* test/psych/test_encoding.rb: corresponding tests.
* test/psych/test_parser.rb: ditto
* test/psych/test_tainted.rb: ditto
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34772 b2dd03c8-39d4-4d8f-98ff-8... -
- and how to use custom classes as Hash keys.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34771 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- example of equal? vs == and recommending eql? be aliased to == when
overridden.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34770 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- deterministic on Marc-Andre's suggestion. Expanded description of
the purpose of the hash method. [Bug #6068]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34769 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- Hiroshi Nakamura wrote:
> The original proposal from Martin, turning off the SSL_OP_DONT_INSERT_EMPTY_FRAGMENTS bit by default, is still open.
Yes, to follow up on this: it remains to decide how this
should be handled in librarie... -
- Eric Wong wrote:
> Vit Ondruch <v.ondruch@tiscali.cz> wrote:
> ...
Seems to be something different. It works (I gave it 160 tries) although I reverted the r34719. -
- 2012/2/22 Vit Ondruch <v.ondruch@tiscali.cz>:
> I am afraid that the test results differs if you run the whole test suite in once or if you run just part of the test suite, as you did.
I see.
The hang is reproduced on my ... - 05:40 PM Bug #6068 (Closed): String::Hash documentation clarification
- modified documentation for String::hash to clarify that results are not conistent across sessions and advice for if that behavior is desired
-
- > clang 3.1 is more picky about "control may reach end of non-void function"
or doesn't deal with noreturn attribute properly?
Anyway, (ID)NULL seems odd. -
- Patches were not added in-order.
Note that return.combined.patch contains all the other patches grouped together -
- =begin
clang 3.1 is more picky about "control may reach end of non-void function"
The attached patches contain add (({return Qnil; /* not reached */})) or the equivalent where the warnings occurred.
=end
- 03:22 PM Revision f51ad043 (git): * 2012-02-24
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34768 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34767 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34766 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34765 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- I can conditionally assign a simple constant:
$ ruby -v -e 'p X ||= 1'
ruby 1.9.3p125 (2012-02-16 revision 34643) [x86_64-darwin10.8.0]
1
However, conditional assignment of a nested constant raises a SyntaxError:
$ ruby -v -e ... -
-
- 11:23 AM Bug #6057: URI - Nonsensical Behavior
- Scott Gonyea <scott@aitrus.org> writes:
> Issue #6057 has been updated by Scott Gonyea.
>
>
> I'd be happy to write this improved functionality. But would it be welcome?
Is there anyone who actually *likes* this behavior? -
- Changing the behavior of URI#+ from the current will break many libraries (including mechanize) that depend upon the current behavior of relative resolution.
The current behavior is frequently used to combine, for example, an anchor h... -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34764 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34763 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34762 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- * lib/uri/common.rb (URI::Parser#initialize_regexp):
use \A \z instead of ^ $. [Bug #5843]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/branches/ruby_1_9_3@34761 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
-
04:35 AM Bug #6062: test/yaml/test_yaml.rb tries to use Test::Unit::TestSuite to run
- Sorry, it looks like this file is old, probably from 1.9.1 timeframe. Got included in our local suite and never removed. Disregard.
-
- Berkeley DB.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34760 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34759 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- loaded file. [ruby-trunk - #5910]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34758 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34757 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
02/22/2012
-
- This block of code appears at the bottom of test/yaml/test_yaml.rb, for running the file directly. It prevents running the file directly, since Test::Unit::TestSuite no longer exists. Logic in minitest/testunit will run the test anyway w...
-
- Yui: Thank you. I will be adding this to our suite and excluding anything that fails. I won't worry too much about it since our iconv is implemented atop Java NIO Charset API.
-
- Just FYI, implementations rescued in those tests are also valid
because those tests depends glibc iconv/GNU libiconv vendor specific extensions. -
- This issue was solved with changeset r34750.
Charles, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
----------
* test/iconv/test_option.rb: enabled. [ruby-core:42802][Bug #... -
- FWIW, we (JRuby) would appreciate if whatever change is made gets backported to 1.9.3, since we're running 1.9.3 test suite as part of our normal dev process.
-
- The only test class in test/iconv/test_option.rb is guarded by this line:
...
end if false and defined?(TestIconv)
If this test is still valid, it should be enabled. If it is not valid, it should be removed. -
- * win32/win32.c (rb_w32_uchmod): typo. [Bug#5671] [ruby-dev:44898]
* test/ruby/test_file.rb (TestFile#test_chmod_m17n): test of above bug.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/branches/ruby_1_9_3@34756 b2dd03c8-39d4-4d... - 08:59 PM Bug #6057: URI - Nonsensical Behavior
- > In my opinion, URI should model the behavior of Pathname.
I totally agree.
Additionally I absolutely dislike using global methods instead of class
factory methods. I think it isn't at all obvious and it poisons the
global name... -
11:45 AM Bug #6057: URI - Nonsensical Behavior
- Ah. That's the issue.
1.9.3-p125 :016 > uri = URI("http://google.com/foo/bar/")
=> #<URI::HTTP:0x007fd97a891038 URL:http://google.com/foo/bar/>
1.9.3-p125 :017 > uri + "baz"
=> #<URI::HTTP:0x007fd97a887ab0 URL:http://google.com/... -
11:10 AM Bug #6057: URI - Nonsensical Behavior
- I have only done a few quick tests, but it seems that the '+' operator implements relative resolution (see http://tools.ietf.org/html/rfc3986#section-5.2). For URIs, this makes a lot of sense.
-
- Another example:
URI.join("http://foo.com/baz", "bar", "bim")
# => #<URI::HTTP:0x1005412e URL:http://foo.com/bim>
Also, if we did model the behavior of Pathname, then joining of "/baz" would reset the path which I do think is acc... -
- I'd be happy to write this improved functionality. But would it be welcome?
-
- Edit: Moronic comment redacted.
-
- The behavior of Ruby's URI is confusing, to say the least.
```
URI("http://foo.com/bar") + "baz"
# => #<URI::HTTP:0x710713de URL:http://foo.com/baz>
URI.join("http://foo.com/baz", "bar")
# => #<URI::HTTP:0x29fd5dc4 URL:http://f... - 06:59 PM Revision dfb1a712 (git): * lib/ostruct.rb (delete_field): Bug fix so previous value is returned.
- Patch by Nick Recobra [Bug #6063]
* test/ostruct/test_ostruct.rb: Test for above
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34755 b2dd03c8-39d4-4d8f-98ff-823fe69b080e - 05:33 PM Revision 9c8d348d (git): * 2012-02-23
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34754 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- text/binary modes given explicitly. [ruby-dev:45268][Bug #6055]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34753 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- Vit Ondruch <v.ondruch@tiscali.cz> wrote:
> I gave it try with ruby 2.0.0dev (2012-02-21 trunk 34723)
> [x86_64-linux] and it does not segfaulted in 1000 runs. Now I'm
> wondering what was the fix, since I'd love to see it backpor... -
- I gave it try with ruby 2.0.0dev (2012-02-21 trunk 34723) [x86_64-linux] and it does not segfaulted in 1000 runs. Now I'm wondering what was the fix, since I'd love to see it backported to Ruby 1.9.3.
- 03:15 PM Revision 0894d6d6 (git): * 2012-02-23
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/branches/ruby_1_9_3@34752 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- * test/iconv/test_option.rb: enabled. [ruby-core:42802][Bug #6061]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/branches/ruby_1_9_3@34751 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34750 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- Motohiro KOSAKI wrote:
> スタックオーバーフローだとしたら犯人はわたしなのですが、そもそもいまのSEGVハンドラだと実質printfしかしてないのでprintfだけでスタックを突き破らないと行けなくて、ありうるかなあ・・と悩んでます。が、まず第一弾としてALT STACKにもPROT_NONEなスタックガードページくっつけてスタックオーバーフローがメモリ破壊ではなくクラッシュになるようにすべきでしょうね。そのあと、落ちたときのバックトレースみて... -
- スタックオーバーフローだとしたら犯人はわたしなのですが、そもそもいまのSEGVハンドラだと実質printfしかしてないのでprintfだけでスタックを突き破らないと行けなくて、ありうるかなあ・・と悩んでます。が、まず第一弾としてALT STACKにもPROT_NONEなスタックガードページくっつけてスタックオーバーフローがメモリ破壊ではなくクラッシュになるようにすべきでしょうね。そのあと、落ちたときのバックトレースみてスタック消費の内訳から対策考えましょう。引き取ります
-
- nariです。
以下のようにたまにSEGVのテストで落ちることがありまして、
http://c5664.rubyci.org/~chkbuild/ruby-trunk/log/20120221T130301Z.log.html.gz
原因を調査したところ、SIGSEGVハンドラの中でスタックオーバフローしている
ようでした。
# uname -orv
2.6.18-274.el5 #1 SMP Fri Jul 22 04:43:29 ED... -
- * io.c (rb_io_s_foreach): return enumerator including kerword
arguments. [ruby-dev:45267][Bug #6054]
* io.c (rb_io_s_foreach): argument check before making Enumerator.
[ruby-dev:31525]
git-svn-id: svn+ssh:... -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34748 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34747 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- [Backport #6043]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/branches/ruby_1_9_3@34746 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- I found the source of the bug. My ~/.profile defined $C_INCLUDE_PATH and $CPLUS_INCLUDE_PATH. Having this here did not affect Ruby 1.8.7 or 1.9.2. It did, however, screw up portions of 1.9.3. How strange.
-
- function or variable.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34745 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34744 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
- 10:23 AM Revision 8cd604c6 (git): * reverted 34739 for test/date.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34743 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34742 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
09:47 AM Revision 1a6b0bab (git): * lib/test/unit.rb (setup_options): add option "--retry" as opposite
- for "--no-retry"
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34741 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- cancel "--hide-skip" (-q)
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34740 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34739 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- This reverts commit r34734.
Use -q on your environment.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34738 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- * gc.c : remove gc_clear_mark_on_sweep_slots() and use
rest_sweep() instead of it, because some dead objects might be
marked in next the mark phase by false pointers.
[ruby-core:42672]
git-svn-id: svn+ssh:... -
- [ruby-dev:31525]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34736 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- Akira Tanaka wrote:
> 2012/2/20 Vit Ondruch <v.ondruch@tiscali.cz>:
> ...
I am afraid that the test results differs if you run the whole test suite in once or if you run just part of the test suite, as you did. -
- 2012/2/20 Vit Ondruch <v.ondruch@tiscali.cz>:
>
> The test_pathname appears to hang somewhere. The TestPathname#test_pathsubext_510 is the last output which appears in my log, however there might be some entries lost due to not flus... -
- arguments. [ruby-dev:45267][Bug #6054]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34735 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34734 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34733 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- It was also recommended to me to suggest #to_h here.
def to_h
@table.dup
end
It would be a much easier way of working with the underlying table, such as getting field names.
openstruct.to_h.keys
And of cou... -
- If #each_pair, why not #each? I realize it's an exception to the fields that can be used, but since a few of those are inevitable no matter what, it seems like an acceptable one.
-
- I've updated the pull request.
-
- Hi,
Thomas Sawyer wrote:
> Each change should be separate pull request or just a separate commit?
Ideally, both. It makes it easier to accept only some of the parts. As I said, "in the future"; no need to split your existing comm... -
- Each change should be separate pull request or just a separate commit?
I knew about issue #6029, I was just trying to take care of that a couple of other features while I was involved with the code.
I see what you are saying about... -
- Hi.
In the future, please break requests in independent parts.
- new_ostruct_member will be protected
- `==` is already defined. I don't think any coercion can be accepted in this case. You can't compare a Set and an Array direc... -
03:50 AM Revision 86716b97 (git): remove unbalanced parenthesis
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34732 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34731 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34730 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- Cocoa which is dependent on QuickTime SDK which has separated
since Xcode 4.3.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34729 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34728 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
02/21/2012
-
- This patch fixes one issue, protecting #new_ostruct_member method, and possibly another by dup'ing marshal_dump, but I need more feedback on the later b/c I've also been told it is not needed.
The rest of this patch provides enhanceme... -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34727 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
10:23 PM Bug #5671 (Closed): windows でのマルチバイト文字列を含むファイルへの File.chmod
- r33873 で修正されていました。ありがとうございます。
チケットを放置してしまいすみませんでした。 -
09:35 PM Feature #3944: Add Fiber#root? method
- Any progress on this?
-
- Its ndbm.h doesn't include db.h.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34726 b2dd03c8-39d4-4d8f-98ff-823fe69b080e - 09:04 PM Revision 80a6b147 (git): * 2012-02-22
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34725 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- * ext/dbm/extconf.rb: check DBC type for above.
[ruby-dev:45269]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34724 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- It crashed on 8th retry with ruby 1.9.3p125 (2012-02-16 revision 34643) [x86_64-linux]. Going to try with trunk ...
-
- I don't have ARM knowledge.
If someone has an idea, contribution is welcome. -
- Yui NARUSE wrote:
> Vit Ondruch wrote:
> ...
Of course I test also on i686 and x86_64 and I cannot reproduce it there.
-
- Vit Ondruch wrote:
> Unfortunately, it still fails: http://arm.koji.fedoraproject.org/koji/getfile?taskID=451175&name=build.log
Hmm, is it only reproduced on ARM? -
- Unfortunately, it still fails: http://arm.koji.fedoraproject.org/koji/getfile?taskID=451175&name=build.log
-
- This issue was solved with changeset r34717.
Marc-Andre, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
----------
* proc.c (rb_hash_proc): get wrapped pointer properly. [Bu... -
-
- This issue was solved with changeset r34715.
Marc-Andre, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
----------
* proc.c (method_hash, proc_hash): Fix {Unbound}Method#hash... - 12:23 AM Bug #6048: {Unbound}Method#hash doesn't always return the right value
- Hi,
On Mon, Feb 20, 2012 at 3:24 AM, Nobuyoshi Nakada <nobu@ruby-lang.org> wrote:
>
> Issue #6048 has been updated by Nobuyoshi Nakada.
> One thing.
>
> rb_method_definition_t* hasn't been used as function interface, rb_m... -
- Some file systems(e.g. ext3, ext4) use do_sync_read() for general read.
http://lxr.linux.no/#linux+v3.2.6/fs/ext3/file.c#L55
http://lxr.linux.no/#linux+v3.2.6/fs/ext4/file.c#L231
In read process, do_generic_file_read() is called fin... -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34723 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34722 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- Curses::VERSION.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34721 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34720 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- rest_sweep() instead of it, because some dead objects might be
marked in next the mark phase by false pointers.
[ruby-core:42672]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34719 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- warnings.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/branches/ruby_1_9_3@34718 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34717 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- and {ruby,vendor,site}archdir. [ruby-core:42766][Feature #6052]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34716 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
02:59 AM Bug #6053 (Closed): Enumerator#rewind goes to beginning instead of decrementing one step.
- This issue was solved with changeset r34712.
Chris, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
----------
* enumerator.c (enumerator_rewind): update the documentation.
... -
- It is a bug in documentation. #rewind method rewinds the sequence to the beginning.
-
01:31 AM Bug #6053 (Closed): Enumerator#rewind goes to beginning instead of decrementing one step.
- From the ruby docs:
rewind → e
Rewinds the enumeration sequence by one step.
In practice, however, it fully rewinds (either change documentation or have it do what it says. Going back one step is nice though):
irb(main):001... - 12:13 AM Revision f12c14d3 (git): * proc.c (method_hash, proc_hash): Fix {Unbound}Method#hash
- [Bug #6048]. Isolate hash computation for proc
* internal.h: Declaration for above
* vm_method.c (rb_method_definition_hash): Computation for
hash part of a method definition
* method.h: Declaration for above
* test/ruby/test_metho...
02/20/2012
- 11:55 PM Revision 80ca7d23 (git): * 2012-02-21
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/branches/ruby_1_9_3@34714 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
- 11:55 PM Revision a81a8172 (git): merge revision(s) 34712:
- * enumerator.c (enumerator_rewind): update the documentation.
fixed: #6053
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/branches/ruby_1_9_3@34713 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
11:40 PM Bug #6049 (Closed): Build failure on enc/mktable.so with VC 2010Build failure on enc/mktable.so with VC 2010
- This issue was solved with changeset r34708.
Heesob, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
----------
* enc/depend: ignore mktable.c because it's not encoding librar... -
06:02 PM Bug #6049 (Closed): Build failure on enc/mktable.so with VC 2010Build failure on enc/mktable.so with VC 2010
- I got the following failure on Windows XP with VC 2010 while building trunk.
C:\work\snapshot>nmake
Microsoft (R) Program Maintenance Utility Version 10.00.30319.01
Copyright (C) Microsoft Corporation. All rights reserved.
... -
- The test_pathname appears to hang somewhere. The TestPathname#test_pathsubext_510 is the last output which appears in my log, however there might be some entries lost due to not flushed log.
-
- Tests passes with following command: "make check TESTS="-v -x test_pathname.rb -x test_drbssl.rb -x test_parse.rb -x test_x509cert.rb"
The test_drbssl.rb and test_x509cert.rb might be related to the OpenSSL changes? -
- Bohuslav Kabrda wrote:
> Well, thanks for fixing the gdbm support, but the other 16 failures and 20 errors are the main reason why I reported the bug... Could you have a look at that?
> ...
Vit, could you inspect this? - 04:12 PM Bug #6036: Test failures in Fedora Rawhide/17
- Well, thanks for fixing the gdbm support, but the other 16 failures and 20 errors are the main reason why I reported the bug... Could you have a look at that?
Thanks. - 09:30 PM Feature #4970 (Closed): FileUtils refactored
- This issue was solved with changeset r34706.
Thomas, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
----------
* lib/fileutils.rb: revert a line modified accidentally at r346... -
- Yui NARUSE wrote:
> これ、libedit 側のバグですね。
> ...
http://gnats.netbsd.org/cgi-bin/query-pr-single.pl?number=46059 本家に報告しました。
libedit はバージョン取れないので Third Party's Issue ってことにします。 -
- fixed: #6053
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34712 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- One thing.
rb_method_definition_t* hasn't been used as function interface, rb_method_entry_t* might be preferable. -
- Seems fine.
-
- {Unbound}Method#hash doesn't always return the right value.
map, collect = Array.instance_method(:map), Array.instance_method(:collect)
map.eql?(collect) # => true
map.hash == collect.hash # => false
I'm te... -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34711 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
- 03:00 PM Revision e5cb1bb9 (git): * 2012-02-21
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34710 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34709 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
- 02:40 PM Revision 07d8dffe (git): * enc/depend: ignore mktable.c because it's not encoding library.
- [ruby-core:42760] [Bug #6049]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34708 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- Fixed by mergin Onigmo 5.13.1 in Ruby 2.0.
-
- Fixed by merging Onigmo 5.13.1.
-
- Jon Forums wrote:
> I think you're right on runtime library mismatch, but shouldn't it fail when miniruby is used later in the build process, not at miniruby link time?
The mismatch between the compiler and the runtime library. It can'... -
04:29 AM Bug #5676: miniruby linking error: undefined reference to ___stack_chk_guard
- Thanks for checking. Trunk builds fine using the old default gcc 4.2.1 and configure adds `-fstack-protector` to Makefile.
I think you're right on runtime library mismatch, but shouldn't it fail when miniruby is used later in the build ... -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34707 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
12:30 PM Revision 5cfba33a (git): * lib/fileutils.rb: revert a line modified accidentally at r34669.
- This fixes mingw test errors in TestDir_M17N.
[ruby-core:42728] [Feature #4970]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34706 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34705 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- header/library choice.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34704 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- "ndbm". It seems several (possibly historical) distributions
provide libndbm. However the content of libndbm vary: Berkeley DB,
GDBM or even 4.3BSD NDBM. (Mandriva, Tru64 UNIX, OpenSuSE,
SCO OpenServer, ...)
"ndbm" is not sear... -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34702 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
- 06:53 AM Feature #6023: Add "a ?= 2" support for meaning "a = a.nil? ? 2 : a"
- Magnus Holm <judofyr@gmail.com> writes:
> If we want something like this, we should provide a non-assignment
> version too. Perl uses // for the same purpose:
>
> sub foo {
> my ($foo, %options) = @_;
> $foo //=... -
05:53 AM Feature #6023: Add "a ?= 2" support for meaning "a = a.nil? ? 2 : a"
- > I've just proposed this idea to Groovy and I thought the same semantics would be interesting to have in Ruby too:
>
> http://jira.codehaus.org/browse/GROOVY-5306
>
> This is a minor, but important, difference to the "a ||= 2" synt... - 06:50 AM Revision aa27e42f (git): * 2012-02-20
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34701 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34700 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- Yusuke Endoh wrote:
> Hello, Martin
> ...
Hi Yusuke,
you're right, my apologies! I just read 'read_all' and
'a lot of reallocs' and was immediately reminded of what
I noticed on a different note :) I opened Issue #6047 for
thi... -
- In the general case, read_all grows its buffer linearly by just the amount that is currently read from the underlying source. This results in a linear number of reallocs, It might turn out beneficial if the buffer were grown exponentiall...
-
- Bump
-
- Worth pointing out that the cost of allocating an exception every time could be blunted by always raising the *same* exception object. This avoids the backtrace, construction cost, *and* mixin overhead in one shot, provided you're ok wit...
-
- I never got to weigh in on this thread back in the day, and I'm working on IO stuff more recently, so a few thoughts...
Eric Wong wrote:
> * Exceptions with the current *_nonblock methods are expensive.
> ...
This is really poor fo...