[#81492] [Ruby trunk Feature#13618] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid — normalperson@...
Issue #13618 has been reported by normalperson (Eric Wong).
12 messages
2017/06/01
[#88695] Re: [Ruby trunk Feature#13618] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid
— Eric Wong <normalperson@...>
2018/08/27
> https://bugs.ruby-lang.org/issues/13618
[#81569] [Ruby trunk Feature#12589] VM performance improvement proposal — vmakarov@...
Issue #12589 has been updated by vmakarov (Vladimir Makarov).
3 messages
2017/06/04
[#81581] [Ruby trunk Bug#13632] Not processable interrupt queue for a thread after it's notified that FD is closed in some other thread. — sir.nickolas@...
Issue #13632 has been reported by nvashchenko (Nikolay Vashchenko).
4 messages
2017/06/05
[#81590] Re: [ruby-cvs:66197] ko1:r59023 (trunk): revert r59020 because it may fail some tests sometimes on some environment (http://ci.rvm.jp/). This revert is to check the reason of failures. — Eric Wong <normalperson@...>
ko1@ruby-lang.org wrote:
5 messages
2017/06/06
[#81591] Re: [ruby-cvs:66197] ko1:r59023 (trunk): revert r59020 because it may fail some tests sometimes on some environment (http://ci.rvm.jp/). This revert is to check the reason of failures.
— Eric Wong <normalperson@...>
2017/06/06
Eric Wong <normalperson@yhbt.net> wrote:
[#81596] Re: [ruby-cvs:66203] Re: Re: ko1:r59023 (trunk): revert r59020 because it may fail some tests sometimes on some environment (http://ci.rvm.jp/). This revert is to check the reason of failures.
— Eric Wong <normalperson@...>
2017/06/06
Eric Wong <normalperson@yhbt.net> wrote:
[#81825] [Ruby trunk Feature#13697] [PATCH]: futex based thread primitives — normalperson@...
Issue #13697 has been reported by normalperson (Eric Wong).
3 messages
2017/06/29
[ruby-core:81820] [Ruby trunk Bug#13695] Issue with require and require_relative with symlinked directories
From:
ryan.rosenblum@...
Date:
2017-06-28 20:57:44 UTC
List:
ruby-core #81820
Issue #13695 has been updated by rrosenblum (Ryan Rosenblum). [rspec-duplicate-require](https://github.com/wconrad/rspec-duplicate-require) shows that this behavior has been around for at least 4 years. More recent discussions of this have been going on in [prawn](https://github.com/prawnpdf/prawn/pull/1026) and [pdf-core](https://github.com/prawnpdf/pdf-core/issues/30). ---------------------------------------- Bug #13695: Issue with require and require_relative with symlinked directories https://bugs.ruby-lang.org/issues/13695#change-65515 * Author: fidothe (Matt Patterson) * Status: Open * Priority: Normal * Assignee: * Target version: * ruby -v: ruby 2.4.1p111 (2017-03-22 revision 58053) [x86_64-darwin16] * Backport: 2.2: UNKNOWN, 2.3: UNKNOWN, 2.4: UNKNOWN ---------------------------------------- Symlinked directories cause an issue with require_relative where libraries loaded from a symlinked path (e.g. in a typical Capistrano / Bundler deployment) can be double-loaded. Reproduce process: 1. Clone git repo from https://github.com/fidothe/symlink-require 2. Run `use-symlink.rb` script: ~~~ bash $ ruby use-symlink.rb ~~~ Expected result: No warning from double-loading of constants issued. Actual result: double-loading of file causing already-initialised constant warning. In the example I linked above, `target.rb` uses `require_relative` to load `dependent.rb`. When the example also requires `dependent.rb` the file is double-loaded and we see a warning about already-initialized constant. The problem is that when `require` in `use-symlink.rb` (line 7) checks the set of loaded files it uses an absolute path containing the symlink (since that is what was added to $LOAD_PATH), but when `require_relative` in target.rb is called, it uses an absolute path containing target of the symlink, causing the double-load. Is this discrepancy intended behaviour on Ruby's part? -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>