[#82518] [Ruby trunk Feature#13618] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid — mame@...
Issue #13618 has been updated by mame (Yusuke Endoh).
5 messages
2017/08/30
[#82552] Re: [Ruby trunk Feature#13618] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid
— Eric Wong <normalperson@...>
2017/08/31
[email protected] wrote:
[#82756] Re: [Ruby trunk Feature#13618] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid
— Eric Wrong <normalperson@...>
2017/09/12
Eric Wrong <[email protected]> wrote:
[ruby-core:82279] [Ruby trunk Bug#13790] rubyspec.org domain seems to be expired
From:
ujihisa@...
Date:
2017-08-08 15:09:14 UTC
List:
ruby-core #82279
Issue #13790 has been reported by ujihisa (Tatsuhiro Ujihisa). ---------------------------------------- Bug #13790: rubyspec.org domain seems to be expired https://bugs.ruby-lang.org/issues/13790 * Author: ujihisa (Tatsuhiro Ujihisa) * Status: Open * Priority: Normal * Assignee: * Target version: * ruby -v: * Backport: 2.2: UNKNOWN, 2.3: UNKNOWN, 2.4: UNKNOWN ---------------------------------------- ## Summary Ruby codebase has http links to rubyspec.org, but the domain is likely owned by different person, and the web page shows completely different stuff. Should we replace these URLs, so that we don't accidentally lead people to that site, and optionally we don't raise the pagerank of that site? https://github.com/ruby/ruby/search?utf8=%E2%9C%93&q=rubyspec.org&type= ## Background and problem details Ruby included rubyspec couple years ago. There used to be http://www.rubyspec.org which hosted actual rubyspec info that we imagine. I'm not sure when it happened, but the rubyspec.org domain seems to be expired and is currently owned by somebody different, according to how it looks like right now. https://github.com/ruby/ruby/search?p=1&q=rubyspec.org&type=&utf8=%E2%9C%93 spec/rubyspec/library/net/http/http/send_request_spec.rb: This test sends an HTTP request to www.rubyspec.org just as an example. I'm surprised this test has been passing. Of course there won't be any guarantees that this passes in the future. spec/mspec/mspec.gemspec: very problematic spec/rubyspec/core/struct/inspect_spec.rb: (yay my name is there!) that issue is missing of course ## Proposed solution spec/rubyspec/library/net/http/http/send_request_spec.rb: Should we keep it? If we do, let's find another example spec/mspec/mspec.gemspec: replace it with this new url http://ruby.github.io/rubyspec.github.io/ spec/rubyspec/core/struct/inspect_spec.rb: refer webarchive url or just note that the url does not exist in the comment -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:[email protected]?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>