Activity
From 01/19/2011 to 01/25/2011
01/25/2011
-
11:18 PM Bug #4322 (Closed): valgrind report error for uncaught throw
- =begin
以下のようなスクリプトを valgrind を使って実行するとエラーが報告されます。
## script
GC.stress = true
throw :tag
## message
==1141== Conditional jump or move depends on uninitialised value(s)
==1141== at 0x40276EB: strlen (mc_replace_strmem... -
11:11 PM Bug #4321 (Closed): valgrind report "Invalid read" for Object#clone
- =begin
以下のようなスクリプトを valgrind を使って実行すると Invalid read of size 4 のようなエラーが報告されます。
optflags=-O3 を指定してビルドした時に発生します。
## script
obj = Object.new
def obj.meth
end
GC.stress = true
obj.clone
## message
==22864== Invalid... -
10:31 PM Bug #4320 (Closed): Bus Error in digest/sha2 on sparc
- =begin
Most likely this is caused due to misaligned memory. Any comment is greatly appreciated.
This bug can reproduce at Ruby 1.8, too.
ruby -e "require 'digest/sha2'; d= Digest::SHA256.new; ['a' * 97, 'a' * 97].each {|i| d.... -
10:05 PM Feature #4197: Improvement of the benchmark library
- =begin
This eases review: https://github.com/eregon/ruby/compare/trunk...benchmark
Konstantin
On Jan 25, 2011, at 13:14 , Benoit Daloze wrote:
> Issue #4197 has been updated by Benoit Daloze.
>
>
> Hi,
>
> Any update on... -
09:14 PM Feature #4197: Improvement of the benchmark library
- =begin
Hi,
Any update on this ?
Could you have a look, Koichi ?
(Or anyone, I welcome comments)
=end
-
04:40 PM Feature #4168: WeakRef is unsafe to use in Ruby 1.9
- =begin
On Mon, Jan 24, 2011 at 11:44 PM, Kurt Stephens <redmine@ruby-lang.org> wrote:
> * Support for multiple Reference subclass instance caches.
> * Working WeakReference, SoftReference and ReferenceQueue in ext/reference/reference... -
02:43 PM Feature #4168: WeakRef is unsafe to use in Ruby 1.9
- =begin
Progress: https://github.com/kstephens/ruby/commit/6f3f2a538455187d67ef504cfa266cf5789ca099
* Support for multiple Reference subclass instance caches.
* Working WeakReference, SoftReference and ReferenceQueue in ext/refere... -
11:14 AM Feature #4264: General type coercion protocol for Ruby
- =begin
On Wed, Jan 19, 2011 at 15:53, Charles Oliver Nutter
<headius@headius.com> wrote:
> They're not bad, but casting to me means something altogether
> different: treating a an object as a different type, while still
> referencin... -
08:44 AM Bug #4314: spwn cause Segmantation Fault if take a long string.
- =begin
Hi,
At Tue, 25 Jan 2011 07:44:51 +0900,
Motohiro KOSAKI wrote in [ruby-core:34842]:
> reproduce way.
>
> ./ruby -ve 'spawn "a"*100_000_000'
I propose new APIs for exception-safe temporary buffer.
diff --git i/inc... -
07:44 AM Bug #4314: spwn cause Segmantation Fault if take a long string.
- =begin
reproduce way.
./ruby -ve 'spawn "a"*100_000_000'
=end
-
07:37 AM Feature #4309: [ext/openssl] ASN1 performance enhancement
- =begin
>Sadly there is no maintainer for openssl currently, so it seems difficult
>for your patch to be reviewed certainly.
>I reviewed your patch simply, but note that I'm not familiar with openssl.
Thanks for your time!
... -
06:57 AM Bug #4319 (Closed): StringValueCStr() should terminate
- =begin
StringValueCStr()の結果が、NUL-terminateされていない場合があります。
=end
-
04:47 AM Bug #4318 (Closed): Legacy bug in net/imap in Ruby 1.9.x
- =begin
Emails that get 'appended' to a mailbox are cut-off
at the end. Not always but only in non-multipart mails where the headers
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
apply to the whol... -
12:16 AM Bug #4317 (Closed): File.stat cause Segmentation Fault if take a long string.
- =begin
following script will crash immediately.
C:\ruby\trunk\build>\ruby\bin\ruby -ve 'File.stat("a"*100_000_000)'
ruby 1.9.3dev (2011-01-23 trunk 30640) [i386-mswin32_100]
=end
-
12:13 AM Bug #4316 (Closed): Dir.new cause Segmentation Fault if take a long string.
- =begin
C:\ruby\trunk\build>\ruby\bin\ruby -ve 'Dir.new("a"*100_000_000)'
ruby 1.9.3dev (2011-01-23 trunk 30640) [i386-mswin32_100]
=end
-
12:08 AM Bug #4315 (Closed): Process.spawn cause Segmentation Fault if take a long string. (windows)
- =begin
test.rb
-------------------------
spawn '"a"|'*100_000_000
-------------------------
ruby ./test.rb
=end
01/24/2011
-
11:44 PM Bug #4314 (Closed): spwn cause Segmantation Fault if take a long string.
- =begin
ruby 1.9.3dev (2011-01-24 trunk 30642) [x86_64-linux]
-e:1: [BUG] Segmentation fault
ruby 1.9.3dev (2011-01-24 trunk 30642) [x86_64-linux]
-- Control frame information -----------------------------------------------
c:... -
11:42 PM Revision a0eeef69 (git): * dln_find.c (dln_find_1): omit too long pathnames.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@30653 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
11:28 PM Revision ced2d699 (git): * string.c (rb_str_resize): get rid of out-of-bound access.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@30652 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
11:23 PM Bug #4313: File.identical? cause Segmentation Fault if take a long string.
- =begin
It maybe windows only. I doubt w32_io_info makes stack overflow.
=end
-
11:20 PM Bug #4313 (Closed): File.identical? cause Segmentation Fault if take a long string.
- =begin
Following script crash immediately, But error log doesn't display at all.
---------------------------------------------------------------------
ruby -ve 'p File.identical?("a"*100_000_000, "a")'
ruby 1.9.3dev (2011-0... -
11:16 PM Feature #4309: [ext/openssl] ASN1 performance enhancement
- =begin
Hi,
2011/1/24 Martin Bosslet <redmine@ruby-lang.org>:
> recently I noticed that the method
>
> static int ossl_asn1_default_tag(VALUE obj)
Sadly there is no maintainer for openssl currently, so it seems difficult
for yo... -
10:26 AM Feature #4309: [ext/openssl] ASN1 performance enhancement
- =begin
Added tests that further assert behavior of OpenSSL::ASN1::default_tag/default_tag_class_of. Attachment replaces the first one.
=end
-
09:42 AM Feature #4309 (Closed): [ext/openssl] ASN1 performance enhancement
- =begin
Hi all,
recently I noticed that the method
static int ossl_asn1_default_tag(VALUE obj)
(in ossl_asn1.c) iterates through an internal array each time a default tag is to be looked up resulting in O(n) runtime
pe... -
10:50 PM Revision 9a4a8673 (git): * test/ruby/test_thread.rb: remove unused variables.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@30651 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
10:50 PM Revision fa6f4336 (git): * test/ruby/test_thread.rb (TestThread#test_condvar_nolock_2): get rid of method redefined.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@30650 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
10:50 PM Revision ff4085d6 (git): move under correct class
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@30649 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
10:00 PM Revision 7a6113d6 (git): * string.c (rb_string_value_cstr): rb_str_modify can change
- RSTRING_PTR.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@30648 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
09:47 PM Bug #4312: exec cause Segmentation fault if passing very long string
- =begin
Because rb_proc_exec() are using alloca and it can cause stack overflow. It shouldn't.
=end
-
09:45 PM Bug #4312 (Closed): exec cause Segmentation fault if passing very long string
- =begin
% ./ruby -ve 'exec "a"*100_000_000'
ruby 1.9.3dev (2011-01-24 trunk 30642) [x86_64-linux]
-e:1: [BUG] Segmentation fault
ruby 1.9.3dev (2011-01-24 trunk 30642) [x86_64-linux]
-- Control frame information -----------... -
09:12 PM Bug #4308: Wrong Bignum calculation in some case.
- =begin
#!/usr/bin/env ruby
class Array
def sum
reduce(:+)
end
def var
empty? ? 0.0 : (map {|x| x ** 2}.sum * size - sum ** 2).fdiv(size ** 2)
end
end
# All of these should clearly return 0.
... -
09:58 AM Bug #4308 (Rejected): Wrong Bignum calculation in some case.
- =begin
It seems from floating point's accuracy.
In line 9, it uses to_f and the value exceeds its limit.
=end
-
06:59 AM Bug #4308 (Rejected): Wrong Bignum calculation in some case.
- =begin
I tried to calculate variance of an array but calculation returns wrong result
when numbers are big.The problem also happens in 1.8.7-p330.
I attached a file that recreates The problem.
=end
-
09:07 PM Bug #4310 (Closed): String#% cause Segmentation fault on Windows
- =begin
This issue was solved with changeset r30641.
Heesob, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
----
* error.c (rb_invalid_str): prevent intermediate variabl... -
02:11 PM Bug #4310: String#% cause Segmentation fault on Windows
- =begin
=end
-
12:06 PM Bug #4310 (Closed): String#% cause Segmentation fault on Windows
- =begin
String#% cause Segmentation fault on Windows with trunk version in case of long string.
C:\work>ruby -ve 'p "%f"%("a"*10000000)'
ruby 1.9.3dev (2011-01-23 trunk 30640) [i386-mswin32_90]
-e:1: [BUG] Segmentation fault
r... -
06:25 PM Revision 68823fde (git): * test/ruby/test_thread.rb: Added various ConditionVariable tests.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@30647 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
- 06:23 PM Revision e9d8fd9b (git): * 2011-01-25
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@30646 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
06:23 PM Revision cab9751e (git): * object.c (rb_str_to_dbl): Fix again. use rb_str_tmp_new()
- instead ALLOC_N.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@30645 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
03:39 PM Bug #4311: ruby setup.sb fails to install ruby gems
- =begin
On Jan 23, 2011, at 19:56, Kent Paul Dolan <redmine@ruby-lang.org> wrote:
> After installing Ruby and downloading and unpacking
> Ruby Gems, I changed to the rubygems-1.4.2 directory
> (since no guidance had been given in th... -
12:55 PM Bug #4311 (Closed): ruby setup.sb fails to install ruby gems
- =begin
Ruby maintainers,
I don't know if this is a bug, or just user
incomprehension, but anyway...
After installing Ruby and downloading and unpacking
Ruby Gems, I changed to the rubygems-1.4.2 directory
(since no guida... -
12:51 PM Revision c11a4d8f (git): * vm_insnhelper.h: parenthesize macro arguments.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@30644 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
12:30 PM Revision 2ec31553 (git): * object.c (rb_str_to_dbl): use ALLOC_N instead ALLOCA_N because
- ALLOC_N may cause stack overflow.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@30643 b2dd03c8-39d4-4d8f-98ff-823fe69b080e - 12:04 PM Revision 76789bbb (git): * 2011-01-24
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@30642 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
12:04 PM Revision 97b8e499 (git): * error.c (rb_invalid_str): prevent intermediate variable from GC.
- [ruby-core:34820]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@30641 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
11:09 AM Bug #4298: Duration of calling String#[] with the same index is strangely related to string length.
- =begin
Thanks for the update. We will look into a cache in JRuby...
=end
-
10:09 AM Bug #4298: Duration of calling String#[] with the same index is strangely related to string length.
- =begin
Hi,
In message "Re: [ruby-core:34814] [Ruby 1.9-Bug#4298] Duration of calling String#[] with the same index is strangely related to string length."
on Mon, 24 Jan 2011 09:51:14 +0900, Thomas Enebo <redmine@ruby-lang.org> ... -
10:06 AM Bug #4298: Duration of calling String#[] with the same index is strangely related to string length.
- =begin
2011/1/24 Thomas Enebo <redmine@ruby-lang.org>:
> Marcin and I were wondering the other day why character length is not cached in the string. It seems whenever code range has to be updated str length cache could also be updated... -
09:51 AM Bug #4298: Duration of calling String#[] with the same index is strangely related to string length.
- =begin
Marcin and I were wondering the other day why character length is not cached in the string. It seems whenever code range has to be updated str length cache could also be updated with little extra cost. Is there a thread that ex... -
09:19 AM Bug #4298: Duration of calling String#[] with the same index is strangely related to string length.
- =begin
JRuby does need a similar fix. I filed http://jira.codehaus.org/browse/JRUBY-5411 to cover it.
=end
-
07:38 AM Bug #4298: Duration of calling String#[] with the same index is strangely related to string length.
- =begin
I think it's worth pointing out that Nobu's fix does not prevent String#[] from needing to do a character scan to reach the nth character, but it does fix the issue of always scanning all characters.
I'll check if JRuby need... -
08:02 AM Bug #4307: include fails after undef_method
- =begin
So it was a misunderstanding of #undef_method that led me to not expect the
actual behaviour. Thanks for the clarification.
I read the documentation and understood the difference between undef_method and
remove_method, b... -
05:10 AM Bug #4307: include fails after undef_method
- =begin
On 1/23/2011 2:14 PM, Adriano Mitre wrote:
> After using #undef_method on a method "inherited" from a mixin, reincluding the mixin should redefine it, but that is not what happens.
>
This seems like expected behaviour to... -
04:14 AM Bug #4307 (Rejected): include fails after undef_method
- =begin
After using #undef_method on a method "inherited" from a mixin, reincluding the mixin should redefine it, but that is not what happens.
Please take a look at this short IRB transcript (source attached):
>> module Foo; ... -
06:10 AM Bug #4301: Off-by-one line number in Psych parse error
- =begin
FYI, 1.8/syck parses the yaml shown here, but libyaml (and SnakeYAML) do not (correctly). Ran into it because it's in a file that ships with RedCar:
https://redcar.lighthouseapp.com/projects/25090/tickets/464-redcar-ships-a-...
01/23/2011
-
02:03 PM Revision b9c0b503 (git): * test/io/console/test_io_console.rb: Don't run test if the system
- don't support io/console.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@30640 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
01:20 PM Revision 99ef8670 (git): * test/fiddle/test_fiddle.rb: Don't run test if the system don't support
- fiddle.
* test/fiddle/test_function.rb: ditto.
* test/fiddle/test_closure.rb: ditto.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@30639 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
09:34 AM Bug #4306 (Rejected): psych makes a lot of test failure on Win32 build
- =begin
I'm sorry. Yes, rebuild and retest work perfectly.
Therefore I'll close this ticket.
Thanks.
=end
-
07:52 AM Bug #4306: psych makes a lot of test failure on Win32 build
- =begin
On Sun, Jan 23, 2011 at 01:41:47AM +0900, Motohiro KOSAKI wrote:
> Bug #4306: psych makes a lot of test failure on Win32 build
> http://redmine.ruby-lang.org/issues/show/4306
>
> Author: Motohiro KOSAKI
> Status: Open, Prio... -
01:41 AM Bug #4306 (Rejected): psych makes a lot of test failure on Win32 build
- =begin
Latest trunk makes a lot of test failure of 'nmake test-all' on win32 platform.
----------------------------------------------------------------------------
5) Error:
test_mapping(Psych::Nodes::TestEnumerable):
NoMet... -
08:27 AM Bug #4298 (Closed): Duration of calling String#[] with the same index is strangely related to string length.
- =begin
This issue was solved with changeset r30636.
Radosław, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
----
* string.c (str_nth_len, str_utf8_nth): return the res... -
08:06 AM Bug #4298: Duration of calling String#[] with the same index is strangely related to string length.
- =begin
Hi,
2011/1/23 Charles Nutter <redmine@ruby-lang.org>:
> Issue #4298 has been updated by Charles Nutter.
>
>
> Perhaps I'm mistaken, but isn't RSTRING_LEN the byte length of the string? Isn't that always guaranteed to be >=... -
08:00 AM Bug #4298: Duration of calling String#[] with the same index is strangely related to string length.
- =begin
Hi,
In message "Re: [ruby-core:34793] [Ruby 1.9-Bug#4298] Duration of calling String#[] with the same index is strangely related to string length."
on Sun, 23 Jan 2011 03:42:20 +0900, Charles Nutter <redmine@ruby-lang.org... -
03:42 AM Bug #4298: Duration of calling String#[] with the same index is strangely related to string length.
- =begin
Perhaps I'm mistaken, but isn't RSTRING_LEN the byte length of the string? Isn't that always guaranteed to be >= str_strlen, which is the character length? And doesn't this patch basically break completely if beg is greater than ... -
07:47 AM Bug #4303 (Third Party's Issue): Segmentation fault (using tarantula and hpricot)
- =begin
=end
-
07:44 AM Bug #4301 (Open): Off-by-one line number in Psych parse error
- =begin
Reopening as this seems like a bug in libyaml.
=end
-
07:41 AM Bug #4301: Off-by-one line number in Psych parse error
- =begin
On Sat, Jan 22, 2011 at 05:23:35PM +0900, Charles Nutter wrote:
> Issue #4301 has been updated by Charles Nutter.
>
>
> Hmm, I think there's more to this, and it could certainly be a bug in libyaml. The following version ha... -
02:39 AM Revision 35dbe505 (git): * vm_exec.h: parenthesize macro arguments.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@30638 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
01:32 AM Revision 6df02103 (git): * template/fake.rb.in (ruby): suppress warnings.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@30637 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
01:09 AM Bug #4305 (Rejected): Win32 上で bignum の test_too_big_to_s が失敗
- =begin
Win32上で test-allすると以下のfailureが出ます
-------------------------------------------------------------------------
22) Failure:
test_too_big_to_s(TestBignum) [C:/ruby/trunk/test/ruby/test_bignum.rb:404]:
[RangeError] excepti... -
01:07 AM Bug #4304 (Rejected): Win32上でfiber大量生成テストが失敗
- =begin
現在、win32でtest-all すると以下のエラーがでます
--------------------------------------------------------------------------
25) Error:
test_many_fibers_with_threads(TestFiber):
ThreadError: can't create Thread (12)
C:/ruby/trun...
01/22/2011
-
11:17 PM Revision 734b6151 (git): * string.c (str_nth_len, str_utf8_nth): return the rest length together.
- * string.c (rb_str_substr): get rid of measure the length always
to improve performance for huge string. [ruby-core:34648]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@30636 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
11:00 PM Revision b0eaf0f6 (git): * string.c (str_nth_len, str_utf8_nth): return the rest length together.
- * string.c (rb_str_substr): get rid of measure the length always
to improve performance for huge string.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@30635 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
10:47 PM Bug #4303: Segmentation fault (using tarantula and hpricot)
- =begin
This turned out to be an issue with hpricot 0.8.3. Using an older
version of hpricot solved the problem. Sorry for spamming.
=end
-
10:43 PM Revision 18e3c52b (git): reverting r30628 since this seems like a bug in libyaml
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@30634 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
10:11 PM Bug #4298: Duration of calling String#[] with the same index is strangely related to string length.
- =begin
This bug(or feature) is due to the repetitive calling of str_strlen() function.
Here is a sentry patch for rb_str_substr() function of string.c
--- string.c 2011-01-22 21:25:38.000000000 +0900
+++ string.c.new 2011-01... -
05:23 PM Bug #4301: Off-by-one line number in Psych parse error
- =begin
Hmm, I think there's more to this, and it could certainly be a bug in libyaml. The following version has the *correct* line number, without your patch:
~ ➔ ruby -rpsych -ryaml -e 'YAML.parse("---\nldquor: ,,")'/Users/headius... -
11:27 AM Bug #4301 (Closed): Off-by-one line number in Psych parse error - =begin
This issue was solved with changeset r30628.
Charles, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
----
* ext/psych/parser.c (parse): fixing off-by-one error o... - 03:46 PM Revision 8135c466 (git): * 2011-01-23
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@30633 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
03:46 PM Revision fe505c47 (git): * test/test_syslog.rb: Fix to make a lot of test failure if
- the platform doesn't support syslog.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@30632 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
02:42 PM Revision d21bc2f8 (git): * properties.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@30631 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
11:37 AM Bug #4300 (Closed): Merge keys not working as expected in psych yaml parser - =begin
This issue was solved with changeset r30629.
Matthew, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
----
* ext/psych/lib/psych/visitors/to_ruby.rb: merge keys a... -
11:27 AM Bug #4297 (Closed): test_time in ruby/test/psych/test_json_tree.rb makes test failure - =begin
This issue was solved with changeset r30627.
Motohiro, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
----
fixed a bug in the test suite. Thanks Benoit Daloze! ... -
02:51 AM Revision 6e5aa631 (git): * ext/psych/lib/psych/visitors/to_ruby.rb: fixing merge key support
- when multiple merge keys are specified.
* test/psych/test_merge_keys.rb: tests for multi-merge key support
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@30630 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
02:34 AM Revision 5b1c06c7 (git): * ext/psych/lib/psych/visitors/to_ruby.rb: merge keys are actually
- part of YAML 1.1, so they should be supported. Remove warning and
merge keys to parent. [ruby-core:34679]
* test/psych/test_merge_keys.rb: test for merge keys
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@30629 b2dd03c8-39d4-4d8... -
02:23 AM Revision 7b876e65 (git): * ext/psych/parser.c (parse): fixing off-by-one error on line numbers
- in parse exceptions. [ruby-core:34690]
* test/psych/test_parser.rb: test for error
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@30628 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
02:18 AM Revision cab95ab7 (git): fixed a bug in the test suite. Thanks Benoit Daloze! [ruby-core:34641]
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@30627 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
01:26 AM Revision 8dd3a4af (git): * ext/psych/parser.c (parse): add the file name to the exception when
- parse errors occur.
* test/psych/test_parser.rb: test for parse error file name
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@30626 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
01:13 AM Revision 0331314d (git): * ext/psych/parser.c (parse): fix assertion error when reusing a
- parser after an exception has been raised
* test/psych/test_parser.rb: test for assertion error
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@30625 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
12:36 AM Bug #4294: IO.popen ['"ping"', 'localhost -n 3'] fails
- =begin
Absolutely agree to Usaku: the whole point of the Array variant of IO.popen is to *not* need to quote strings. Quoting in the string form is only needed for the implementation to be able to rip arguments properly apart in light ...
01/21/2011
-
09:05 PM Feature #4288: Allow invoking arbitrary method names with foo."something" syntax
- =begin
Em 21-01-2011 07:37, Charles Oliver Nutter escreveu:
> On Fri, Jan 21, 2011 at 2:50 AM, Stephen Sykes<sdsykes@gmail.com> wrote:
>> Yes, agree, if you want interpolation you can use send.
>>
>> But using double quotes leads... -
06:38 PM Feature #4288: Allow invoking arbitrary method names with foo."something" syntax
- =begin
On Fri, Jan 21, 2011 at 2:50 AM, Stephen Sykes <sdsykes@gmail.com> wrote:
> Yes, agree, if you want interpolation you can use send.
>
> But using double quotes leads to an expectation of interpolation does it not?
> So would ... -
05:50 PM Feature #4288: Allow invoking arbitrary method names with foo."something" syntax
- =begin
> It does, but my concern with it is that (in the same way as
> string-interpolated ."" syntax) it can't be made 100% parse-time. So I
> think the questions to be answered are (in this order):
>
> 1. Do we feel it's useful to... -
06:39 AM Feature #4288: Allow invoking arbitrary method names with foo."something" syntax
- =begin
On Wed, Jan 19, 2011 at 6:03 PM, Gary Wright <gwtmp01@mac.com> wrote:
> I probably wasn't clear. I also don't want syntactic sugar for #send
> but instead a way to dynamically name a method without the extra step
> of looking ... -
08:59 PM Bug #4303 (Feedback): Segmentation fault (using tarantula and hpricot)
- =begin
Could you try again at ruby-trunk without rvm?
See also: http://redmine.ruby-lang.org/wiki/ruby/HowtoReport
=end
-
08:26 PM Bug #4303 (Third Party's Issue): Segmentation fault (using tarantula and hpricot)
- =begin
I get this this segmentation fault when running tarantula tests for a rails application. I don't know if the bug is in ruby or hpricot or something else. I cannot provide a small test case to reproduce it because to me it seems t... -
07:11 PM Revision 960720ef (git): * ext/psych/lib/psych/nodes/node.rb: Make Psych::Nodes::Node
- enumerable.
* ext/psych/lib/psych/visitors/depth_first.rb: Add a depth-first
visitor to enumerate over a YAML AST in a depth-first fashion
* test/psych/nodes/test_enumerable.rb: test for enumerating nodes
* test/psych/visitors/test_dep... - 03:54 PM Revision 5f710e22 (git): * 2011-01-22
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@30623 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
03:54 PM Revision 741e7788 (git): * vm_core.h: parenthesize macro arguments.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@30622 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
11:41 AM Feature #4257: switch_hitter - an acceleration of date library
- =begin
Looks good. The only thing I noticed is that DateTime#amjd is broken:
$ ruby -v -r date -e 'DateTime.new.amjd'
ruby 1.9.3dev (2011-01-21 trunk 30620) [x86_64-openbsd4.8]
-e:1:in `amjd': undefined method `amjd_r' for #<D... -
11:29 AM Bug #4294: IO.popen ['"ping"', 'localhost -n 3'] fails
- =begin
Thank you Usaku,
I can take what you've said if that's what Ruby Spec has specified.
I just don't know where to find the respective spec,
the ruby-doc[1] doesn't have such words
[1] http://ruby-doc.org/core/cl... -
09:41 AM Feature #4168: WeakRef is unsafe to use in Ruby 1.9
- =begin
Ok, I see why Brian's reference queue doesn't have the same restrictions as the JVM's: it isn't triggered by the reference, it's triggered by the finalizer attached to the object.
There's a lot of other stuff here, so I'm no... -
08:38 AM Feature #4168: WeakRef is unsafe to use in Ruby 1.9
- =begin
I'm not sure I see any real benefit to caching the WeakReference and SoftReference objects themselves. Indeed, it may be undesirable to not be guaranteed you're going to have a fresh reference, since there may be multiple places ... -
04:17 AM Feature #4168: WeakRef is unsafe to use in Ruby 1.9
- =begin
Charles:
I've been using Brian's ref gem as a starting point for a proposed standard API; for example: WeakReference and SoftReference are subclasses of Reference.
I probably should have done this at the start, but I wi... -
09:34 AM Bug #4301 (Third Party's Issue): Off-by-one line number in Psych parse error
- =begin
For the following yaml:
# based on "SGML/XML character entity reference" at http://www.bitjungle.com/isoent/
#
---
#DOUBLE LOW-9 QUOTATION MARK
#requires fontenc:T1
ldquor: ,,
Psych produces the following err... -
09:27 AM Bug #3889 (Closed): Incorrectly detected i686-w64-mingw32 as x64-mingw
- =begin
This issue was solved with changeset r30620.
Luis, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
----
* configure.in: Fix incorrectly detected x86_64-w64-mingw3... -
09:15 AM Revision 85f8c01a (git): * configure.in: should not use -Werror=* flags while conftests.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@30621 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
04:19 AM Bug #4300 (Assigned): Merge keys not working as expected in psych yaml parser
- =begin
=end
-
04:10 AM Bug #4300 (Closed): Merge keys not working as expected in psych yaml parser
- =begin
Psych doesn't seem to support merge keys ( http://yaml.org/type/merge.html ) with alias/anchor the same way that syck does. I'm not sure if this is intentional or not, but its a pretty useful behavior so I'm filing a bug. Basi... -
12:46 AM Bug #4287: test_europe_lisbon(TestTimeTZ) Failure
- =begin
まつもと ゆきひろです
In message "Re: [ruby-dev:43085] Re: [Ruby 1.9-Bug#4287] test_europe_lisbon(TestTimeTZ) Failure"
on Fri, 21 Jan 2011 00:28:42 +0900, nagachika <nagachika00@gmail.com> writes:
|
|近永と申します。
|
|対応して頂いてありがとうござい... -
12:30 AM Bug #4287: test_europe_lisbon(TestTimeTZ) Failure
- =begin
近永と申します。
対応して頂いてありがとうございます。
> ところで、Chikanaga がコミット権を取得して自分でチェックインするのがみんなが幸せになれると
> 思うですが、どうでしょうか。
小さな不具合に気がついた時に毎回コミッタのかたの手を煩わすのも気が引けるものがありますので、
もし許可していただけるものならコミット権限を頂きたいと思います。
いかがでしょうか?
=end
-
12:18 AM Revision 89bd00d8 (git): * configure.in: Fix incorrectly detected x86_64-w64-mingw32 due
- canonalization of target_os. Bug #3889 [ruby-core:32634]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@30620 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
01/20/2011
-
08:45 PM Bug #4297: test_time in ruby/test/psych/test_json_tree.rb makes test failure
- =begin
On 20 January 2011 05:05, Motohiro KOSAKI <redmine@ruby-lang.org> wrote:
> % svn diff
> Index: test/psych/test_json_tree.rb
> ===================================================================
> --- test/psych/test_json_tree... -
01:06 PM Bug #4297: test_time in ruby/test/psych/test_json_tree.rb makes test failure
- =begin
=end
-
01:05 PM Bug #4297 (Closed): test_time in ruby/test/psych/test_json_tree.rb makes test failure
- =begin
Recently ruby trunk + linux increase one test failure.
--------------------------------------------------------------------------------
1) Failure:
test_time(Psych::TestJSONTree) [/home/kosaki/linux/ruby-svn/ruby/test/... -
08:10 PM Feature #4299 (Closed): no warning: found = in conditional, should be ==
- =begin
http://d.hatena.ne.jp/nagachika/20110119/ruby_trunk_changes_30595_30603
で知ったのですが、右辺の種類によっては「warning: found = in conditional, should be ==」が出ないことがあるようです。
% ruby-trunk -ve '!_=""'
ruby 1.9.3dev (2011-01-20 trunk 30614) [i... -
06:28 PM Bug #4298: Duration of calling String#[] with the same index is strangely related to string length.
- =begin
I copied&pasted wrong info about ruby's version. It's actually:
$ ruby-trunk -v
ruby 1.9.3dev (2010-09-06 trunk 29190) [x86_64-darwin10.4.0]
=end
-
06:21 PM Bug #4298 (Closed): Duration of calling String#[] with the same index is strangely related to string length.
- =begin
The longer string is the slower is String#[] (for the same index > 0). See the example benchmark below:
-
03:40 PM Revision 7fd0d4a4 (git): revert unrelated fix from r30615. Sorry!
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@30619 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
03:38 PM Revision c940b393 (git): * configure.in: Fix rb_cv_va_args_macro was broken. We are using
- -Werror=implicit-function-declaration compile option. therefore
we need a function declaration explicitly.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@30618 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
03:35 PM Bug #4256: [BUG] Segmentation fault ruby 1.9.2p0 (2010-08-18) [i386-mingw32]
- =begin
Hi all,
The issue was resolved when we uninstalled IE7 and installed IE6. We want know if there is any compatibility issues of Ruby 1.9.2 and the other installed gems, with IE7.
The same code however, is working with R... -
03:25 PM Bug #4294: IO.popen ['"ping"', 'localhost -n 3'] fails
- =begin
Hello,
In message "[ruby-core:34642] [Ruby 1.9-Bug#4294] IO.popen ['"ping"', 'localhost -n 3'] fails"
on Jan.20,2011 13:49:00, <redmine@ruby-lang.org> wrote:
> Right, the case became more obvious when we're running comma... -
01:48 PM Bug #4294: IO.popen ['"ping"', 'localhost -n 3'] fails
- =begin
Right, the case became more obvious when we're running commands whose path contains spaces.
In 1.8.7 IO.popen only support cmd_string, not cmd_array, anyway, the respective form IO.popen '"ping" -n 3 localhost' works, and th... -
02:36 AM Bug #4294: IO.popen ['"ping"', 'localhost -n 3'] fails
- =begin
Perhaps the OP was really concerned about things not on PATH and in dirs with spaces.
FWIW, the following works for me on Win7 32-bit for MRI 1.9.2p160 and 1.9.3dev r30603 (i386-mingw32) but not JRuby 1.6.0.RC1 in --1.9 mode... -
01:57 AM Bug #4294: IO.popen ['"ping"', 'localhost -n 3'] fails
- =begin
How is that a bug ? If ping is surrounded by quotes, ruby will look for an executable named "ping" with the quotes around. If ruby starts to magically remove these quotes, I'm not sure it will bring other unwanted side-effect. Bu... -
12:54 AM Bug #4294 (Closed): IO.popen ['"ping"', 'localhost -n 3'] fails
- =begin
>> RUBY_VERSION
=> "1.9.2"
>> RUBY_PLATFORM
=> "i386-mingw32"
>> IO.popen ['"ping"', 'localhost -n 3']
Errno::EINVAL: Invalid argument - "ping"
from (irb):6:in `popen'
from (irb):6
from d:... - 03:00 PM Revision 3c1b996a (git): * 2011-01-21
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@30617 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
02:59 PM Revision 6bc19376 (git): * node.h: parenthesize macro arguments.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@30616 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
02:34 PM Revision d41d2f26 (git): * configure.in: Add '#include <stdlib.h>' to
- rb_cv_localtime_overflow test too. It's reported by Tomoyuki
Chikanaga. Thanks.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@30615 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
01:52 PM Bug #4287: test_europe_lisbon(TestTimeTZ) Failure
- =begin
> いつもありがとうございます。Linuxとのことなのでこちらでコミットさせていただきました。
> ところで、Chikanaga がコミット権を取得して自分でチェックインするのがみんなが幸せに
Chikanaga-san が。
英語と日本語と行ったり来たりしてると言葉が無茶苦茶になりますね。反省
=end
-
12:37 PM Bug #4287 (Closed): test_europe_lisbon(TestTimeTZ) Failure
- =begin
This issue was solved with changeset r30612.
Tomoyuki, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
----
* configure.in: Add stdlib.h inclusion into rb_cv_nega... -
12:30 PM Bug #4287: test_europe_lisbon(TestTimeTZ) Failure
- =begin
いつもありがとうございます。Linuxとのことなのでこちらでコミットさせていただきました。
ところで、Chikanaga がコミット権を取得して自分でチェックインするのがみんなが幸せになれると
思うですが、どうでしょうか。
=end
-
11:56 AM Bug #4287 (Assigned): test_europe_lisbon(TestTimeTZ) Failure
- =begin
=end
-
01:02 PM Bug #4283: Timeout.timeout may cause application exit unintetionally
- =begin
Hi,
2011/1/20 Charles Oliver Nutter <headius@headius.com>:
> So I repeat: JRuby implements kill and raise using a mechanism similar
> to cancellation points, and those points occur at roughly the same
> places during execut... -
06:58 AM Bug #4283: Timeout.timeout may cause application exit unintetionally
- =begin
On Wed, Jan 19, 2011 at 4:32 AM, Yusuke ENDOH <mame@tsg.ne.jp> wrote:
> I guess that you misunderstand cancellation points. They do not mean
> context-switch boundaries.
I think you misunderstood me. I know what cancellatio... -
09:16 AM Feature #4264: General type coercion protocol for Ruby
- =begin
Em 19-01-2011 19:53, Charles Oliver Nutter escreveu:
> On Wed, Jan 19, 2011 at 5:54 AM, Rodrigo Rosenfeld Rosas
> <rr.rosas@gmail.com> wrote:
>> I like the cast_to/cast_from names and I guess it avoids conflict with most
>... -
06:57 AM Feature #4264: General type coercion protocol for Ruby
- =begin
On Wed, Jan 19, 2011 at 5:54 AM, Rodrigo Rosenfeld Rosas
<rr.rosas@gmail.com> wrote:
> I like the cast_to/cast_from names and I guess it avoids conflict with most
> libraries.
They're not bad, but casting to me means someth... -
08:13 AM Feature #4288: Allow invoking arbitrary method names with foo."something" syntax
- =begin
On Wed, Jan 19, 2011 at 8:53 AM, Nikolai Weibull <now@bitwi.se> wrote:
> And, as demonstrated, isn’t #send good enough?
* It's longer :)
* It defeats optimization, since you have to bounce through a "send"
call to get to th... -
08:13 AM Feature #4288: Allow invoking arbitrary method names with foo."something" syntax
- =begin
On Wed, Jan 19, 2011 at 2:58 PM, Gary Wright <gwtmp01@mac.com> wrote:
> Maybe I'm crazy, but could I suggest something a little more general?
>
> foo.{expression}(arg1)
>
> to have the same semantics as
>
> foo.send(exp... -
06:23 AM Feature #4288: Allow invoking arbitrary method names with foo."something" syntax
- =begin
On Wed, Jan 19, 2011 at 21:58, Gary Wright <gwtmp01@mac.com> wrote:
> On Jan 18, 2011, at 12:51 AM, Charles Nutter wrote:
>> For non-standard or arbitrary method names, it would be nice to have a way to invoke them directly t... -
08:04 AM Revision cffda96b (git): fix typos
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@30614 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
07:18 AM Feature #4168: WeakRef is unsafe to use in Ruby 1.9
- =begin
More comments:
* On JVM, you can only specify a ReferenceQueue to the constructor of a Reference. You cannot change or add queues on already-created references. JRuby would not be able to support adding new reference queues ... -
07:02 AM Feature #4168: WeakRef is unsafe to use in Ruby 1.9
- =begin
FYI, on the JVM it is not possible to use an arbitrary collection for reference enqueuing, and I think there's a good reason for it: calling back into user code while enqueuing a reference is probably not a good idea.
The JV... - 07:13 AM Revision 74535bd6 (git): * README.EXT, README.EXT.ja: You shouldn't choose ``conftest.c'' as a
- name of a source file.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@30613 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
04:51 AM Bug #3967: rdoc generates bad HTML output for '...' in parameter list, call-seq: with multiple values
- =begin
Back-ref: #4149 can be resolved once this is fixed.
=end
-
03:27 AM Revision 1a3950e2 (git): * configure.in: Add stdlib.h inclusion into rb_cv_negative_time_t
- test becuase it's required for exit(3). The patch is
created by Tomoyuki Chikanaga. [Bug #4287] [ruby-dev:43060]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@30612 b2dd03c8-39d4-4d8f-98ff-823fe69b080e - 02:41 AM Revision a9f76259 (git): * test/webrick/utils.rb (TestWEBrick::RubyBin): test CGI does not need
- to load rubygems. if it activated, ruby raises LoadError about
rbconfig.rb.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@30611 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
12:20 AM Revision 74b0a7a0 (git): * ext/psych/lib/psych/visitors/json_tree.rb: Fix JSON emit for
- DateTime and Time classes.
* test/psych/test_json_tree.rb: test for JSON emit
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@30610 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
01/19/2011
-
11:53 PM Feature #4288: Allow invoking arbitrary method names with foo."something" syntax
- =begin
On Wed, Jan 19, 2011 at 14:56, Austin Ziegler <halostatue@gmail.com> wrote:
> On Tue, Jan 18, 2011 at 12:51 AM, Charles Nutter <redmine@ruby-lang.org> wrote:
>> This syntax would make it easier to integrate with other languag... -
11:13 PM Feature #4288: Allow invoking arbitrary method names with foo."something" syntax
- =begin
On Tue, Jan 18, 2011 at 12:51 AM, Charles Nutter <redmine@ruby-lang.org> wrote:
> This is one Groovy feature I tend to like.
[…]
> This syntax would make it easier to integrate with other languages that have different
> n... -
03:45 AM Feature #4288 (Assigned): Allow invoking arbitrary method names with foo."something" syntax
- =begin
=end
-
11:05 PM Revision a17cdfdd (git): * ext/psych/lib/psych/coder.rb (represent_object): arbitrary objects
- may be passed to the Psych::Coder object.
* ext/psych/lib/psych/visitors/yaml_tree.rb: support for visiting
arbitrary objects set on the coder.
* test/psych/test_coder.rb: supporting test case.
git-svn-id: svn+ssh://ci.ruby-lang.org/r... -
10:42 PM Feature #4168: WeakRef is unsafe to use in Ruby 1.9
- =begin
Progress:
* Implementation of reference queue core protocol in C. Works with any object that respond_to?(:push).
* Nasty HACKS due to MRI GC clobbering of RBASIC(obj)->flags to handle deferred free lists. Would love to u... -
01:33 PM Feature #4168: WeakRef is unsafe to use in Ruby 1.9
- =begin
Progress:
* Prototype for C SoftReference as requested by Brian.
* Refactored code to use a rb_reference data structure.
https://github.com/kstephens/ruby/commit/c5ab0bf789089d08ddc549d5d9950addeeb41943
=end
-
06:54 AM Feature #4168: WeakRef is unsafe to use in Ruby 1.9
- =begin
FWIW, "ref" is the namespace Java uses (java.lang.ref.WeakReference). Since Ruby's namespaces are shorter, I'd almost prefer Reference::WeakReference, but I'll abstain from the naming discussion.
=end
-
03:26 AM Feature #4168: WeakRef is unsafe to use in Ruby 1.9
- =begin
Progress:
* Moved weakref.c into ext/weak_reference/weak_reference.c via a simple gc_api.c callback manager. Class is now named WeakReference.
* Suggestions/comments on gc_api.c and its semantics are greatly appreciated. F... - 09:23 PM Revision 64847a9c (git): Importing rubygems @ c2d4131: Deal with platforms that have DLEXT2 == nil. Fixes RF#28867
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@30608 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
- 09:03 PM Revision df2762fb (git): * 2011-01-20
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@30607 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
09:03 PM Revision 63d5d7f5 (git): * method.h: parenthesize macro arguments.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@30606 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
08:55 PM Feature #4264: General type coercion protocol for Ruby
- =begin
On 19-01-2011 08:05, mathew wrote:
> On Tue, Jan 11, 2011 at 10:26, Charles Nutter<redmine@ruby-lang.org> wrote:
>> Issue #4264 has been updated by Charles Nutter.
>>
>>
>> I like #to better as well, but isn't it too gene... -
07:06 PM Feature #4264: General type coercion protocol for Ruby
- =begin
On Tue, Jan 11, 2011 at 10:26, Charles Nutter <redmine@ruby-lang.org> wrote:
> Issue #4264 has been updated by Charles Nutter.
>
>
> I like #to better as well, but isn't it too generic a name, sure to conflict with libraries
... -
07:34 PM Bug #4283: Timeout.timeout may cause application exit unintetionally
- =begin
Hi,
2011/1/19 Charles Oliver Nutter <headius@headius.com>:
> JRuby implements Thread#raise and #kill using exactly this mechanism.
> On boundaries roughly equivalent to MRI 1.8's thread context switches,
> we ping thread st... -
03:21 PM Bug #4283: Timeout.timeout may cause application exit unintetionally
- =begin
On Tue, Jan 18, 2011 at 10:00 PM, Yusuke ENDOH <mame@tsg.ne.jp> wrote:
> This is not just a problem of Thread#raise. Asynchronous signals
> (such as Interrupt caused by Ctrl+C) have the same problem.
> Of course, we cannot re... -
01:13 PM Bug #4283: Timeout.timeout may cause application exit unintetionally
- =begin
Hi,
2011/1/19 Charles Nutter <redmine@ruby-lang.org>:
> I tried to patch this many times, and it's very difficult. The problem here is that kill is inherently broken in the presence of an ensure block. I've discussed this on ... -
06:44 AM Bug #4283: Timeout.timeout may cause application exit unintetionally
- =begin
We also have a "load test" for Timeout here: https://github.com/jruby/jruby/blob/master/test/load/load_timeout.rb
This should run to completion,only ever printing "ok" or "timeout". Instead, all versions of MRI I tested will... -
06:37 AM Bug #4283: Timeout.timeout may cause application exit unintetionally
- =begin
I tried to patch this many times, and it's very difficult. The problem here is that kill is inherently broken in the presence of an ensure block. I've discussed this on ruby-core emails in the past and on my blog here: http://blo... -
01:00 PM Bug #4285: Ruby don't have asynchrounous exception safe syntax and It should have.
- =begin
Hi,
2011/1/19 Charles Nutter <redmine@ruby-lang.org>:
> I tried to patch this many times, and it's very difficult. The problem here is that kill is inherently broken in the presence of an ensure block. I've discussed this on ... -
06:49 AM Bug #4285: Ruby don't have asynchrounous exception safe syntax and It should have.
- =begin
It is not possible to make cross-thread exception-raising safe with current Ruby semantics.
See the discussion on my blog post here: http://blog.headius.com/2008/02/rubys-threadraise-threadkill-timeoutrb.html
No matter ... -
02:25 AM Bug #4285: Ruby don't have asynchrounous exception safe syntax and It should have.
- =begin
Actually, protecting from async exceptions in the ensure block would
be mostly backward-compatible. It means that while a thread is in that
part of the code, no other thread would be running. Only code that
will break, would b... -
01:54 AM Bug #4285: Ruby don't have asynchrounous exception safe syntax and It should have.
- =begin
2011/1/18 Yusuke ENDOH <mame@tsg.ne.jp>:
> Basically agreed, but what is needed actually?
I think that ensure blocks should protect us from async exceptions.
They're here to make sure some part of a code is executed, that sh... -
12:22 PM Bug #4238 (Closed): GC.stress 下で OptionParser で設定のない引数をパースさせると core
- =begin
直ったとのことなので代理コミットしときました。Chikanagaさんは早くまつもとさんに言ってコミット権をもらうべきだと思います。
=end
-
10:21 AM Bug #4238: GC.stress 下で OptionParser で設定のない引数をパースさせると core
- =begin
note-2 のパッチで私のほうでも SEGV が起きなくなりました。
=end
- 08:40 AM Revision 0d672545 (git): * 2011-01-19
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/branches/ruby_1_8@30605 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
- 08:40 AM Revision 896e7a06 (git): * win32/win32.c (init_stdhandle): backport mistake of r29382.
- some code are needless in ruby 1.8.
[ruby-core:34579]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/branches/ruby_1_8@30604 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
04:17 AM Revision 4993a1a8 (git): Finish removing code, (fixes sources command test).
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@30603 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
03:41 AM Bug #4291: rb_time_new with negative values (pre-epoch dates) on Windows
- =begin
My previous comment is not accurate and enough helpful.
rb_time_new's prototype is VALUE rb_time_new(time_t sec, long usec).
so this is depends on sizeof(time_t).
mingw32's time_t seems 32bit.
This means the year 2038 ... -
02:34 AM Bug #4291: rb_time_new with negative values (pre-epoch dates) on Windows
- =begin
Shouldn't we use 64bit on all platforms instead ?
=end
-
02:23 AM Bug #4291 (Rejected): rb_time_new with negative values (pre-epoch dates) on Windows
- =begin
-11676096000 exceeds 32bit long.
On i386-mingw32, long is 32bit (on mswin32 long is of course 32bit, and mswin64 is also 32bit because mswin64 is LLP64)
"Other platforms"'s long seem 64bit.
=end
-
01:16 AM Bug #4291 (Rejected): rb_time_new with negative values (pre-epoch dates) on Windows
- =begin
rb_time_new does not handle negative values (and thus pre-epoch dates) on windows. It seems like it should given that Time.at does.
ruby 1.9.2p136 (2010-12-25) [i386-mingw32]
Pure ruby does work:
irb(main):005:0> sec ... -
03:33 AM Revision b7dd8d07 (git): Always enable rubygems/custom_require
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@30602 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
03:27 AM Bug #4290 (Closed): !_=%w~ dumps core
- =begin
This issue was solved with changeset r30597.
Yusuke, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
----
* parse.y: avoid NULL reference. [ruby-dev:43067]
=end
-
03:21 AM Revision 6d6fe7fe (git): * proc.c (proc_call): Add gc guard to avoid segfault. The fix
- is created by Tomoyuki Chikanaga. [Bug #4238][ruby-dev:42963]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@30601 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
03:09 AM Revision 84e892f8 (git): Remove require of deleted file in RubyGems.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@30600 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
02:42 AM Bug #4292: Type of rdoc in string.c
- =begin
I apologize, I meant typo.
=end
-
02:32 AM Bug #4292 (Closed): Type of rdoc in string.c
- =begin
--- string.c (revision 30594)
+++ string.c (working copy)
@@ -2577,7 +2577,7 @@
* against <i>str</i>,and returns the position the match starts, or
* - 12:08 AM Revision e798ccba (git): Import rubygems 1.5.0 (release candidate)
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@30599 b2dd03c8-39d4-4d8f-98ff-823fe69b080e