[#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:35755] Re: [Ruby 1.9 - Bug #4558] TestSocket#test_closed_read fails after r31230
KOSAKI Motohiro <kosaki.motohiro@gmail.com> wrote:
> > KOSAKI Motohiro <kosaki.motohiro@gmail.com> wrote:
> >> > Issue #4558 has been updated by Eric Wong.
> following scenario should be happen too.
>
> CPU1 CPU2 CPU3
> -------------------------------------------------------------------
> open() -> 5
> close(5)
> open() -> 5
> read(5) -> success, but read different data.
OK, I'm starting to think there's no safe way to handle these
situations, especially with MVM on the horizon. Just telling users to
stop doing close() in a different thread is probably the best way to
go...
> >> Hmm...
> >> If windows can't implement close() case, I doubt r30852 is correct fix.
> >> Is this really worth that *nix and windows have different spec?
> >
> > If r30852 is reverted, Linux (and maybe other *nix) will still break
> > threads out of blocking read/write with EBADF and
> > rb_io_wait_*able(fptr->fd) will raise IOError as long as we
> > assign fptr->fd = -1 before the actual close() call in IO#close.
> >
> > Maybe Windows (and possibly other OS) will be forced to call do_select()
> > to implement behavior consistent with Linux.
>
> ???
> I'm sorry, I haven't catch your point.
> Which issue is solved by calling do_select()?
It can reduce the likelyhood of read() being uninterruptable since
do_select() will sleep in 100ms intervals to check for interrupts on
win. There's still a small chance of blocking read() since select()
can have false positives and other threads could've drained the data...
> > On a related note, r30852 also has the problem with making IO#close an
> > O(n) operation since it needs to scan through all threads (and I'd like
> > to run thousands of threads :>).
>
> I have no opinion. I like faster software, but I haven't seen close
> makes performance bottleneck.
Contrived test case, but it gets worse as nr_thread increases:
# ruby 1.9.2p180 (2011-02-18 revision 30909) [x86_64-linux]
0.010000 0.000000 0.010000 ( 0.007288)
# ruby 1.9.3dev (2011-04-14 trunk 31267) [x86_64-linux]
0.030000 0.000000 0.030000 ( 0.033881)
-----------------------------8< -------------------------
require "benchmark"
nr_thread = 1_000
nr_close = 1_000
threads = nr_thread.times.map { Thread.new { sleep } }
puts(Benchmark.measure do
nr_close.times do
File.open(__FILE__).close
end
end)
threads.each { |thr| thr.run }.each { |thr| thr.join }
--
Eric Wong