Activity
From 12/07/2011 to 12/13/2011
12/13/2011
-
05:23 PM Bug #5714: Unexpected error of STDIN#read with non-ascii input on Windows XP
- Hello,
In message "[ruby-core:41628] [ruby-trunk - Bug #5714] Unexpected error of STDIN#read with non-ascii input on Windows XP"
on Dec.13,2011 16:44:29, <h.shirosaki@gmail.com> wrote:
> It's difficult, but it seems switchi... -
04:44 PM Bug #5714: Unexpected error of STDIN#read with non-ascii input on Windows XP
- > Hiroshi and Heesob, do you guys think can solve this without reverting
> ...
It's difficult, but it seems switching from binary mode to text mode would be possible. I added binary and text mixed test cases.
I use implicit mode setti... -
12:23 AM Bug #5714: Unexpected error of STDIN#read with non-ascii input on Windows XP
- On Sun, Dec 11, 2011 at 11:42 PM, U.Nakamura <usa@garbagecollect.jp> wrote:
> Hello,
>
> In message "[ruby-core:41578] [ruby-trunk - Bug #5714] Unexpected error of STDIN#read with non-ascii input on Windows XP"
> Â Â on Dec.10,2011... -
04:33 PM Revision 8e9ab339 (git): * thread_pthread.c (rb_thread_create_timer_thread): fix memory
- leak. [ruby-dev:44904] [Bug #5688]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34033 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
04:13 PM Bug #5754 (Closed): Double require bug in 1.9.3
- This issue was solved with changeset r34027.
Evan, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
----------
* load.c (load_unlock): all threads requiring one file should
s... -
07:58 AM Bug #5754: Double require bug in 1.9.3
- I missed pruning out one bit from rubyspec so I've fixed it and put the code into a gist: https://gist.github.com/1469546
-
- There appears a bug in the handling of concurrent requires of the same file. If a thread (t2) is waiting for another thread (t1) to finish requiring the file, but requiring the file raises an exception, t1 signals t2 and t2 tries to requ...
-
04:11 PM Bug #5756 (Feedback): crashs when Twitter.update_with_media with rails
- * please upload full of log; your uploaded "crashog.txt" seems partial.
* "ruby -v" is not output of `ruby -v`; please paste exact output of "ruby -v" like this: ruby 2.0.0dev (2011-11-25 trunk 33837) [x86_64-darwin11.2.0]
thanks. -
03:55 PM Bug #5756 (Rejected): crashs when Twitter.update_with_media with rails
- I'm using the Ruby 1.9.3dev and Ruby on Rails 3.1.3
When I use twitter gem and call 'Twitter.update_with_media', the interpreter crashs.
~~ ruby
class WelcomeController < ApplicationController
def upload
Twitter.update_with_... - 03:01 PM Revision 07e447fb (git): * 2011-12-14
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34032 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- [Bug #5614]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34031 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
02:56 PM Revision 3dd1e6a9 (git): * ChangeLog: add ML/ticket links to r34028 entry. [ruby-core:41612] [Bug #5755]
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34030 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34029 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- ignore exception under rb_protect().
* test/ruby/test_exception.rb (test_exception_in_name_error_to_str):
add a corresponding test.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34028 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
12:23 PM Bug #5737: WEBrick doesn't support keep alive connections for 204 and 304 responses - On Tue, Dec 13, 2011 at 10:35:16AM +0900, Hiroshi Nakamura wrote:
>
> Issue #5737 has been updated by Hiroshi Nakamura.
>
> Status changed from Closed to Open
>
> Sorry for not responding.
>
> As a maintainer, I'll review th... -
10:35 AM Bug #5737 (Open): WEBrick doesn't support keep alive connections for 204 and 304 responses
- Sorry for not responding.
As a maintainer, I'll review the patch later. I don't understand now, the rationale why we should do keep-alive for 304/204 even if the response is neither chunked nor having content-length. Handling empty ... -
07:20 AM Bug #5737 (Closed): WEBrick doesn't support keep alive connections for 204 and 304 responses
- Applied this in r34023
-
11:04 AM Bug #5681 (Closed): Conflcting types for rb_w32_inet_ntop caused by duplicate definition under MinGW
- Oops, disregard, I had dirty files.
-
- =begin
r33919 broke the socket extension on OS X:
have_func: checking for inet_ntop(0, (const void *)0, (char *)0, 0)... -------------------- yes
"clang -o conftest -I../../.ext/include/x86_64-darwin11.2.0 -I../.././include ... -
- share same loading barrier, so it must be kept alive while those
are waiting on it. [ruby-core:41618] [Bug #5754]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34027 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34026 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- This issue was solved with changeset r34020.
Yukihiro, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
----------
* vm_insnhelper.c (vm_yield_setup_block_args): splat single
... -
05:12 AM Bug #5752 (Closed): Array#delete_if side effects due to changeset r32360
- It seems that the changeset r32360 introduced another side effect. Here are two IRB sessions, one in ruby-1.9.2-p136 and the other in ruby-1.9.3-p0:
ruby-1.9.2-p136 :001 > x = [1,2,3,4,5,6,7,8,9]
=> [1, 2, 3, 4, 5, 6, 7, 8, 9]
rub... -
04:33 AM Revision 5e12ce3c (git): * ChangeLog: style fix.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34025 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- A brace after method invocation is parsed as a block.
-
01:58 AM Bug #5751 (Rejected): functions unable to handle hashes containing spaces unless wrapped in parenthesis
- puts { :a => :b}
SyntaxError: (irb):23: syntax error, unexpected tASSOC, expecting '}'
puts { :a => :b}
puts { a: :b}
SyntaxError: (irb):24: syntax error, unexpected ':', expecting '}'
puts { a: :b}
> def foo x
> ...
=> ni... -
12:54 AM Feature #5749: new method String#match_all needed
- If memory serves Facets has #mscan method.
-
12:14 AM Bug #5750 (Open): Thread.current local-variables behavior
- Sorry, I was stupid. Indeed the documatation has room for improvement.
If I recall correctly, akira tanaka suggested the current behavior.
So I'm reopening and assigning this ticket to him.
--
Yusuke Endoh <mame@tsg.ne.jp>
12/12/2011
-
11:58 PM Bug #5750: Thread.current local-variables behavior
- Although I consider this behavior (and the reason why it was done) completely absurd, how about at least changing the documentation to mention the real behavior of the supposedly thread-local storage ?
Replacing thread-local by fiber-lo... -
- Hello, thank you for your reporting.
I am not surprised that you are surprised, but it is intentional.
The rationale is because most of legacy libraries that uses thread-
local storage will expect the storage to be also fiber-loca... -
- Hi, I stumbled upon something which for me is a bug and wanted to check if it is working as intended or not:
Thread.current[:a] = 1
p Thread.current[:a] # => 1
Fiber.new do
p Thread.current[:a] # => nil
end.... -
- are allowed to have Keep-Alive connections.
* test/webrick/test_httpresponse.rb: corresponding test.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34024 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- are allowed to have a Keep-Alive connection. [ruby-core:41581]
* test/webrick/test_httpresponse.rb: corresponding test.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34023 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- [ruby-dev:44984][Bug #5753]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34022 b2dd03c8-39d4-4d8f-98ff-823fe69b080e - 08:50 PM Revision a3eaaf89 (git): * 2011-12-13
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34021 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- argument if optinal arguments are defined not only mandatory or
post arguments. [ruby-core:41557] [Bug #5730]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34020 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/branches/ruby_1_9_3@34019 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
06:42 PM Feature #5749: new method String#match_all needed
- Yui NARUSE wrote:
> Why don't you use $~, $&, $`, $', $+, $1, $2, .. in scan' block parameter?
You reminds me! Yes, what I want can be done in this tricky way. Thank you!
However, I think relying on these special global variables ... -
06:18 PM Feature #5749: new method String#match_all needed
- Why don't you use $~, $&, $`, $', $+, $1, $2, .. in scan' block parameter?
-
- The String class should contain an instance method 'match_all', which is a mixture of 'match' and 'scan'.
The method 'scan' is not a very powerful tool, its result(the yielding thing) is just a matched string or an array of captured s... - 05:47 PM Revision f7a9b07c (git): * 2011-12-13
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/branches/ruby_1_9_3@34018 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- * ext/psych/lib/psych.rb: update psych version.
* ext/psych/psych.gemspec: generate new gemspec for new version.
* ext/psych/lib/psych.rb: calling `yaml` rather than `to_yaml`.
* ext/psych/lib/psych/nodes/node.rb: Rename `to... -
05:33 PM Bug #5748 (Closed): class_eval ブロック内での定数のスコープがドキュメントと矛盾
- 以下の class_eval の説明によると、
http://doc.ruby-lang.org/ja/1.9.3/method/Module/i/class_eval.html
> 定数とクラス変数のスコープは、自身のモジュール定義式内と同じスコープになります。
とのことですが、以下のコードを実行すると NameError が発生します。
class MyClass
CONST = "MyClass"
end
MyClass.class_... -
- This issue was solved with changeset r34013.
Yura, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
----------
* load.c (rb_feature_p): lazy assigned load_path searched in
lo... -
01:43 PM Revision 900b4a6d (git): * parse.y (stmt_or_begin): changed the error message for BEGIN not
- at toplevel. [ruby-dev:44963] [Bug #5738]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34016 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
01:31 PM Bug #5688: Solaris10 で spawn を繰り返すとメモリリークする
- 後藤です。sparc上のSolaris担当ということになってますが、Intelチップ上のSolarisはよく知りません。
r34010 + trunk用のパッチが、sparc 上の Solaris10 にて、SunStudio 11, gcc 4.4.3, gcc 3.4.3, fcc 5.6 の32ビット、64ビット両方のコンパイルオプションにて、make testが通り、Error/Failureが増えていないことを確認しました。
Oracle Sola... -
01:23 PM Bug #5688: Solaris10 で spawn を繰り返すとメモリリークする
- まつもと ゆきひろです
In message "Re: [ruby-dev:44971] Re: [ruby-trunk - Bug #5688] Solaris10 で spawn を繰り返すとメモリリークする"
on Mon, 12 Dec 2011 13:16:08 +0900, Shugo Maeda <shugo@ruby-lang.org> writes:
|> そろそろgithub化してpull requestで処理す... -
- 前田です。
2011年12月12日12:54 Yukihiro Matsumoto <matz@ruby-lang.org>:
> |Assignee changed from okkez _ to Yukihiro Matsumoto
> |見落されているようなので一旦まつもとさんに担当を振ってみます。
>
> おお、見落としてました。例の手順(see [ruby-dev:43227])で申請
> してください。前田くん、よろしく。
... -
- まつもと ゆきひろです
In message "Re: [ruby-dev:44968] [ruby-trunk - Bug #5688] Solaris10 で spawn を繰り返すとメモリリークする"
on Mon, 12 Dec 2011 12:36:09 +0900, okkez _ <redmine@ruby-lang.org> writes:
|Assignee changed from okkez _ to Yukihi... -
- 見落されているようなので一旦まつもとさんに担当を振ってみます。
-
- まつもと ゆきひろです
In message "Re: [ruby-dev:44966] Re: [ruby-trunk - Bug #5738][Rejected] if false; BEGIN {}; end が syntax error になる"
on Sat, 10 Dec 2011 23:25:19 +0900, Shugo Maeda <shugo@ruby-lang.org> writes:
|エラーメッセージがわか... -
- Hi,
In message "Re: [ruby-core:41600] [ruby-trunk - Bug #5694] Proc#arity doesn't take optional arguments into account."
on Mon, 12 Dec 2011 11:30:26 +0900, Marc-Andre Lafortune <ruby-core@marc-andre.ca> writes:
|Yukihir... -
11:30 AM Bug #5694: Proc#arity doesn't take optional arguments into account.
- Hi,
Yukihiro Matsumoto wrote:
> We are not going to add incompatible changes to trunk, ...
Could you please explain to me what difference you see between an "incompatible change" and any "bug fix"?
Every bug fix will change som... -
- Hi,
In message "Re: [ruby-core:41593] [ruby-trunk - Bug #5694][Open] Proc#arity doesn't take optional arguments into account."
on Mon, 12 Dec 2011 02:06:26 +0900, Marc-Andre Lafortune <ruby-core@marc-andre.ca> writes:
|I... -
- Changing this to "open", as this bug can not simply be "rejected" as the implementation currently doesn't agree with the documentation.
Either the documentation needs to change, or the implementation needs to change.
Here's why I (... -
- We are not going to add incompatible changes to trunk, unless we see consensus after discussion. I think this is not the case. Currently and for near future, arity ignores optional arguments. Use #parameters or propose new API like #ari...
-
- Hello,
In message "[ruby-core:41578] [ruby-trunk - Bug #5714] Unexpected error of STDIN#read with non-ascii input on Windows XP"
on Dec.10,2011 06:49:55, <luislavena@gmail.com> wrote:
> Category set to build
build?
... - 09:53 AM Bug #5746: Proc#curry too strict about lambda's arity.
- Hi,
On Sun, Dec 11, 2011 at 4:06 PM, Yukihiro Matsumoto <matz@ruby-lang.org> wrote:
> Hi,
>
> In message "Re: [ruby-core:41594] [ruby-trunk - Bug #5746][Open] Proc#curry too strict about lambda's arity."
> Â Â on Mon, 12 Dec 201... -
- Hi,
In message "Re: [ruby-core:41594] [ruby-trunk - Bug #5746][Open] Proc#curry too strict about lambda's arity."
on Mon, 12 Dec 2011 02:08:08 +0900, Marc-Andre Lafortune <ruby-core@marc-andre.ca> writes:
|Currently, Pro... -
- Currently, Proc#curry raises an error when you attempt to curry a lambda with optional (but limited) arguments:
l = ->(arg = 42) {}
l.curry(1) # => ArgumentError: wrong number of arguments (1 for 0)
Note that Proc#curry be... -
- Currently, Proc#curry checks the validity of the `arity` argument and will raise an error if:
1) arity is less than the number of required arguments or
2) arity is more than the maximum number of arguments
Note that simple Procs alw... -
- patched by eMxyzptlk. https://github.com/ruby/ruby/pull/62
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34015 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34014 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- loading_table were not expanded, but all features, pushed to
loading table, are expanded. a patch by Yura Sokolov
<funny.falcon AT gmail.com> in [ruby-core:41545]. [Bug #5727]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34013... - 06:41 AM Revision 1297bedc (git): * 2011-12-12
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34012 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- Nick Howard <ndh AT baroquebobcat.com>.
https://github.com/ruby/ruby/pull/65
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34011 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
01:05 AM Feature #5741: Secure Erasure of Passwords
- Thanks for investigating! I looked into it, here's what
I found.
`String#tr!` doesn't work unfortunately. The original string's buffer
is deleted and the replacement takes place in a newly allocated
buffer [1]. I verified this in ...
12/11/2011
-
- Marc-Andre Lafortune wrote:
> You sure seem to enjoy reverting my commits.
I don't want to see such ugly commits.
I hate reverting but I hate more legacy code in ruby repo.
> ...
The rdoc describes optional arguments but doesn't ... -
- This issue was solved with changeset r34010.
art , thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
----------
* lib/net/imap.rb: includes the sequence number of UID in a error... -
- This issue was solved with changeset r34009.
mathew, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
----------
* ext/syslog/syslog.c: fix a typo. [ruby-core:41585] [Bug #5740] -
03:46 AM Bug #5740 (Closed): Trivial typo in ext/syslog.c
- diff --git a/ext/syslog/syslog.c b/ext/syslog/syslog.c
index f7d622e..02f36aa 100644
--- a/ext/syslog/syslog.c
+++ b/ext/syslog/syslog.c
@@ -111,7 +111,7 @@ static VALUE mSyslog_close(VALUE self)
* LOG_KERN:: A kernel message (not... -
- This issue was solved with changeset r34008.
Akira, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
----------
* error.c (exit_initialize): deal with true and false as well as... -
02:24 AM Bug #5728: SystemExit.new(bool, message)
- I wrote a patch.
-
07:23 AM Feature #5741: Secure Erasure of Passwords
- Eric Wong <normalperson@yhbt.net> wrote:
> You can use `IO#read` / `StringIO#read` to overwrite an existing String:
`String#tr!` (on binary strings) can also work:
~~~ruby
# -*- encoding: binary -*-
pass = ""
$stdin.sysread(256... -
- Martin Bosslet <Martin.Bosslet@googlemail.com> wrote:
> 3. Are there better alternative ways how we could achieve this?
You can use `IO#read` / `StringIO#read` to overwrite an existing String:
----------- /tmp/pass.rb ------------... -
- In other languages it is considered good practice to securely erase
passwords immediately after they were used. Imagine authentication
in a web app - ultimately a String containing the password arrives
at the server, where it will be... -
- message. suggested by art lussos.
[ruby-core:41413] [Feature #5692]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34010 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34009 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- Kernel#exit. [ruby-dev:44951] [Bug #5728]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34008 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- an Integer if possible, but returns nil instead of raising an
exception otherwise.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34007 b2dd03c8-39d4-4d8f-98ff-823fe69b080e - 01:34 AM Revision 0468b1bd (git): * 2011-12-11
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34006 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- rb_f_exit. assume 0 to be success in Kernel#exit! too.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@34005 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
12/10/2011
-
11:35 PM Bug #5739: [BUG] object allocation during garbage collection phase
- This thing actually occurring when there's infinite loop and stack overflow, but it should say "stack level too deep", not generate bug scary messages. I was wrong about not being able to reproduce on 1.8.7. It's reproducible and user co...
-
- Hi.
Getting the following error off ruby-1.9.2-p290. I have no idea what that means and why it occurs in production environment and it's freaking me and users out. It's working okay with 1.8.7.
Thanks! -
- 前田です。
2011年12月10日22:10 Yukihiro Matsumoto <matz@ruby-lang.org>:
> エラーのタイプは異なりますが、この変更は意図的です。ifでくくってあってもBEGINはコンパイル時に登録されます。ので、トップレベルでしか登録できないように文法が変更されました。
エラーメッセージがわかりにくくなっている気がするのですが、こんな感じで
エラーメッセージを表示してはどうでしょうか。
... -
10:34 PM Bug #5738: if false; BEGIN {}; end が syntax error になる
- 了解です。ありがとうございます。
-
- エラーのタイプは異なりますが、この変更は意図的です。ifでくくってあってもBEGINはコンパイル時に登録されます。ので、トップレベルでしか登録できないように文法が変更されました。
-
- 1.8 の時と異なり、以下のコードが syntax error になります。
if false; BEGIN {}; end
test/ruby/test_beginendblock.rb や過去の NEWS に記述がない事などから、もしかしたらバグかもしれないと考えています。1.9 からの仕様であれば reject してやってください。
なお、以下についても syntax error になりますが、1.8 の時と異なり、yyerror("BEGI... -
- I modified the patch because rubygems didn't work properly.
However, I think it is consistent with _read() api behavior that read(length) does CRLF conversion.
Ruby 1.9 doesn't do CRLF conversion, but ruby 1.8 does.
>ruby -ve "open(... -
- Usa, what do you think about attached read_binmode.patch?
-
- Hi,
(11/12/10 1:19), Yukihiro Matsumoto wrote:
> I am happy to see we agree. Nobu, could you fix this issue?
Roger.
# But I'm afraid no time at this weekend.
--
Nobu Nakada -
- Hi,
In message "Re: [ruby-core:41568] Re: [ruby-trunk - Bug #5730][Open] Optinal block parameters assigns wrong"
on Fri, 9 Dec 2011 18:03:15 +0900, Tanaka Akira <akr@fsij.org> writes:
|I.e. You are right. Now I think it... -
12:24 PM Revision 858cb3f6 (git): oops.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/branches/ruby_1_8_7@34004 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- * lib/securerandom.rb: call OpenSSL::Random.seed at the
SecureRandom.random_bytes call.
based on the patch by Masahiro Tomita. [ruby-dev:44270]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/branches/ruby_1_8@32741 b2d... -
- * mkconfig.rb: fix for continued lines. based on a patch from
Marcus Rueckert <darix AT opensu.se> at [ruby-core:20420].
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@20587 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
Signed-off-... - 12:17 PM Revision 5a7338d8 (git): * 2011-12-10
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/branches/ruby_1_8_7@34001 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- * numeric.c (flo_cmp): Infinity is greater than any bignum
number. [ruby-dev:38672]
* bignum.c (rb_big_cmp): ditto.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@23730 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
Signed-... -
- * ext/openssl/ossl_x509store.c (ossl_x509store_initialize): initialize
store->ex_data.sk. [ruby-core:28907] [ruby-core:23971]
[ruby-core:18121]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@27064 b2dd03c8-39d4-4... -
- WEBrick doesn't support keep alive connections for 204 and 304 responses. If a 204 or 304 response is made along with a keepalive, a warning is issued and webrick closes the connection.
I've attached a patch that fixes the problem, a... -
08:42 AM Bug #5713: Fixnum#** returns Infinity for 0 ** negative Bignum
- FYI, I've been doing RubySpec work on this in Rubinius: https://github.com/rubinius/rubinius/commits/master/spec/ruby/shared/rational/exponent.rb
-
- John Firebaugh wrote:
> The execution path of 0 ** -Bignum goes to Rational(0) ** -Bignum, so I think the issue is there. I.e. Rational(0) ** -Bignum should raise ZeroDivisionError, the same as Rational(0) ** -Fixnum.
Yes, unless the... -
- The execution path of 0 ** -Bignum goes to Rational(0) ** -Bignum, so I think the issue is there. I.e. Rational(0) ** -Bignum should raise ZeroDivisionError, the same as Rational(0) ** -Fixnum.
- 08:12 AM Revision 5f3470b3 (git): * 2011-12-10
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@33998 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@33997 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@33996 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
06:29 AM Feature #5478: Add syntax to import Set into core
- On 2011-12-09, at 12:05:41, Alexey Muranov wrote:
>
> I agree, i was simply pointing out that set is, in my opinion, a more basic data structure than associative array, and both associative arrays and relations can be either built on... -
- Numeric#quo currently constructs a Rational with self as the raw numerator, doing no coercion, before dividing. Instead it should follow the same pattern as Numeric#{numerator,denominator}, and convert self with #to_r. This allows any Nu...
-
- Just saw this update. Yes, as I stated, same issue as 5713. Yes the case for (-1) and bignum exponents can be fixed too. The case for 1 and 0 must be addressed for rational and float exponents too (but -1 will go to float for those)
-
- The failing cases are the ones that go through the Rational(+/-1) ** Bignum code path, so this is closely related to #5713.
12/09/2011
-
07:05 PM Feature #5478: Add syntax to import Set into core
- Magnus Holm wrote:
>
> ...
I agree, i was simply pointing out that set is, in my opinion, a more basic data structure than associative array, and both associative arrays and relations can be either built on top of it, or simply repre... -
- 2011/12/9 Yukihiro Matsumoto <matz@ruby-lang.org>:
> |I think the consistency explains current behavior.
>
> From above examples, I consider the current behavior is NOT consistent
> at all, under some condition.
The beha... -
05:59 PM Bug #5730: Optinal block parameters assigns wrong
- Matz,
On 09.12.2011 09:44, Yukihiro Matsumoto wrote:
> Hi,
>
> In message "Re: [ruby-core:41561] Re: [ruby-trunk - Bug #5730][Open] Optinal block parameters assigns wrong"
> on Fri, 9 Dec 2011 17:31:31 +0900, Matthias ... -
- Hi,
In message "Re: [ruby-core:41559] Re: [ruby-trunk - Bug #5730][Open] Optinal block parameters assigns wrong"
on Fri, 9 Dec 2011 09:36:00 +0900, Tanaka Akira writes:
|If we break consistency between method invocation... -
- 2011/12/9 Yukihiro Matsumoto <matz@ruby-lang.org>:
> The following program do not expand the given array, but it should expand the value.
It is not clear.
If we break consistency between method invocation and block invoca... - 09:29 AM Bug #5730: Optinal block parameters assigns wrong
- On Fri, Dec 09, 2011 at 08:59:26AM +0900, Yukihiro Matsumoto wrote:
>
> Issue #5730 has been reported by Yukihiro Matsumoto.
>
> ----------------------------------------
> Bug #5730: Optinal block parameters assigns wrong
> http... -
- The following program do not expand the given array, but it should expand the value.
def foo(&block)
block.call([1,2])
end
h = foo{|k=6,v=8|
p [k,v] # gives [[1,2],8] but should be [1,2]
} -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@33995 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
01:31 PM Feature #5735 (Closed): Extending the use of splat operator to when it is inside a hash
- Ruby convention of allowing omittion of the curly brackets for the last argument is convenient:
foo(arg1, arg2, 1 => :a, 2 => :b)
Sometimes, I want to pass a hash with some modifications. For example, suppose `h = {3 => :c, 4 => :d... -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@33994 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- * enc/trans/single_byte.trans: ditto.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@33993 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@33992 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- ascii only. [ruby-core:41556] [Bug #5733]
tests are contributed by nobu.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@33991 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
04:12 AM Feature #5623: [PATCH] Update documentation for Complex
- I marked each deprecated because there is
-
- Hi,
Yui NARUSE wrote:
> Revert r33921.
> ...
I just noticed this, as I think the mailing list didn't get this update (at least I didn't)
You sure seem to enjoy reverting my commits.
> Because following two reason:
> ...
What ...
12/08/2011
-
11:41 PM Feature #5231: Allow to disable versioned paths
- The recent version of patch fix small issue with RubyGems LOAD_PATH order.
- 11:00 PM Revision 11d85dc1 (git): * 2011-12-09
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@33990 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@33989 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
10:59 PM Bug #5728: SystemExit.new(bool, message)
- >> I don't think we have two.
>>
>> The latter choice is not acceptable, since the return value of (({Kernel#system})) and the first argument of (({Kernel#exit})) are same as the former.
>>
>> And should not assume (({EXIT_SUCCE... -
- 2011/12/8 Nobuyoshi Nakada <nobu@ruby-lang.org>:
> I don't think we have two.
>
> The latter choice is not acceptable, since the return value of (({Kernel#system})) and the first argument of (({Kernel#exit})) are same as the fo... -
- =begin
I don't think we have two.
The latter choice is not acceptable, since the return value of (({Kernel#system})) and the first argument of (({Kernel#exit})) are same as the former.
And should not assume (({EXIT_SUCCESS})) to b... -
- > I think SystemExit.new should accept a bool.
We have two choice and both are a lot of confusable.
1) true => EXIT_SUCCESS, false => EXIT_FAILURE
People may dislike it becuase true mapped 0 and false mapped 1.
2) true => EXIT... -
- I found SystemExit.new doesn't take a bool as exit status:
It works well if an integer is given for status.
% ./ruby -e 'SystemExit.new(0, "msg")'
% ./ruby -e 'SystemExit.new(1, "msg")'
But it doesn't work if the status ... -
09:59 PM Feature #5478: Add syntax to import Set into core
- On Wed, Dec 7, 2011 at 10:01, Alexey Muranov
<muranov@math.univ-toulouse.fr> wrote:
>
> ...
From a theoretical point of view, a relation has a heading + a set
that holds tuples (arrays):
```ruby
class Relation
attr_reader :... -
- 2011/12/8 Nobuyoshi Nakada <nobu@ruby-lang.org>:
> Why don't you use (({SystemExit#success?})) ?
Oops. I missed that. Thanks.
--
Tanaka Akira -
- =begin
Why don't you use (({SystemExit#success?})) ?
=end
-
- I'd like to define Process::EXIT_SUCCESS and Process::EXIT_FAILURE.
I want to use them to test my command line application.
The test calls the main routine of the application and
traps SystemExit.
I'd like to compare status of the ... -
04:24 PM Feature #5427: Not complex patch to improve `require` time (load.c)
- Currenly, I've update patch with fix from #5727
https://gist.github.com/1272991 -
- lazy assigned load_path searched in loading_table were not expanded
(http://redmine.ruby-lang.org/projects/ruby-trunk/repository/revisions/33027/entry/load.c#L186),
but all features, pushed to loading table, are expanded.
This bug ... -
03:27 PM Bug #5614: Proc#source_location & #inspect shows wrong line number when chained
- It may not a bug but a specification. A block returns the number of a line in which the block is defined for its "source_location." When you use procs instead of blocks, it returns the values you expected.
Code:
1 require 'pp'
2... -
- It seems read with length should always be binary mode. #5562 patch lacks this point.
I think this patch fixes above issue.
It seems OK that stdin is default binary mode, but if stdout and stderr are default binary mode, newline conv... -
10:23 AM Bug #5714: Unexpected error of STDIN#read with non-ascii input on Windows XP
- Hi,
2011/12/7 Hiroshi Shirosaki <h.shirosaki@gmail.com>
>
> >
> > - if (_osfile(fd) & FTEXT) {
> > + isconsole = is_console(_osfhnd(fd));
> > + if (!isconsole && (_osfile(fd) & FTEXT)) {
> > return _read(fd, buf... -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@33988 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- visibility is modified. [ruby-dev:44929]
* test/ruby/test_module.rb (test_private_constants_clear_inlinecache):
add test for it.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@33987 b2dd03c8-39d4-4d8f-98ff-823fe69b080e - 02:28 PM Revision f6a2a431 (git): * ext/extmk.rb (extract_makefile): should sort after map, not before
- it. in this case there is no difference, but we should write better
code. this bad smell was caught by nagachika.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@33986 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@33985 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- Just noting for the benefit of anyone else passing by that I posted a way to do popen3 with timeout at
https://gist.github.com/1032297 -
- In case it helps, I have a Gist with some working 1.9.3 code to perform a popen3 with time out, not using Timeout::timeout:
https://gist.github.com/1032297 - 01:34 PM Revision d9d841e3 (git): * ext/extmk.rb (extract_makefile): need to sort the array of current
- srcs before comparing to the sorted old srcs.
fixed the problem that the configuring stage of exts were always
run, introduced at r33801.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@33984 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@33983 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- This issue was solved with changeset r33978.
Heesob, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
----------
* configure.in (RUBY_WERROR_FLAG): append all warning flags whi... -
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@33982 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
10:25 AM Feature #2294: [PATCH] ruby_bind_stack() to embed Ruby in coroutine
- Hi
While looking for a solution to an issue we have with embedding ruby into a pthread I found this thread
We have been running ruby embedded into a pthread for about 10 years now and and have upgraded periodically. We recently moved f... -
10:01 AM Feature #5710 (Closed): Enumerable#each( :method ) and Enumerable#map( :method )
- closed at request of submitter
-
01:56 AM Feature #5710: Enumerable#each( :method ) and Enumerable#map( :method )
- It works. Thank you!
I guess that this issue has been resolved... -
- 2011/12/7 rommel nocando <redmine@ruby-lang.org>:
> Bug #5721: require_relative
> http://redmine.ruby-lang.org/issues/5721
>
> Our users have found that with synchronicity's (a revision control system) populating with -share... -
- =begin
I'm uncertain of your case.
I imagined the following case, but this works.
$ mkdir bin lib
$ echo 'p :foo' > lib/foo.rb
$ ln -s ../lib/foo.rb bin/
$ echo 'require_relative "foo"' > bin/a.rb
$ ruby bin/a.rb
:foo
=e... -
-
- I altered the wording on =~ mentioning Range and String because the operator is generic and may be overridden to perform other types of pattern matching.
-
- This issue was solved with changeset r33977.
Sylvain, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
----------
* doc/re.rdoc: Document difference between match and =~, opti... -
- This issue was solved with changeset r33976.
Jarno, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
----------
* doc/re.rdoc: Fix example code to match documentation. Patch ... -
- Hello,
I'm having problems building date_core.c with GCC 4.6 from mingw-w64 project: -
- What are the replacements for Complex.generic? and Numeric#im? I think these should be documented instead of just "Deprecated"
- 04:31 AM Revision 0bfa4abd (git): * test/rexml/test_order.rb (OrderTester#test_more_ordering): use
- GZip::GzReader.open instead of GZip::GzReader.new with File.new.
fixed a test error on Windows introduced at r33946.
* ChangeLog: mention the causes.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@33981 b2dd03c8-39d4-4d8f-98ff-82... - 04:12 AM Revision bb329872 (git): * test/ruby/test_process.rb (TestProcess#test_sete[gu]id): silently
- skip if not implemented such functions (such as, on Windows).
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@33980 b2dd03c8-39d4-4d8f-98ff-823fe69b080e - 03:59 AM Revision 2470d781 (git): * ext/socket/extconf.rb: forgotten to define HAVE_SOCKETPAIR for
- windows.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@33979 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- are enabled to compile, so that printf format modifiers properly
fail. [ruby-core:41351] [Bug #5679]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@33978 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
12/07/2011
-
- Regexp.new and global variables. Patch by Sylvain Daubert.
[Ruby 1.9 - Bug #5709]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@33977 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- Jarno Lamberg. [Ruby 1.9 - Bug #5624]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@33976 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- >
> - Â Â if (_osfile(fd) & FTEXT) {
> + Â Â isconsole -
- Hi,
(11/12/06 22:34), Luis Lavena wrote:
> BTW, I'm collecting stats about Ruby-users with Windows to determine
> the best option for that, can you spread the word?
>
> https://docs.google.com/spreadsheet/viewform?hl=en_US... -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@33975 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
- 10:13 PM Revision 253079bc (git): * 2011-12-08
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@33974 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- So skip until it is released.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@33973 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
09:59 PM Bug #5721 (Rejected): require_relative
- Our users have found that with synchronicity's (a revision control system) populating with -share option that the symbolic links break require_relative
bin/launchLib.rb:54:in `require_relative': no such file to load -- /blah/sync_cac... -
- This issue was solved with changeset r33970.
Gabriel, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
----------
* vm.c (vm_set_top_stack, vm_set_eval_stack): check for stack
... -
03:51 PM Bug #5720 (Closed): Exceptions can be caused via eval that evade exception handling
- While poking at #5719, I discovered it's possible to cause an exception via Kernel#eval that leaks through any surrounding rescue block. Please see the gist for details. I tested against 1.9.2-p290, 1.9.3-p0, and HEAD of the 1.9.3 branch...
-
- If you had enough of my comments on this thread, please tell me stop, i will listen.
Here is my another argument in favor of pure Set as a base class or replacement for Hash: on top of Set (or Hash modified in a way to be able to hold... -
- 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 a very long array created by a splash. At ht...
-
12:26 PM Bug #5719: Hash::[] can't handle 100000+ args
- i shall give you four hints: stack, heap, push, pop
ruby's behavior is expected.
you can pass Hash::[] an array instead i think.
Hash[[[:a, 1], [:b, 2]]] #=> {:a=>1, :b=>2} -
- Hi,
In message "Re: [ruby-core:41511] [ruby-trunk - Bug #5719][Open] Hash::[] can't handle 100000+ args"
on Wed, 7 Dec 2011 11:30:44 +0900, Nick Quaranto <nick@quaran.to> writes:
|I couldn't pin down an exact size for wh... -
- It looks to be a variable argument length thing, not a Hash thing in particular.
https://gist.github.com/5037bf83d28c2c119c44
Edit: Not just variable argument length. Ruby just won't have any of your guff if you intend on passing any m... -
11:47 AM Bug #5719: Hash::[] can't handle 100000+ args
- I was able to duplicate this issue with the above code in 1.9.2-p290 It didn't matter if I ran it through IRB or from the command line.
-
11:30 AM Bug #5719 (Closed): Hash::[] can't handle 100000+ args
- I couldn't pin down an exact size for when/how this occurs, but I have code that was creating hashes just fine with Hash::[] with 300k+ arguments.
irb(main):056:0> (0...140000).map { |n| [:a, n] }.tap { |a| Hash[*a] }.size
SystemStac... -
- This issue was solved with changeset r33969.
Sylvain, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
----------
* ext/bigdecimal/bigdecimal.c: Document +@, -@, hash, INFINIT... -
- This issue was solved with changeset r33968.
Misty, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
----------
* io.c (Init_IO): Mention io/console methods. [Ruby 1.9 - Bug ... -
- trans wrote:
> On Sunday, December 4, 2011 3:02:29 PM UTC-5, NARUSE, Yui wrote:
>>
>>
>> After some consideration, I'm wondering why following code is not used.
>> There is already a method or proc object in usual use case?
... -
- On Sunday, December 4, 2011 3:02:29 PM UTC-5, NARUSE, Yui wrote:
>
>
> After some consideration, I'm wondering why following code is not used.
> There is already a method or proc object in usual use case?
>
> begin
> obj... - 10:04 AM Revision 83d1eebb (git): * 2011-12-07
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/branches/ruby_1_9_3@33972 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- Yuji Yamano <yyamano AT kt.rim.or.jp> in [ruby-list:48568].
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@33971 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- Yuji Yamano <yyamano AT kt.rim.or.jp> in [ruby-list:48568].
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/branches/ruby_1_9_3@33971 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- overflow with stack_max before push new frame. [ruby-core:41520]
[Bug #5720]
* vm.c (vm_set_main_stack): no stack overflow chances after
vm_set_eval_stack().
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@33970 b2dd03c8-39d4-4d8f... -
- Patch by Sylvain Daubert. [Ruby 1.9 - Feature #5622]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@33969 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- * ext/io/console/console.c: Mention that io/console must be required
similar to lib/time.rb
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@33968 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- Indeed, I have aliased `#is` to `#include` and aliased `#is?` as `#===`
before
class Collection
is Enumerable
end
Collection.is? Enumerable
Which I find exceptionally readable. -
- FreeBSD PR: kern/155606, kern/162379
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@33967 b2dd03c8-39d4-4d8f-98ff-823fe69b080e