[#35599] Proc#== behaviour on 1.8.7 and 1.9.2 — Adam Prescott <adam@...>
I've encountered a problem when using Proc#== (with both lambdas and
[#35613] [Ruby 1.9 - Feature #4539][Assigned] Array#zip_with — Yui NARUSE <redmine@...>
> http://redmine.ruby-lang.org/issues/4539
Hi,
[#35618] Redmine issues — Benoit Daloze <eregontp@...>
Hello,
[#35621] [Ruby 1.9 - Bug #4555][Open] [PATCH] ext/socket/init.c: rsock_connect retries on interrupt — Eric Wong <normalperson@...>
[#35629] [Ruby 1.9 - Bug #4473] Calling return within begin still executes else — Mayank Kohaley <redmine@...>
[#35631] [Ruby 1.9 - Bug #4558][Open] TestSocket#test_closed_read fails after r31230 — Tomoyuki Chikanaga <redmine@...>
> ----------------------------------------
KOSAKI Motohiro <kosaki.motohiro@gmail.com> wrote:
Tomoyuki Chikanaga <redmine@ruby-lang.org> wrote:
> Issue #4558 has been updated by Eric Wong.
KOSAKI Motohiro <kosaki.motohiro@gmail.com> wrote:
[#35632] [Ruby 1.9 - Bug #4559][Open] Proc#== does not match the documented behaviour — Adam Prescott <redmine@...>
(2012/11/28 16:10), matz (Yukihiro Matsumoto) wrote:
I believe this will be a spec change, albeit a small one. Can we
[#35636] [Ruby 1.9 - Feature #4560][Open] [PATCH] lib/net/protocol.rb: avoid exceptions in rbuf_fill — Eric Wong <redmine@...>
[#35637] [Ruby 1.9 - Bug #4561][Open] 1.9.2 requires parentheses around argument of method call in an array, where 1.8.7 did not — Dave Schweisguth <redmine@...>
[#35644] [Ruby 1.8 - Bug #4563][Open] Dir#tell broken — Daniel Berger <redmine@...>
[#35648] mvm branch status? — Eric Wong <normalperson@...>
Hello, I noticed the "mvm" branch in SVN hasn't been updated in over a year.
Hi Eric.
Has there been any thought on solving the C extension problem in MVM? In the present state, I've stopped working on it in Rubinius because there is no workable solution if there are C extensions in the mix.
Evan Phoenix <evan@fallingsnow.net> wrote:
On Thu, Apr 7, 2011 at 6:18 PM, Eric Wong <normalperson@yhbt.net> wrote:
[#35666] caching of the ancestor chain — Xavier Noria <fxn@...>
Why does Ruby cache the ancestors chain? I mean, not why the implementation implies that, but why it works that way conceptually.
Ah, in case it is not clear, where I find the metaphor broken is in that you can add methods to a mixin and have them available in classes that already included it, but if you include a new ancestor, then method dispatch in classes that already included the module aren't aware of the new chain.
Hi,
On Fri, Apr 8, 2011 at 7:56 PM, Yukihiro Matsumoto <matz@ruby-lang.org> wrote:
[#35678] [Ruby 1.9 - Bug #4564][Open] mingw-w64, truncate, ftruncate and ftello -- properly evalute it's existence — Luis Lavena <redmine@...>
[#35699] [Ruby 1.9 - Feature #4568][Open] [PATCH] file.c (rb_group_member): kill 256K of stack usage — redmine@...
[#35707] [Ruby 1.9 - Feature #4569][Open] Replace IPAddr with IPAddress — redmine@...
[#35713] [Ruby 1.9 - Bug #4571][Open] YAML.load given an ISO8601 timestamp creates an incorrect value for usec — redmine@...
[#35734] [Ruby 1.9 - Feature #4574][Open] Numeric#within — redmine@...
[#35753] [Ruby 1.9 - Bug #4576][Open] Range#step miss the last value, if end-exclusive and has float number — redmine@...
Hi,
2011/9/16 Kenta Murata <muraken@gmail.com>:
2011/9/16 Marc-Andre Lafortune <ruby-core@marc-andre.ca>:
On 16 September 2011 15:49, Tanaka Akira <akr@fsij.org> wrote:
Can somebody please reopen this issue? Since the test suite fix is
2011/9/17 Marc-Andre Lafortune <ruby-core@marc-andre.ca>:
2011/9/17 Tanaka Akira <akr@fsij.org>:
(2011/09/17 9:07), Tanaka Akira wrote:
I have not been watching ruby-core, but let me give a comment for this issue.
2011/9/17 Masahiro TANAKA <masa16.tanaka@gmail.com>:
2011/9/20 Tanaka Akira <akr@fsij.org>:
I haven't explained the reason of the error estimation in
On 21 September 2011 14:25, masa <masa16.tanaka@gmail.com> wrote:
[#35754] [Ruby 1.9 - Bug #4577][Open] (int...float).max should not raise an error — redmine@...
[#35759] [Ruby 1.8 - Bug #4578][Open] Fixnum.freeze not frozen? — redmine@...
[#35765] [Ruby 1.9 - Bug #4579][Open] SecureRandom + OpenSSL may repeat with fork — redmine@...
[#35777] hashes are not consistent across ruby processes? — Roger Pack <rogerdpack2@...>
Hello all.
[#35813] [Ruby 1.9 - Bug #4320] Bus Error in digest/sha2 on sparc — redmine@...
[#35814] [Ruby 1.9 - Bug #4320] Bus Error in digest/sha2 on sparc — redmine@...
[#35825] [Ruby 1.8 - Bug #4587][Open] RMATCH_REGS definition is wrong — redmine@...
[#35828] [Ruby 1.9 - Feature #4589][Open] add Queue#each() method and include Enumerable — redmine@...
[#35830] [Ruby 1.9 - Feature #3436] Spawn the timer thread lazily — redmine@...
[#35850] [Ruby 1.9 - Feature #4189] FileUtils#ln_r — Sakuro OZAWA <redmine@...>
[#35866] [Ruby 1.9 - Bug #4603][Open] lib/csv.rb: when the :encoding parameter is not provided, the encoding of CSV data is treated as ASCII-8BIT — yu nobuoka <nobuoka@...>
On Sun, Apr 24, 2011 at 1:33 AM, yu nobuoka <nobuoka@r-definition.com>wrote:
2011/4/25 James Gray <james@graysoftinc.com>:
On Sun, Apr 24, 2011 at 11:29 PM, NARUSE, Yui <naruse@airemix.jp> wrote:
[#35879] [Ruby 1.9 - Bug #4610][Open] Proc#curry behavior is inconsistent with lambdas containing default argument values — Joshua Ballanco <jballanc@...>
[#35883] [Ruby 1.9 - Bug #4611][Open] [BUG] Segementation fault reported — Deryl Doucette <me@...>
[#35895] [Ruby 1.9 - Feature #4614][Open] [RFC/PATCH] thread_pthread.c: lower RUBY_STACK_MIN_LIMIT to 64K — Eric Wong <normalperson@...>
[#35923] [Ruby 1.9 - Feature #4621][Open] NilClass#to_hash — Tsuyoshi Sawada <sawadatsuyoshi@...>
[#35933] [Ruby 1.9 - Bug #4623][Open] Consistent crash related to action_mailer — Alex Neth <alex@...>
[#35942] change in timeout error — Roger Pack <rogerdpack2@...>
Hello. Sorry if this is a repeat...
[#35943] [Ruby 1.9 - Feature #3905] rb_clear_cache_by_class() called often during GC for non-blocking I/O — Motohiro KOSAKI <kosaki.motohiro@...>
[ruby-core:35899] [Ruby 1.9 - Bug #4368] MiniTest::Assertions#assert_block ignores the given message.
Issue #4368 has been updated by Deryl Doucette.
We tested this against the following: 1.9.2 patch levels p136, p180, and p188 (revisions 30365, 30909, and 31204).
We came up with the same errors as shown by the following:
=== TEST FILE CONTENTS
require 'test/unit'
class TestingTest < Test::Unit::TestCase
def test_omg
assert_block("SEEING THE ACTUAL MESSAGE") { false }
end
end
=== TEST OUTPUT
pgpmbp:tmp pgpkeys$ ruby brain.rb
Loaded suite brain
Started
F
Finished in 0.000365 seconds.
1) Failure:
test_omg(TestingTest) [brain.rb:5]:
Expected block to return true value.
1 tests, 1 assertions, 1 failures, 0 errors, 0 skips
Test run options: --seed 8967
NOTE
----
The first revision to show correctly was revision 29036 (p0). Revision 30365 showed it correctly as well (p136).
So to summarize:
pgpmbp:tmp pgpkeys$ rvm use 1.9.2-p0
Using /Users/pgpkeys/.rvm/gems/ruby-1.9.2-p0
pgpmbp:tmp pgpkeys$ ruby brain.rb
Loaded suite brain
Started
F
Finished in 0.000618 seconds.
1) Failure:
test_omg(TestingTest) [brain.rb:5]:
SEEING THE ACTUAL MESSAGE.
Expected block to return true value.
1 tests, 1 assertions, 1 failures, 0 errors, 0 skips
Test run options: --seed 38217
pgpmbp:tmp pgpkeys$ rvm use 1.9.2-p136
Using /Users/pgpkeys/.rvm/gems/ruby-1.9.2-p136
pgpmbp:tmp pgpkeys$ ruby brain.rb
Loaded suite brain
Started
F
Finished in 0.000395 seconds.
1) Failure:
test_omg(TestingTest) [brain.rb:5]:
SEEING THE ACTUAL MESSAGE.
Expected block to return true value.
1 tests, 1 assertions, 1 failures, 0 errors, 0 skips
Test run options: --seed 58527
pgpmbp:tmp pgpkeys$ rvm use 1.9.2-p180
Using /Users/pgpkeys/.rvm/gems/ruby-1.9.2-p180
pgpmbp:tmp pgpkeys$ ruby brain.rb
Loaded suite brain
Started
F
Finished in 0.000374 seconds.
1) Failure:
test_omg(TestingTest) [brain.rb:5]:
Expected block to return true value.
1 tests, 1 assertions, 1 failures, 0 errors, 0 skips
Test run options: --seed 62205
pgpmbp:tmp pgpkeys$ rvm use 1.9.2-p188
pgpmbp:tmp pgpkeys$ ruby brain.rb
Loaded suite brain
Started
F
Finished in 0.000616 seconds.
1) Failure:
test_omg(TestingTest) [brain.rb:5]:
Expected block to return true value.
1 tests, 1 assertions, 1 failures, 0 errors, 0 skips
Test run options: --seed 34294
=== NOTE TO DEVS
So, p0 and p136 act almost correctly, but they display both the specified error message as well as the default error message. p188 or an earlier point release between p136 and p188 introduces an regression which reverts this behaviour to only showing the default error message.
It would be more appropriate if it displayed the custom error message only.
----------------------------------------
Bug #4368: MiniTest::Assertions#assert_block ignores the given message.
http://redmine.ruby-lang.org/issues/4368
Author: Nobuyoshi Nakada
Status: Closed
Priority: Normal
Assignee: Ryan Davis
Category: lib
Target version: 1.9.2
ruby -v: r30784
This method ignores the argument.
def assert_block msg = nil
assert yield, "Expected block to return true value."
end
--
http://redmine.ruby-lang.org