Activity
From 04/25/2012 to 05/01/2012
05/01/2012
-
10:29 PM Feature #5784: Readline.special_prefixes の追加
- 遅くなりましたが、近いうちに対応します。
-
10:26 PM Feature #5785: Readline に pre_input_hook, insert_text, redisplay を追加
- 少し補足します。
オリジナルのパッチから以下の修正をしています。
* ユニットテストのtest_modify_text_in_pre_input_hookの出力結果(stdout.read)の期待値を"> hello world\n"に修正しました。
* rl_pre_insert_hookのsetterとgetterの名前はReadline.pre_insert_hookにしました。
* RDocを記述しました。
以上です。
なにわともあ... -
10:21 PM Feature #5785 (Closed): Readline に pre_input_hook, insert_text, redisplay を追加
- This issue was solved with changeset r35513.
Tomoyuki, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
----------
* ext/readline/readline.c (Readline.pre_input_hook)
(Readli... -
06:10 PM Feature #5785 (Assigned): Readline に pre_input_hook, insert_text, redisplay を追加
- すみません。#1823にコメントするつもりが間違ってこちらにコメントしてしまいました。
さっさと、これを実装します。
パッチをいただき、ありがとうございます。 -
06:06 PM Feature #5785 (Rejected): Readline に pre_input_hook, insert_text, redisplay を追加
-
06:06 PM Feature #5785 (Closed): Readline に pre_input_hook, insert_text, redisplay を追加
-
06:08 PM Feature #1823 (Rejected): Readline Command Completion
- Sorry, late reply.
I'm going to implement Readline.pre_input_hook, Readline.insert_text and Readline.redisplay. These are wrapper for rl_pre_input_hook, rl_insert_text and rl_redisplay.
So I think you will be able to implement a proc... -
04:18 PM Bug #5151: test/socket/test_socket.rb fail when udp connection failed
- Mac OSX Lion(Darwin Kernel Version 11.3.0) では、r35509 で再現しなくなっていました。
-
02:23 PM Revision 517f2253 (git): fix typo
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35514 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
01:21 PM Revision 7a4b2145 (git): * ext/readline/readline.c (Readline.pre_input_hook)
- (Readline.insert_text, Readline.redisplay): new function. An
original patch was created by nagachika. [Feature #5785]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35513 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
07:15 AM Revision 28b7df78 (git): * revert r35510 and r35511 which caused removing the headers everytime.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35512 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
06:52 AM Revision d7228e5b (git): depends on ext/openssl/deprecation.rb
- * ext/digest/*/depend: depends on ext/openssl/deprecation.rb.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35511 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
06:52 AM Revision 17359692 (git): extconf.h dependency
- * lib/mkmf.rb (MakeMakefile#depend_rules): deal with extconf.h
dependency. just remove it and bail out right now.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35510 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
06:49 AM Revision e6bd1496 (git): * common.mk: "$(Q)-..." doesn't work on nmake.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35509 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
06:37 AM Revision 458c30e5 (git): * common.mk: replace '@' prefix to '$(Q)' to control build
- process outputs.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35508 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
06:03 AM Bug #6379 (Closed): inconsistent configuration of core extensions linking against libssl and libcrypto (ext/openssl, ext/digest/*)
- This issue was solved with changeset r35504.
Stefan, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
----------
* ext/digest/*/extconf.rb: use pkg_config to use same library w... -
05:18 AM Revision d3215535 (git): * ext/openssl/deprecation.rb (OpenSSL.check_func): check if header is
- available for macro compatibility.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35507 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
02:03 AM Feature #6373: public #self
- Like many of Ruby's keywords, it can still be used to define a public method:
~~~ruby
class X
def self; "x"; end
end
x = X.new
x.self #=> "x"
~~~ -
01:10 AM Feature #6373: public #self
- Thomas, i think an argument against public #self is that 'self' is a reserved word, which moreover is used more as an object name than as a method name. So 'self' would need to stop being a keyword and become a public 'predefined' metho...
- 01:56 AM Revision 633cebb0 (git): * test/ruby/test_settracefunc.rb: ignore traces from another threads
- because Kernel.set_trace_func affects other threads.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35506 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
04/30/2012
-
11:35 PM Feature #6367: #same? for Enumerable
- trans (Thomas Sawyer) wrote:
> My methods names for the "_by" methods are not very good. This should clarify:
> ...
Is a bit misleading about if it's using #equal? or #== for the comparison. -
11:20 PM Feature #6373: public #self
- What about if we borrow #yourself message name from Smalltalk?
-
11:09 PM Bug #6382 (Closed): test_tracing_with_set_trace_func で RuntimeError "continuation called across threads"
- This issue was solved with changeset r35498.
Tomoyuki, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
----------
* test/ruby/test_continuation.rb (tracing_with_set_trace_func... -
11:04 PM Bug #6382 (Closed): test_tracing_with_set_trace_func で RuntimeError "continuation called across threads"
- make test-all を -j2 オプションつきで実行しているとごく稀に
test_tracing_with_set_trace_func で "continuation called across threads" という RuntimeError 例外が発生していました。
set_trace_func に設定した lambda から Continuation を呼んでいて、別 Thread がそれを呼んでしまっていたようです。
このテストは r325... -
09:09 PM Bug #6370 (Closed): NaNTest failed for Ruby 1.9.3 P194
- This issue was solved with changeset r35497.
ray, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
----------
* configure.in (optflags): disable unsafe optimizations.
[ruby-c... -
09:04 PM Revision e1d1397a (git): * ext/digest/sha2/sha2.c (REVERSE32): exlicitly cast since unsigned
- long may be larger than sha2_word32.
* ext/digest/sha2/sha2.c (SHA{256,512,384}_{Final,End}): should clear
whole content, not pointer size.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35505 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
09:03 PM Revision 26e258c8 (git): * ext/digest/*/extconf.rb: use pkg_config to use same library with
- openssl. [ruby-core:44755][Bug #6379]
* ext/openssl/deprecation.rb: extract check for broken Apple OpenSSL.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35504 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
08:14 PM Revision 0f1181a5 (git): Bug #6370
- * configure.in (optflags): fixed typo. [ruby-core:44679][Bug #6370]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35503 b2dd03c8-39d4-4d8f-98ff-823fe69b080e - 08:02 PM Revision fa9a1b62 (git): * 2012-05-01
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35502 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
08:02 PM Revision 7d45d3f8 (git): * configure.in (optflags): disable unsafe optimizations.
- [ruby-core:44679][Bug #6370]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35501 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
04:06 PM Feature #6375: Python notation for literal Hash
- Ok, thanks for the explanation.
Alexey. -
12:23 PM Feature #6375: Python notation for literal Hash
- Hi,
In message "Re: [ruby-core:44761] [ruby-trunk - Feature #6375] Python notation for literal Hash"
on Mon, 30 Apr 2012 08:30:30 +0900, "alexeymuranov (Alexey Muranov)" <redmine@ruby-lang.org> writes:
|Matz, currently {... -
08:30 AM Feature #6375: Python notation for literal Hash
- Matz, currently { 'a': 'b' } does not work in Ruby, do you propose that it be a synonym for { :a => 'b' } in a future version? If not, i do not see your point. The { a: 'b' } syntax is already exceptional, i do not think it will become ...
-
02:45 PM Revision 52af87a5 (git): add an assertion.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35500 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
02:37 PM Revision 7d89ecdc (git): * lib/fileutils.rb (copy_metadata): use File.lchown and File.lchmod to
- update meta data of symlinks.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35499 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
02:09 PM Revision c40e6f82 (git): * test/ruby/test_continuation.rb (tracing_with_set_trace_func): don't
- call Continuation from other threads. [ruby-dev:45596] [Bug #6382]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35498 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
12:48 PM Feature #6361: Bitwise string operations
- trans (Thomas Sawyer) wrote:
> I'm not so sure using "String" in the name is a good idea.
> ...
Hmm, I guess names are a very subtle topic. I stole from [1],
but I see your point why "String" could be confusing. I don't
really care... -
12:27 PM Feature #6361: Bitwise string operations
- I'm not so sure using "String" in the name is a good idea.
The reason I suggested Blob is b/c that's what it is often called: http://en.wikipedia.org/wiki/Binary_large_object
-
11:35 AM Feature #6361: Bitwise string operations
- > If I may intrude for a moment…
No such thing - thank you for your ideas!
> ...
That's a good point. IO would definitely benefit from this
feature, Strings would only be needed when reading line by
line. Encoding would not b... -
01:53 AM Feature #6361: Bitwise string operations
- On Saturday, April 28, 2012 at 8:52 AM, KOSAKI Motohiro wrote:
> On Fri, Apr 27, 2012 at 8:53 PM, MartinBosslet (Martin Bosslet)
> <Martin.Bosslet@googlemail.com (mailto:Martin.Bosslet@googlemail.com)> wrote:
> >
> > Issue #6361 h... -
12:09 PM Revision 860cf7b8 (git): * configure.in (optflags): disable unsafe optimizations.
- [ruby-core:44679][Bug #6370]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35497 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
11:47 AM Bug #3128: Randomness specs
- Hi,
mame (Yusuke Endoh) wrote:
> Marc-Andre, do you need discussion about this?
After your remarks and those of Nobu, the question becomes:
Should `Randomg.new(42); rand` return the same value in all Ruby implementations, or is... -
11:36 AM Feature #6311: memmem()によるrb_memsearch()の高速化
- >rb_memsearch_ss()が何だったか思い出せないですが、これ自体を置き換えてはどうでしょうかね。
添付のpatchのようにするのが良いでしょうか。
rb_memsearch_ss()についてですが、これは1つのVALUEの値にSIZEOF_VALUE以下の長さのバイト列の組み合わせを対応させた完全ハッシュ法のようです。 -
11:11 AM Revision ce007c7c (git): * ext/zlib/extconf.rb: detect z_crc_t type which will be defined
- since zlib-1.2.7.
* ext/zlib/zlib.c (rb_zlib_crc_table): use z_crc_t if available.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35496 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
10:16 AM Feature #6354: Remove escape (break/return/redo/next support) from class/module scope
- Such as:
def f
class << self
yield
end
end
-
08:26 AM Bug #6381 (Third Party's Issue): Useful methods like included don't appear in RDoc
- =begin
Methods like (({Module.included})) and (({Module.private_constant})) don't appear in ruby-doc.org's documentation, because they are private methods. This can cause difficulty for new users of Ruby, for example in http://stackover... -
03:51 AM Revision 38931595 (git): * test/net/http/test_https.rb: update test for r35494
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35495 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
12:11 AM Revision 0456c36d (git): * ext/openssl/lib/openssl/ssl.rb: add hostname to "hostname does not
- match server cert." error.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35494 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
04/29/2012
-
11:06 PM Bug #6370: NaNTest failed for Ruby 1.9.3 P194
- I can reproduce this issue on GCC 4.7.0 Mingw32.
The optimization flag -Ofast is the root cause of this issue.
Accoring to the manual, -Ofast is same to -O3 and -ffast-math.
And -ffast-math sets -fno-math-errno, -funsafe-math-optimi... -
10:57 PM Feature #6375: Python notation for literal Hash
- And repeating myself, when {a: 'b'} is a shorthand for {:a => 'b'},
naturally {'a': 'b'} should be {:'a' => 'b'} that is another form of
{:a => 'b'} in Ruby.
Matz. -
10:00 PM Feature #6375: Python notation for literal Hash
- Ok. However, i was not proposing to remove the 1.9 syntax: { a: 'b' } could be a shorthand notation for { :a: 'b' }, like "#@x #@y" is a shorthand notation for "#{@x} #{@y}".
Alexey. -
08:47 AM Feature #6375 (Rejected): Python notation for literal Hash
- The suggested changes will break almost every program after 1.9.
Ruby is not Python. Please get used to Ruby-way when you are using Ruby.
Matz.
-
02:57 AM Feature #6375: Python notation for literal Hash
- Related: #4801.
-
02:50 AM Feature #6375: Python notation for literal Hash
- I guess i am not using { a: 'b' } because what goes in my head is: "Poor new Ruby user who might need to read this..."
-
02:44 AM Feature #6375 (Rejected): Python notation for literal Hash
- Is there a reason not to use Python notation for literal Hash as an alternative to Ruby notation? I would like to be able to write either { 'a' => 'b', 'c' => 'd' } or { 'a' : 'b', 'c' : 'd' }, and either { :a => 'b' } or { :a: 'b' } . ...
-
08:02 PM Bug #6379 (Closed): inconsistent configuration of core extensions linking against libssl and libcrypto (ext/openssl, ext/digest/*)
- ext/openssl/extconf.rb was change some time ago to prefer compile settings via a pkconfig("openssl") directive.
See https://github.com/ruby/ruby/commit/f6b49243eb0c21bea1c4198cdd52a549e6ead075
However, ext/digest/{md5,rmd160,sha1,s... - 07:44 PM Revision 746c080b (git): * 2012-04-30
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35493 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
07:44 PM Revision 13edcbea (git): * ext/psych/lib/psych/json/yaml_events.rb: implicit styles should not
- be changeable for JSON events.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35492 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
05:38 PM Feature #6311: memmem()によるrb_memsearch()の高速化
- =begin
(({rb_memsearch_ss()}))が何だったか思い出せないですが、これ自体を置き換えてはどうでしょうかね。
=end -
05:29 PM Feature #6376: Feature lookup and checking if feature is loaded
- On Sun, Apr 29, 2012 at 00:03, trans (Thomas Sawyer)
<transfire@gmail.com> wrote:
> These methods could be class methods of special module, if it's important to keep the Kernel more tidy, e.g. `Ruby.required?('ostruct')`.
Wh... -
07:06 AM Feature #6376: Feature lookup and checking if feature is loaded
- Oh, I forget to mention that there seems to be no way to see what the "current loading feature" is either, as it appears that it is not added to $LOADED_FEATURES until after loading is completed, which kind of surprised me. Is that right?
-
07:03 AM Feature #6376 (Assigned): Feature lookup and checking if feature is loaded
- $LOADED_FEATURES is useful to know what "files" have been loaded. But it doesn't really tell us what "features" have been loaded. If there where were a way to look-up a load path, without actually loading it then it would be possible to ...
-
03:40 PM Bug #6378 (Closed): irb incorrectly considers line incomplete when parenthesis are excluded
- Steps to reproduce:
start irb
attempt to execute the following line:
[1,2,3].reduce :+
Expected:
a result of `=> 6` should be printed and a new line should be available
Actual:
The result is not printed and the shell indicat... -
06:12 AM Feature #6353 (Closed): caller-side **
- This issue was solved with changeset r35489.
Yusuke, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
----------
* parse.y (assoc, parser_yylex): add syntax to splat keyword ha... -
03:39 AM Feature #6367: #same? for Enumerable
- =begin
My methods names for the "_by" methods are not very good. This should clarify:
[1,1,1].all_equal? #=> true
[1,1,2].all_equal? #=> false
[2,4,6].all_equal?{|x| x*0} #=> true
[1,1,2].any_equal? ... -
01:49 AM Feature #6367: #same? for Enumerable
- trans (Thomas Sawyer) wrote:
> This reminds me of #sort and #sort_by, and I think both forms would be needed here too --where the later makes it possible to use a comparison besides #==.
> ...
As for me it's contrintuitive to have a pa... -
01:45 AM Feature #6367: #same? for Enumerable
- edtsech (Edward Tsech) wrote:
> I don't know, but I was a little bit confused by that:
> ...
I think renaming of method can make it less confusing. May be Enumerable#coincident?/coincident_by? or Enumerable#identical_by? -
02:32 AM Feature #6361: Bitwise string operations
- nobu (Nobuyoshi Nakada) wrote:
> Hi,
> ...
I thought about this, and yes, you are absolutely right, there's
nothing I couldn't do in a separate C extension. The only remaining
argument I have for built-in support:
I would have lik... -
02:20 AM Feature #6361: Bitwise string operations
- kosaki (Motohiro KOSAKI) wrote:
> I don't dislike a bult-in idea. But you haven't show a detailed spec
> ...
Yes, I thought about writing a proof of concept that could serve as
the blueprint for further discussion. I just wanted... -
02:18 AM Bug #6374: Acces to initialized class variable from included module
- Then why in 'set_variables' (module Variables) is set @@class_variable for class 'A', appropriates to a class variable value? The second call (at the end of program) of a.print_variables already displays the changed values.
-
01:02 AM Bug #5993: Thread.new{ Fiber.new { Thread.exit }.resume }.join で例外
- 長らく放置しててすみません。
先のパッチをテストしていて、これだけでは不十分で確か Fiber 内で fatal() を呼んだりした時の挙動に問題があったためもう少し考えないといけないなぁ、というところで止まってたと思います。
ちょっとどうやら作業していたブランチを消してしまったみたいで、すぐには具体的な内容を思い出せないのですが、少し調べてみてこの修正とは別の問題として切り分けられそうであれば別チケットを作ろうかと思います。 -
12:59 AM Feature #6373: public #self
- On 28/04/2012 16:10, matz (Yukihiro Matsumoto) wrote:
>
> Issue #6373 has been updated by matz (Yukihiro Matsumoto).
>
>
> `__id__` returns `object_id` number, identity here is supposed to return itself.
> I agree with intro... -
12:53 AM Feature #6373: public #self
- Public #self seems like the most obvious choice. Is there some reason not to use it?
-
12:10 AM Feature #6373: public #self
- `__id__` returns `object_id` number, identity here is supposed to return itself.
I agree with introducing method to return self, but not fully satisfied with the name '`identity`'.
Any opinion?
Matz.
04/28/2012
-
10:45 PM Bug #6228: [mingw] Errno::EBADF in ruby/test_io.rb on ruby_1_9_3
- On Win7 32bit, using the following build recipe on both trunk@r35485 and ruby_1_9_3@r35484 with MinGW GCC 4.6.2
sh -c "../configure --enable-shared --disable-install-doc CPPFLAGS='-DFD_SETSIZE=32767'"
make
make test-all TESTS=... -
06:15 AM Bug #6228: [mingw] Errno::EBADF in ruby/test_io.rb on ruby_1_9_3
- > I seem unable to reproduce the exact exception on both trunk and ruby_1_9_3 branches. The error seems randomly manifest.
> ...
I've seen failures in both test_invalid_advise (see comment #3) and test_lines. Both disappeared when I tes... -
04:21 AM Bug #6228 (Feedback): [mingw] Errno::EBADF in ruby/test_io.rb on ruby_1_9_3
- luislavena (Luis Lavena) wrote:
> I'll commit suggested patch from nagachika-san.
> ...
I seem unable to reproduce the exact exception on both trunk and ruby_1_9_3 branches. The error seems randomly manifest.
Right now, against ruby... -
10:24 PM Revision 75cff1d7 (git): add a test for yaml ast roundtripping
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35491 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
10:23 PM Feature #6361: Bitwise string operations
- Hi,
(12/04/28 9:53), MartinBosslet (Martin Bosslet) wrote:
> A real advantage of having it built-in could be
> that this gives us the chance to fix #5741 at
> the same time.
It doesn't explain anything about why they nee... -
09:53 PM Feature #6361: Bitwise string operations
- On Fri, Apr 27, 2012 at 8:53 PM, MartinBosslet (Martin Bosslet)
<Martin.Bosslet@googlemail.com> wrote:
>
> Issue #6361 has been updated by MartinBosslet (Martin Bosslet).
>
>
> nobu (Nobuyoshi Nakada) wrote:
>> Then what k... -
09:53 AM Feature #6361: Bitwise string operations
- nobu (Nobuyoshi Nakada) wrote:
> Then what kind of methods should Blob have?
> ...
A real advantage of having it built-in could be
that this gives us the chance to fix #5741 at
the same time. I could imagine that we have two
kinds o... -
10:20 PM Feature #6362: Modular exponentiation/inverse
- =begin
What about a new class, say Modulo?
m = Modulo.new(101, 11)
m.to_i #=> 2
m**4 #=> 5
=end
-
09:32 AM Feature #6362: Modular exponentiation/inverse
- mame (Yusuke Endoh) wrote:
> Personally I like this proposal, but it seems to require:
> ...
It would be incredibly helpful when implementing cryptographic primitives.
Apart from mathematics in general (and Project Euler in particular... - 09:12 PM Revision 874acd73 (git): * 2012-04-29
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35490 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
09:12 PM Revision 33809741 (git): * parse.y (assoc, parser_yylex): add syntax to splat keyword hash.
- [ruby-core:44591][Feature #6353]
* compile.c (compile_array_): generate keyword splat insns.
* vm.c (m_core_hash_merge_kwd): merge keyword hash into intermediate
hash. leftward argument is prior currently.
git-svn-id: svn+ssh://ci.r... -
09:05 PM Feature #6372: More specific error for uncaught throw
- > Because you didn't explain use case at all, I didn't understand the spec of your code nor what you really want. You are talking about tests, right?
Yes, that's the general use case. Also, I thought my code was correct and so covered... -
07:33 PM Feature #6372 (Assigned): More specific error for uncaught throw
- Because you didn't explain use case at all, I didn't understand the spec of your code nor what you really want. You are talking about tests, right?
Yes, the current design of exception class hierarchy is too coarse for tests. The fa... -
09:20 AM Feature #6372: More specific error for uncaught throw
- I know right? You would think that would work. But...
refute(:a.thrown?{ throw :b })
Fails. I think that's why this has been tricky for me to get right.
-
07:26 AM Feature #6372 (Feedback): More specific error for uncaught throw
- How about:
class Symbol
def thrown?
thrown = true
catch(self) do
yield
thrown = false
end
thrown
end
end
--
Yusuke Endoh <mame@tsg.ne.jp> -
04:09 AM Feature #6372 (Rejected): More specific error for uncaught throw
- I have this method:
=begin
class Symbol
# Does the block throw the symbol?
#
def thrown?
catch(self) do
begin
yield
true
rescue ArgumentError => err # 1.9 exception... -
08:46 PM Feature #6367: #same? for Enumerable
- This reminds me of #sort and #sort_by, and I think both forms would be needed here too --where the later makes it possible to use a comparison besides #==.
On the other hand it reminds me of #all? as well, which makes me wonder about ... -
03:12 PM Feature #6367: #same? for Enumerable
- I don't know, but I was a little bit confused by that:
assert_equal(true, [1,3,9,7].same?(&:even?))
assert_equal(true, [4,8,2,2].same?(&:even?))
or I can write smth like that:
assert_equal(true, [1.0,2.0,3.0,4.0].same?(&:integer?))
May... -
07:40 PM Bug #6374: Acces to initialized class variable from included module
- It's a spec.
Class variables belong to the static scope of classes, as well as constants. -
02:16 PM Bug #6374: Acces to initialized class variable from included module
- And more:
If then at the end to execute 'a.print_variables', we will receive values which set in 'a.set_variables_a (12, 33)' -
01:53 PM Bug #6374 (Rejected): Acces to initialized class variable from included module
- # Description of bug (?) below in comments of code
# May by it is not a bug, but feature ?
module Variables
def print_var
print "In module #{self.class.name}: #{@variable}\n"
end
def print_class_var
print "In module c... -
06:31 PM Feature #6373: public #self
- `enum.map(&:identity)` can be replaced with `enum.to_a`
But I think `Object#identity` is useful. `Object#tap` requires a block. It's not an option to use it in many cases. I can't imagine how to replace `enum.group_by(&:identity)` with ... -
04:06 PM Feature #6373: public #self
- Actually, I just realized there is already a method you can call to just return the method itself, albeit in a really gross way: `#tap`.
~~~ruby
obj.tap{} #returns obj; block is required and invoked -
04:02 PM Feature #6373: public #self
- At first I found this laughable, but then I realized there's no clear method you can call against an object that simply returns the object. It is a small thing, but turns out to be very useful.
For example, if you want a chain of meth... -
10:05 AM Feature #6373: public #self
- Use __id__.
-
08:28 AM Feature #6373: public #self
- `#identity` (or whatever it's called) is quite important in functional languages. It's handy to pass to another function that e.g. uses it as an argument to map,... So I think it's a good idea to add it.
The name should be identity or... -
07:11 AM Feature #6373 (Assigned): public #self
-
06:46 AM Feature #6373 (Closed): public #self
- This was recently suggested to me as an extension:
~~~ruby
class Object
# An identity method that provides access to an object's 'self'.
#
# Example:
# [1,2,3,4,5,1,2,2,3].group_by(&:identity)
# #=> {1=>[1, 1], 2=>... -
05:53 PM Feature #6354: Remove escape (break/return/redo/next support) from class/module scope
- (2012/04/28 0:37), ktsj (Kazuki Tsujimoto) wrote:
> What about yield?
> I think it should also be removed if the proposal is accepted.
Example?
--
// SASADA Koichi at atdot dot net -
12:37 AM Feature #6354: Remove escape (break/return/redo/next support) from class/module scope
- What about yield?
I think it should also be removed if the proposal is accepted. -
03:00 PM Feature #6308: Eliminate delegation from WeakRef
- My proposal is that at some time deemed acceptable by ruby-core and Matz, the delegate-based WeakRef should go away, and that in Ruby 2.0 a "preferred" non-delegate WeakRef be added (ideally along with the reference queue support in my o...
-
02:47 PM Feature #6309: Add a reference queue for weak references
- Ok, fair enough.
Here is a *very primitive* modification of the current weakref.rb to support a reference queue. I need to stress that I don't think this is the best way to implement it; a hook into the GC cycle that inserts weakrefs ... -
02:22 PM Revision 82fa2995 (git): * ext/-test-/win32/dln/extconf.rb: remove test DLL.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35488 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
01:34 PM Feature #6311: memmem()によるrb_memsearch()の高速化
- rb_memsearch_ss()はrb_memsearch()以外からは使われていないので、memmem()を使う場合にはrb_memsearch_ss()がコンパイルされないようにしました。
-
12:25 PM Feature #5455: $SAFE should be removed
- In an effort to be constructive here, I will attempt to break out specific, concrete permissions revoked at each SAFE level (or conversely, granted as SAFE levels are reduced). I base this on the publicly available edition of Programming...
- 09:59 AM Revision 55ac2cac (git): * 2012-04-28
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35487 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
09:59 AM Revision 6978b8ca (git): * vm_core.h (rb_thread_t#yielding): add a field.
- * thread.c (rb_thread_schedule_limits): set th#yielding while
release GVL to yield CPU time.
* thread.c (timer_thread_function): skip timer interrupt when
th#yielding is true. This patch fixes r35480.
* thread.c (rb_threadptr_execut... -
09:55 AM Feature #5741: Secure Erasure of Passwords
- Just to add this, I think it wasn't mentioned yet: we
also have to be aware of copying during GC, this could
compromise a password in memory as well. -
05:53 AM Feature #5458: DL should be removed - On Sat, Apr 28, 2012 at 02:06:51AM +0900, mame (Yusuke Endoh) wrote:
>
> Issue #5458 has been updated by mame (Yusuke Endoh).
>
> Assignee changed from mame (Yusuke Endoh) to tenderlovemaking (Aaron Patterson)
> Target version ch... -
02:06 AM Feature #5458: DL should be removed
- Okay, I'm willing to mark DL as obsolete in 2.0.
If anyone has an objection, please declare yourself ASAP.
Aaron, could you add a warning?
Then, please reassign back to me.
--
Yusuke Endoh <mame@tsg.ne.jp> -
01:51 AM Feature #5458: DL should be removed
- Even though DL can be emulated by using Fiddle in theory, I'd rather keep it for 2.0 for compatibility.
After 2.0, it's OK to replace DL. In that case, we can mark DL as obsolete.
-
05:05 AM Bug #6369: GServer blocking after shutdown called
- Hi Yusuke-san,
all your syntactic points are accepted. This is the first patch I have submitted,so please excuse my lack of knowledge of the accepted submission protocols.
Also, I completely accept that the initial motivation for th... -
12:24 AM Bug #6369: GServer blocking after shutdown called
- When you send a patch,
* don't split header (we don't search the file)
* don't introduce cosmetic changes (follow the coding style of original code)
* use unified diff (diff -u)
* use -p option (-p --show-c-function Show which C fu... -
01:46 AM Bug #6370 (Assigned): NaNTest failed for Ruby 1.9.3 P194
- I have no idea why (nan != 0) is evaluated to false.
Luis, Usa-san, Hongli Lai, can you reproduce it?
--
Yusuke Endoh <mame@tsg.ne.jp> -
01:17 AM Feature #6353: caller-side **
- =begin
Almost implemented, and another question.
What should happen in this case?
def foo(k1: 1)
p k1
end
h = {k1: "bar"}
foo(k1: "foo", **h) # <== conflict
(({k1})) will be (({"foo"})), or (({"bar"}))?
Or an except... -
01:07 AM Bug #4044: Regex matching errors when using \W character class and /i option
- One additional note is that this only seems to occur when `\W` is in a character group:
~~~
➜ ruby -ve '("a".."z").each {|ch| p(/\W/i.match(ch)) }'
ruby 1.9.3p125 (2012-02-16 revision 34643) [x86_64-darwin12.0.0]
nil
nil
nil
n... -
12:26 AM Bug #5358 (Closed): YAML 中のタグの扱いについて
- 報告者が納得されているようなのでこのチケットはCloseします。
-
12:24 AM Bug #5390 (Closed): YAML.load が、正しく解析できないエンコーディングの文字列も受け付けてしまう
- 1.9.2はもうすぐメンテナンス終了で、1.9.3からPsychがデフォルトです。
こちらのチケットはCloseします。
04/27/2012
-
11:56 PM Bug #6370: NaNTest failed for Ruby 1.9.3 P194
- Here is the result:
beta@beta-PC ~
$ ruby test.rb
NaN
"\x00\x00\x00\x00\x00\x00\xF8\xFF"
nil
false
false
false
false
false -
10:25 PM Bug #6370: NaNTest failed for Ruby 1.9.3 P194
- Could you run the following script and show the result?
nan = 0.0 / 0
p nan
p [nan].pack("D")
p nan <=> 0
p nan != 0
p nan < 0
p nan > 0
p nan <= 0
p nan >= 0
--
Yusuke Endoh <mame@tsg.ne.jp> -
02:27 PM Bug #6370 (Closed): NaNTest failed for Ruby 1.9.3 P194
- The Ruby 1.9.3 is compibled by GCC 4.7.0 (MinGW64) under Windows64. Configure line is as following:
.configure --build=x86_64-w64-mingw32 CFLAGS="-Ofast -mieee-fp -I/usr/local/include" CPPFLAGS="-Ofast -mieee-fp -I/usr/local/include" ... -
11:41 PM Bug #5993: Thread.new{ Fiber.new { Thread.exit }.resume }.join で例外
- ちょっと思い出せないんですが(多分、その辺整理すると思う)、
近永さんのことだから信じられると思います。
というわけで、テスト付きでコミットいただければ。 -
10:07 PM Bug #6369 (Assigned): GServer blocking after shutdown called
- Hello,
> I believe there is also an underlying design flaw: the main thread (@tcpServerThread) is blocked in the TCPServer#accept call, so if no further connections are attempted after #shutdown() is called, the main thread remains b... -
05:52 AM Bug #6369 (Closed): GServer blocking after shutdown called
- Hi,
My investigation of bug #6358 points the finger at GServer triggering bug #5343 on lower power arm-linux platforms, because of the blocking TCPServer#accept call.
I believe there is also an underlying design flaw: the main threa... -
09:48 PM Feature #6368 (Rejected): Improvement to GServer - avoids bug #5343 on low speed [arm-linux] platform
- You filed this ticket by mistake?
If not, please reopen it with description.
--
Yusuke Endoh <mame@tsg.ne.jp> -
05:29 AM Feature #6368 (Rejected): Improvement to GServer - avoids bug #5343 on low speed [arm-linux] platform
-
05:06 PM Feature #6367: #same? for Enumerable
- homologous? :)
-
02:18 PM Feature #6367 (Feedback): #same? for Enumerable
- I accept the idea of having the method that ensures all elements are same (under some criteria).
But the same? is not good name for it. I place this "feedback" to get the "right" name.
Matz.
-
04:41 AM Feature #6367: #same? for Enumerable
- I think any name you choose can be used.
-
03:21 AM Feature #6367 (Assigned): #same? for Enumerable
- Personally I don't think it is a good name.
It looks a kind of comparison operator.
--
Yusuke Endoh <mame@tsg.ne.jp> -
02:28 PM Bug #4443: odd evaluation order in a multiple assignment
- 手元にあるJIS x3017のドラフトを見ると現状の評価順(多重代入の場合には右辺が先)が記述してありますね(11.4.2.4)。
どうしたもんだか。 -
02:13 PM Bug #5829: /dl/test_cptr.rb Segmentation fault on Ruby 1.9.3 P0
- This can be closed now. already find out it is DL CPtr issue.
-
02:12 PM Bug #6333: Ruby 1.9.3 (P0, P125,P194) Segmentation fault when compiled with GCC 4.7.0
- GCC also corrected this issue.
Regards. -
02:06 PM Bug #6364: Segmentation fault happend when running test_cptr.rb
Win32 use LP32 data modle and Win64 use LLP64 data model. LP32 means long & pointer is 4bytes, LLP64 means long long & pointer is 8bytes. some widely used types like size_t, time_t, and ptrdiff_t are also 8bytes within Win64.
I t...-
01:23 PM Bug #6364: Segmentation fault happend when running test_cptr.rb
- Hello,
In message "[ruby-core:44651] [ruby-trunk - Bug #6364] Segmentation fault happend when running test_cptr.rb"
on Apr.26,2012 23:41:32, <raylinn@gmail.com> wrote:
> Here is the log. I wrote a small C to invoke the f... -
12:36 PM Bug #6364 (Closed): Segmentation fault happend when running test_cptr.rb
- This issue was solved with changeset r35485.
ray, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
----------
* ext/dl/cfunc.c (rb_dlcfunc_call): should convert a Bignum value ... -
03:14 AM Bug #6364 (Assigned): Segmentation fault happend when running test_cptr.rb
- Usa-san, may I assign this to you?
If not, please reassign to Aaron who is a maintainer of dl.
I guess he will say "WONTFIX, use fiddle instead," though.
--
Yusuke Endoh <mame@tsg.ne.jp> -
12:59 PM Feature #6365 (Rejected): [Feature request] Better readable syntax to check if String is included in Array
- You explained you prefer str.included_in?(ary) or str.include?(ary) better because you "don't think it reads very nice".
I consider it very subjective. Could you elaborate if you really want the feature merged?
I am against str.incl... -
03:25 AM Feature #6365 (Assigned): [Feature request] Better readable syntax to check if String is included in Array
- There were some similar proposals:
- Object#in? [ruby-core:23543]
- "in" infix operator [ruby-core:32454]
But matz is not enthusiastic for this kind of proposals.
--
Yusuke Endoh <mame@tsg.ne.jp> -
10:58 AM Bug #6357 (Closed): readlineのテストtest_editing_modeが実行ユーザの.inputrcに影響される
- This issue was solved with changeset r35483.
Wataru, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.
----------
* test/readline/test_readline.rb (setup): avoid affected by use... -
09:56 AM Feature #6361: Bitwise string operations
- Then what kind of methods should Blob have?
And does it need to be built-in? -
03:03 AM Feature #6361: Bitwise string operations
- +1 : I use them every day.
-
01:52 AM Feature #6361: Bitwise string operations
- +1 for Blob (or, my preferred name: Data). I've mentioned this in the past, but we can look at Obj-C's example: NSString => a string class with encoding and code-point/character-wise manipulation, NSData => a class to encapsulate a rando...
-
05:43 AM Bug #6355: arm-linux build test suite fails: on : /lib/ruby/1.9.1/arm-linux/digest/md5.so: [BUG] Segmentation fault
- Yusuke-san
Please close - identified as a missing linux library dependency.
The following script finds missing library dependencies
#!ruby
lib_list=`find . -name *.so`.split("\n")
lib_list.each do |lib|
ldd_out=`ldd #{lib... - 03:36 AM Revision 62d71852 (git): * ext/dl/cfunc.c (rb_dlcfunc_call): should convert a Bignum value to
- unsigned long long on Win64.
[ruby-core:44636][Bug #6364] reported by raylinn@gmail.com (ray linn)
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35485 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
03:11 AM Bug #6363 (Feedback): mak test fail on hpux 11.31 ia
- Please try Ruby trunk.
If the problem still occurs, could you please create a patch yourself?
There is no arm maintainer unfortunately.
If your patch looks simple and benign for other platforms, we may import it.
Thanks,
-- ... -
03:10 AM Feature #6362 (Feedback): Modular exponentiation/inverse
- Personally I like this proposal, but it seems to require:
- use cases (Well, personally I often use them for Project Euler :-)
- candidates of method name (pow_mod / inv_mod?)
- a detailed spec (especially corner cases, e.g., ... -
03:05 AM Feature #6362: Modular exponentiation/inverse
- +1 : very helpful for cryptographic stuffs.
-
02:10 AM Revision 7caf2598 (git): merge revision(s) 33196:
- * test/rinda/test_rinda.rb (test_core_03_notify): Fixed test failures
[ruby-dev:44430] [Ruby 1.9 - Bug #372]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/branches/ruby_1_9_3@35484 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
01:58 AM Revision 0a68f120 (git): * test/readline/test_readline.rb (setup): avoid affected by user's
- inputrc file. [ruby-dev:45584][Bug #6357]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35483 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
01:41 AM Revision 664a13b7 (git): test/readline/test_readline.rb: suppress bell
- * test/readline/test_readline.rb (replace_stdio, with_pipe): suppress bell.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35482 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
01:20 AM Bug #6358: arm-linux : sleep() time dependent threading bug
- Hi Yusuke-san
Resolved - duplicated #5343
further investigation leads me to believe that this is actually a duplicate of Bug #5343 as I can consistently make that bug happen on the arm-linux platform. Therefore please close this bug.... -
12:19 AM Bug #6358: arm-linux : sleep() time dependent threading bug
- Could you write a reproducible code with C?
If you can, it is an issue of ulibc's pthread implementation.
The root of sleep(timeout) is pthread_cond_timedwait(3).
So I suspect it has a bug.
04/26/2012
-
11:48 PM Bug #6364: Segmentation fault happend when running test_cptr.rb
- it is this line cause the Segmentation fault.
p fread.([buf.to_i, 1, buf.size - 1, fp.to_i])
The declaretion of fread is size_t fread(void*,size_t,size_t,FILE*), in 64bit GCC, size_t size is 8, so ffi type should be POINTER and UIN... -
11:41 PM Bug #6364: Segmentation fault happend when running test_cptr.rb
- Here is the log. I wrote a small C to invoke the fread within msvcrt.dll via libffi, but it works fine.
$ ruby rubyffi2.rb
true
#<DL::CPtr:0x00000002c5a430 ptr=0x00000002c5a370 size=10 free=0x00000000000000>
#<DL::CPtr:0x00000002c... -
04:59 PM Bug #6364: Segmentation fault happend when running test_cptr.rb
- Hello,
In message "[ruby-core:44640] [ruby-trunk - Bug #6364] Segmentation fault happend when running test_cptr.rb"
on Apr.26,2012 14:15:30, <raylinn@gmail.com> wrote:
> Yes, My target is to provide the most compatiable r... -
02:15 PM Bug #6364: Segmentation fault happend when running test_cptr.rb
- Yes, My target is to provide the most compatiable ruby binray of Windows. Most Ruby ext include fiddle,syslog has been compiled except pty. and the test result of fiddel is zero error, as following:
$ make test-all TESTS='fiddle'
.... -
12:35 PM Bug #6364: Segmentation fault happend when running test_cptr.rb
- You must use ext/fiddle (= libffi wrapper) on Win64.
-
12:24 PM Bug #6364 (Closed): Segmentation fault happend when running test_cptr.rb
- Ruby 1.9.3-P194 compiled by MinGW64 (GCC 4.7.0), Compiled success, but failed when run test all. The same issue happened on GCC 4.6.3 + Ruby 1.9.3-P0. The error dump is
C:/msys/1.0/home/beta/ruby-1.9.3-p194/test/dl/test_cptr.rb:84: [... -
11:32 PM Feature #6361: Bitwise string operations
- +1 for Blob, strings are not the only data that one might wish to encrypt.
-
11:26 PM Feature #6361: Bitwise string operations
- Would it be better to have a dedicated class, e.g. a Blob ?
-
07:22 PM Feature #6361 (Feedback): Bitwise string operations
- Propose a detailed spec with use cases.
For example the behavior of the case "aa" ^ "bbbb" -
09:57 AM Feature #6361: Bitwise string operations
- +1 from me...
There are many cases where high-perf treatment of a homogeneous array would be useful in Ruby, as evidenced by libraries like NArray and friends. NArray has been proposed for inclusion in Ruby in the past, but I don't kn... -
09:37 AM Feature #6361 (Rejected): Bitwise string operations
- I know this has been discussed a lot in the past (and if there's still
an open issue for this, I apologize, I couldn't find one), for example
in [1]. While it is generally no problem to implement this on the fly,
I still find that bu... -
11:30 PM Revision 85f444d4 (git): merge revision(s) 35417:
- * test/rinda/test_rinda.rb: fix sticks on some testsf problem
[Bug #6272]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/branches/ruby_1_9_3@35481 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
11:19 PM Revision c746b6fa (git): * thread.c (rb_threadptr_execute_interrupts_common):
- handle timer_interrupt only on the first loop for the case to avoid
the infinite loop like following case:
* there is 2 Ruby threads (3 pthreads)
(1) main thread is waiting at gvl_yield:112 (native_cond_wait)
(2) sub thread works... -
10:35 PM Feature #6367 (Feedback): #same? for Enumerable
- I realised that I frequently test if all objects in enumerable have the same feature. For example if all words have the same length (but not defined before). So I found particulary useful method Enumerable#same_by? that test this behavio...
-
10:18 PM Revision da12c793 (git): * ext/socket/socket.c (sock_s_pack_sockaddr_un): support the longest
- path in sockaddr_un, really.
reported by nagachika.
http://d.hatena.ne.jp/nagachika/20120426/ruby_trunk_changes_35474_35476
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35479 b2dd03c8-39d4-4d8f-98ff-823fe69b080e - 05:38 PM Revision 0e01d836 (git): * 2012-04-27
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35478 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
05:38 PM Revision 9a92bcdb (git): fix typos
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35477 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
05:36 PM Feature #6365: [Feature request] Better readable syntax to check if String is included in Array
- Since I can't fix the RD syntax error, here is the text again:
I find myself constantly wanting to check whether one string is included within an array of strings.
It is certainly possible (and also fast) to do that in Ruby with some... -
05:33 PM Feature #6365 (Rejected): [Feature request] Better readable syntax to check if String is included in Array
- =begin
I find myself constantly wanting to check whether one string is included within an array of strings.
It is certainly possible (and also fast) to do that in Ruby with something like this: (({["foo", "bar"].include?("foo")}))
But... -
05:07 PM Feature #3219: assert now passes non-boolean result
- In my view those are a kind of predicates that deserve to be tested using a straightforward assertion call. They are common, for example
# Says whether there's a user in the session.
def logged_in?
@current_user
end
o... -
04:58 PM Feature #3219: assert now passes non-boolean result
- Hmmm... if I have
# Returns true if the user has first and last names.
def name_complete?
@first_name && @last_name
end
I'd like to be able to continue testing that as
assert user.name_complete?
the a... -
02:05 PM Feature #3219: assert now passes non-boolean result
- =begin
fxn, you can use (({assert_send})) instead and will see better message if it fails.
$ ruby -rtest/unit -e 'class X<Test::Unit::TestCase;def test_fail; assert_send([3, :even?]); end; end'
Run options:
# Running tests:
... -
01:24 PM Revision b82f8f71 (git): add a comment.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35476 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
01:24 PM Revision 4c87e943 (git): suppress a warning.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35475 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
12:53 PM Bug #6356: arm linux build test suite fails on test/socket
- 2012/4/25 stevegoobermanhill (stephen gooberman-hill)
<stevegoobermanhill@gmail.com>:
>
> Issue #6356 has been reported by stevegoobermanhill (stephen gooberman-hill).
> ruby -v: ruby 1.9.2p136 (2010-12-25 revision 30365) [ar... -
11:49 AM Bug #6363 (Rejected): mak test fail on hpux 11.31 ia
- $ export PATH=/usr/local/bin:$PATH
$ export CC=gcc
$ export CFLAGS="-O2 -g -pthread -mlp64 -w -pipe -Wall -fexceptions"
$ export CPPFLAGS="-DHAVE_HMAC_CTX_COPY -DHAVE_EVP_CIPHER_CTX_COPY"
$ ./c... -
11:18 AM Bug #6341 (Third Party's Issue): SIGSEGV: Thread.new { fork { GC.start } }.join
- rudolf (r stu3) wrote:
> naruse (Yui NARUSE) wrote:
> ...
enami committed it to NetBSD current as rev 1.134.
http://cvsweb.netbsd.org/bsdweb.cgi/src/lib/libpthread/pthread.c?rev=1.134&content-type=text/x-cvsweb-markup&only_with_tag=M... -
03:24 AM Bug #6341: SIGSEGV: Thread.new { fork { GC.start } }.join
- naruse (Yui NARUSE) wrote:
> Following patch to NetBSD fixes this issue.
> ...
[...]
I've tested the patch and can no more reproduce the problem. Thanks! -
09:57 AM Bug #5511: "make test" failure on HP-UX/PA
- i got the bug on hpux 11.31 IA 1.9.3p125
-
09:52 AM Feature #6362 (Closed): Modular exponentiation/inverse
- I'd like to ask your opinion about adding two methods for modular
exponentiation/modular inverse to integer classes. Is this
functionality too specific or would this be a welcome addition? -
09:20 AM Feature #6219: Return value of Hash#store
- Yes, I neglected assignment in my initial proposal, silly idea :) Hash#store would be great, though! Apart from the problem of how to handle the default proc, are there still other reasons against this?
-
08:46 AM Bug #6360 (Assigned): Debug information build even without requesting it
- Hello,
While working on latest RubyInstaller release for 1.9.3-p194 our team detected a bigger shared library and import library being generated.
After further inspection, we found this commit:
https://github.com/ruby/ruby/commit/... -
05:37 AM Bug #6358: arm-linux : sleep() time dependent threading bug
- Hi Yusuke-san,
I'm not sure that I will be able to create a patch - you can blame Matz :-) If he hadn't written such a brilliant language I would still be competent in C. :-) As it is, while I can still competently read and understand C... -
03:34 AM Revision 1413510e (git): * ext/socket/raddrinfo.c (init_unix_addrinfo): support the longest
- path in sockaddr_un.
(inspect_sockaddr): ditto.
(addrinfo_mdump): ditto.
(addrinfo_mload): ditto.
(rsock_unixpath_str): new function.
(rsock_unixpath): removed.
(rsock_unixaddr): use rsock_unixpath_str.
* ext/socket/socket.c...
04/25/2012
-
10:39 PM Bug #6358 (Feedback): arm-linux : sleep() time dependent threading bug
- At first, please try Ruby trunk.
If the problem still occurs, could you please create a patch yourself?
There is no arm maintainer unfortunately.
If your patch looks benign for other platforms, we may import it.
Thanks,
--
... -
10:31 PM Bug #6358 (Closed): arm-linux : sleep() time dependent threading bug
- Hi,
I have a multi-threading bug on a low-speed (180MHz) arm-linux platform. The bug can be consistantly produced or removed by varying the length of a sleep() interval at the end of a piece of code invoked in a Thread (the GServer#serv... -
10:37 PM Bug #6356 (Feedback): arm linux build test suite fails on test/socket
- At first, please try Ruby trunk.
If the problem still occurs, could you please create a patch yourself?
There is no arm maintainer unfortunately.
If your patch looks benign for other platforms, we may import it.
Thanks,
--
... -
09:33 PM Bug #6356 (Rejected): arm linux build test suite fails on test/socket
- consistent unix address errors in 3 places, plus 1 failure in socket test suite
kind regards
Steve
[root@techbase /mnt/nand-user/ruby-1.9.2-p136]# /mnt/nand-user/ruby/bin/ruby test/socket/*
Loaded suite test/socket/test_addrinf... -
10:37 PM Bug #6355 (Feedback): arm-linux build test suite fails: on : /lib/ruby/1.9.1/arm-linux/digest/md5.so: [BUG] Segmentation fault
- At first, please try Ruby trunk.
If the problem still occurs, could you please create a patch yourself?
There is no arm maintainer unfortunately.
If your patch looks simple and benign for other platforms, we may import it.
Than... -
09:29 PM Bug #6355 (Closed): arm-linux build test suite fails: on : /lib/ruby/1.9.1/arm-linux/digest/md5.so: [BUG] Segmentation fault
- build test suite fails
- first claims that a file which exists is not found
- then throws a segfault
I suspect that this may be an issue with the test suite as if I run the test on it's own, ruby claims that the file cannot be found... -
10:22 PM Bug #6357 (Assigned): readlineのテストtest_editing_modeが実行ユーザの.inputrcに影響される
-
10:00 PM Bug #6357 (Closed): readlineのテストtest_editing_modeが実行ユーザの.inputrcに影響される
- =begin
木村といいます。
readlineのテストが実行したユーザの~/.inputrcによって失敗することがあります。
以下に例を示します。
1. inputrcでviモードが指定されているとtest_editing_modeが失敗する
% echo set editing-mode vi > inputrc
% INPUTRC=inputrc make test-all TESTS=readline
:
1) Failur... -
06:49 PM Feature #3219: assert now passes non-boolean result
- Not sure I understand this ticket.
If I write a generic predicate foo? whose return value is undocumented and irrelevant, I should be able to test it like this?
assert obj.foo?
-
06:46 PM Feature #3219: assert now passes non-boolean result
- Sorah-san, you can decide this.
--
Yusuke Endoh <mame@tsg.ne.jp> -
04:36 PM Revision 2bc4268e (git): * test/optparse/test_summary.rb (test_summary_containing_space): add
- test for r35467. OptionParser#to_a shouldn't split banner by spaces.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35473 b2dd03c8-39d4-4d8f-98ff-823fe69b080e - 04:22 PM Revision df79ded6 (git): * 2012-04-26
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35472 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
04:22 PM Revision f51e9cc0 (git): * ChangeLog: fix a typo.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@35471 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
02:05 PM Revision c1d27b8c (git): * ext/socket/raddrinfo.c (init_unix_addrinfo): refine error message
- format.
(addrinfo_mload): show more information on "too long AF_UNIX path"
error.
(addrinfo_unix_path): ditto for "too short AF_UNIX address" and
"too long AF_UNIX address" error.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/tru... -
01:23 PM Feature #6354: Remove escape (break/return/redo/next support) from class/module scope
- (2012/04/25 12:37), mame (Yusuke Endoh) wrote:
> By removing it, what advantage will we get?
It simplifies VM implementation.
--
// SASADA Koichi at atdot dot net -
12:37 PM Feature #6354 (Assigned): Remove escape (break/return/redo/next support) from class/module scope
- I don't object, but just curious.
By removing it, what advantage will we get?
--
Yusuke Endoh <mame@tsg.ne.jp> -
12:12 PM Feature #6354 (Assigned): Remove escape (break/return/redo/next support) from class/module scope
- Let's remove global escape (break/return/redo/next support) from class/module scope.
Yes, it introduces incompatibility. However, anyone use it?
I think the following examples are evil (difficult to understand).
# examples:
... -
12:43 PM Bug #4974 (Closed): [ext/tk] ruby_1_9_2@32391 build failure with MinGW
- I think this issue can be closed. Let me know if I'm wrong.
--
Yusuke Endoh <mame@tsg.ne.jp> -
07:59 AM Feature #6353: caller-side **
- Hi,
In message "Re: [ruby-core:44591] [ruby-trunk - Feature #6353][Assigned] caller-side **"
on Tue, 24 Apr 2012 22:04:03 +0900, "mame (Yusuke Endoh)" <mame@tsg.ne.jp> writes:
|However, it conflicts with power expression... -
07:50 AM Bug #6341: SIGSEGV: Thread.new { fork { GC.start } }.join
- Following patch to NetBSD fixes this issue.
thanks @_enami
Index: pthread.c
===================================================================
RCS file: /cvsroot/src/lib/libpthread/pthread.c,v
retrieving revision 1.133
diff -u -... -
06:23 AM Bug #6341: SIGSEGV: Thread.new { fork { GC.start } }.join
- On Tue, Apr 24, 2012 at 2:25 PM, Eric Wong <normalperson@yhbt.net> wrote:
> KOSAKI Motohiro <kosaki.motohiro@gmail.com> wrote:
>> (4/24/12 6:55 AM), Yusuke Endoh wrote:
>> >2012/4/24, KOSAKI Motohiro<kosaki.motohiro@gmail.com>:
>> >... -
03:29 AM Bug #6341: SIGSEGV: Thread.new { fork { GC.start } }.join
- KOSAKI Motohiro <kosaki.motohiro@gmail.com> wrote:
> (4/24/12 6:55 AM), Yusuke Endoh wrote:
> >2012/4/24, KOSAKI Motohiro<kosaki.motohiro@gmail.com>:
> >>Do you want raise NotImplementError on _all_ platform?
> >
> >My answer ... -
01:53 AM Bug #6341: SIGSEGV: Thread.new { fork { GC.start } }.join
- On Tue, Apr 24, 2012 at 12:13 PM, NARUSE, Yui <naruse@airemix.jp> wrote:
> (2012/04/24 19:44), KOSAKI Motohiro wrote:
>>> kosaki (Motohiro KOSAKI) wrote:
>>>> On Mon, Apr 23, 2012 at 11:17 PM, Yusuke Endoh <mame@tsg.ne.jp> wrote:
>>... -
01:23 AM Bug #6341: SIGSEGV: Thread.new { fork { GC.start } }.join
- (2012/04/24 19:44), KOSAKI Motohiro wrote:
>> kosaki (Motohiro KOSAKI) wrote:
>>> On Mon, Apr 23, 2012 at 11:17 PM, Yusuke Endoh <mame@tsg.ne.jp> wrote:
>>> > I suggest to make Kernel#fork raise a NotImplementedError on NetBSD
... -
12:29 AM Bug #6341: SIGSEGV: Thread.new { fork { GC.start } }.join
- (4/24/12 6:55 AM), Yusuke Endoh wrote:
> Hello,
>
> 2012/4/24, KOSAKI Motohiro<kosaki.motohiro@gmail.com>:
>> Do you want raise NotImplementError on _all_ platform?
>
> My answer is yes, if the problem occurs actually.
>
... -
06:53 AM Feature #5555: rename #include? to #includes? - > Do you try to call pop! as well? :)
That sounds like a balloon! yes! pop!
(I suppose in answer to your question, for some reason I don't use
pop, but I would probably reach for a pop! :) -
05:53 AM Feature #5555: rename #include? to #includes?
- On Wed, 2012-04-25 at 05:24 +0900, Roger Pack wrote:
> >> It always confuses me how that one defies the rule.
> >
> > There’s no non-dangerous version of Array#shift, so it doesn’t defy the rules.
>
> True, I just always reac... -
05:29 AM Feature #5555: rename #include? to #includes? - >> It always confuses me how that one defies the rule.
>
> There’s no non-dangerous version of Array#shift, so it doesn’t defy the rules.
True, I just always reach for shift! since it makes more sense in my head.
-r -
05:23 AM Feature #5555: rename #include? to #includes?
- On Tue, Apr 24, 2012 at 15:47, Roger Pack <rogerdpack2@gmail.com> wrote:
>> The basic naming for methods in standard class libraries are:
>>
>> * use basic form (include not includes)
>> * put question mark for predicates
>> * put ... -
05:53 AM Bug #6246: 1.9.3-p125 intermittent segfault
- >
/home/deploy/.rvm/rubies/ruby-1.9.3-p125/lib/libruby.so.1.9(rb_gc_call_finalizer_at_exit+0x219) [0x7f9f37246359] gc.c:3044
> /home/deploy/.rvm/rubies/ruby-1.9.3-p125/lib/libruby.so.1.9(ruby_cleanup+0x1ec) [0x7f9f37233fac] eval.c:... -
04:31 AM Bug #6246: 1.9.3-p125 intermittent segfault
- I've been using p194 for about a day now - no crashes yet
I'll notify you here over the next while
if the crashing resumes, I'll try the patch Yusuke.
much thanks to you both. -
01:44 AM Feature #2565: adding hooks for better tracing
- Could the experimental probes be added in 1.9.3, so that developers would gain experience using them and have a more solid basis to recommend better probe design in 2.0?
-
12:21 AM Bug #6344: 1.9.3 p125, p194 ruby causes SEGV with test_massign.rb on ppc/ppc64
- >OP said the same issue occurred on x86_64-linux, but I couldn't reproduce.
> ...
No I can't. we need more feedback, I think.
-
12:10 AM Bug #5986: Segmentation Fault
- Thanks Yusuke.
I have notified the ActiveAdmin project (https://github.com/gregbell/active_admin/issues/1269) and I have closed the issue at EventMachine (https://github.com/eventmachine/eventmachine/issues/318).
Chears.