Activity
From 08/23/2017 to 08/29/2017
08/29/2017
-
06:40 PM Bug #13846: Openbsd possible memory leak when using Thread
- I installed 2.5.0-dev (from github) and seems that this bug does not occur or at least it is fixed. I believe that it might be related to #13772. My daemons started with low memory around 30mb and ended up after a week to 300mb with high...
-
02:14 PM Bug #13846: Openbsd possible memory leak when using Thread
- I've confirmed this also happens with the current version of OpenBSD and ruby 2.4.1. I'll have to write a C version to see if this is a problem with OpenBSD's thread library. If not, it's probably an issue with ruby. Hopefully I'll ha...
-
08:14 AM Bug #13846 (Closed): Openbsd possible memory leak when using Thread
- On openBSD 5.9/6.1 running this code causes RSS memory to increase without limit. This does not happen in ubuntu or other linux.
~~~ ruby
loop do
thr = Thread.new { puts "thread test" }
thr.join
GC.start
end
~~~
This is... -
06:26 PM Bug #13844: Toplevel returns should fire ensures
- Oh also...IRB is a very weird beast. The code you enter isn't really running at toplevel; it's running in an eval that's likely within a block or method scope (I haven't looked recently). As a result, things you'd expect to work at tople...
-
06:25 PM Bug #13844: Toplevel returns should fire ensures
- I do not assume it was intentional, but it was codified by tests added along with the toplevel return change. See test_syntax.rb in test_return_toplevel, where it tests that each of the following lines should exit silently:
```ruby
r... -
06:30 AM Bug #13844: Toplevel returns should fire ensures
- This is indeed weird that the blocks are treated differently depending on whether they
are defined in a method or outside of it. I do not assume that this was intentional.
On a side note, interestingly, the last variant aka:
```ru... -
05:23 PM Bug #13848: BigDecimal.new('200.') raises an exception
- I believe you mean for BigDecimal.new('200.') to be equivalent to BigDecimal.new('200.0')?
I could see both ways be ok; there may be use cases where the error is better because of
the user not being explicit enough; or the user does ... -
12:24 PM Bug #13848 (Closed): BigDecimal.new('200.') raises an exception
- BigDecimal.new('200.') raises an exception:
ArgumentError: invalid value for BigDecimal(): "200."
It should accept this as a valid decimal number.
This requires fixing numbers read in from the wild. -
12:13 PM Revision 4b9aeef1 (git): array.c: use rb_check_array_type
- * array.c (ary_join_1): simplified by rb_check_array_type.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@59688 b2dd03c8-39d4-4d8f-98ff-823fe69b080e - 11:52 AM Revision f32e46b7 (git): * remove trailing spaces.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@59687 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
11:52 AM Revision 4790c089 (git): Merge rdoc-6.0.0.beta1.
- This version fixed strange behavior of ruby code parser.
We will list all of impromovement to Changelog when 6.0.0 releasing.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@59686 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
11:35 AM Revision 26a9bf75 (git): array.c: nested encoding
- * array.c (ary_join_1): ignore encodings in nested arrays as an
initial encoding.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@59685 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
11:33 AM Feature #13847: Gem activated problem for default gems
- > Also, in this use case, it seems to be enough to use [..]
> ...
Matz will decide but I wanted to comment on what Hiroshi Shibata wrote.
Kernel require presently accepts no additional arguments:
https://ruby-doc.org/core-2.4.... -
09:27 AM Feature #13847: Gem activated problem for default gems
- hsbt (Hiroshi SHIBATA) wrote:
> Unfortunately, since rubygems has required openssl before the bundler runs it will result in an activated error like this:
> ...
Off-topic, but in this specific case, the root of the problem is that bund... -
08:53 AM Feature #13847 (Assigned): Gem activated problem for default gems
- If you try to use some default gems with a fixed version using Bundler, there are cases where the current RubyGems/Bundler/Ruby specification can not be used with the version specified by the user.
For example
```
$ ruby -v
ruby ... -
10:49 AM Revision cb70a92e (git): array.c: join encoding
- * array.c (ary_join_1): copy the encoding of the converted string
of the first element by to_str too, as an initial encoding.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@59684 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
10:22 AM Revision 9d990931 (git): Partly reverted r59642. Because IO#close is idempotent since Ruby 2.3.
- Reported by Eric Wong. Thank you.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@59683 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
10:17 AM Bug #13794: Infinite loop of sched_yield
- Apologies for my delay in replying. I have not yet had an opportunity to fully test any of these patches (apart from my initial hack which did not work). I will aim to test your patch as soon as possible. Thank you for your assistance!
-
09:06 AM Bug #13769 (Assigned): IPAddr#ipv4_compat incorrect behavior
-
08:25 AM Bug #13769: IPAddr#ipv4_compat incorrect behavior
- I'd vote for marking it deprecated & fixing the bug in the original ticket. Despite the fact that the addresses are now deprecated, it may be useful for ruby code to interact with or check for legacy situations - that's how I found the bug
-
08:02 AM Bug #13769: IPAddr#ipv4_compat incorrect behavior
- RFC4291 says: '"IPv4-Compatible IPv6 address" is now deprecated.'
We can remove #ipv4_compat? or mark it as deprecated.
Section 2.5.5.1.
The "IPv4-Compatible IPv6 address" is now deprecated because the
current IPv6 transition ... -
08:43 AM Bug #4731 (Rejected): ruby -S irb fails with mingw/msys vanilla builds
- I couldn't reproduce this with RubyInstaller 2.4.1-2.
-
08:18 AM Bug #13831 (Third Party's Issue): error when try to install
- I couldn't reproduce this.
```
C:\Users\hsbt>gem i sass
Fetching: sass-listen-4.0.0.gem (100%)
Successfully installed sass-listen-4.0.0
Fetching: sass-3.5.1.gem (100%)
Successfully installed sass-3.5.1
Parsing documentation for ... -
08:14 AM Bug #13843 (Assigned): [PATCH] RubyGems 2.6.13 - Align lib/rubygems/resolver.rb with rubygems/rubygems
-
08:14 AM Bug #13652 (Rejected): Ruby 2.3.4 does not catch Argument error when comparing DateTime with String
- It can't be reproduced.
```
% ruby -v -r "date" -e "p DateTime.parse == 'No End Date'"
ruby 2.5.0dev (2017-08-29 trunk 59656) [x86_64-darwin15]
false
``` -
07:41 AM Bug #11174: threads memory leak
- I am having similar issue. Even calling open3.capture2 which uses threads results into 250mb of rss memory after a day. 2.3.4 and all 2.3.x.. ,2.4.x
-
07:11 AM Revision 3895e300 (git): test/ruby: tweaked heredocs
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@59682 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
07:01 AM Revision 480c84e1 (git): fix error message.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@59681 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
06:24 AM Revision 174fd5fd (git): .gitignore: ignore run.gdb
- * .gitignore: ignore run.gdb which is assumed to be generated
by make gdb and customized manually during development
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@59680 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
04:58 AM Revision f70827b7 (git): resolv.rb: remove unnecessary require statement
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@59679 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
04:50 AM Bug #9639: libyaml not found, rubygems not functional on freebsd with ruby 2.1.0
- I couldn't reproduce FreeBSD 11.0 and Ruby 2.1.10.
08/28/2017
-
11:51 PM Bug #13794: Infinite loop of sched_yield
- charlie@atech.media wrote:
> Eric Wong <normalperson@yhbt.net> wrote:
> > How about checking owner_process before incrementing?
>
> I'm afraid this fix doesn't quite match up in my mind. To
> clarify, I am suggesting that timer_th... -
11:26 PM Bug #13845 (Closed): thread_win32.c: set thread name breaking mswin builds on appveyor and at rubyci
- Applied in changeset trunk|r59678.
----------
win32.c: fix function pointer
* win32/win32.c (rb_w32_set_thread_description): fix the condition
if the API function pointer is found.
[ruby-core:82494] [Bug #13845] -
08:26 PM Bug #13845 (Closed): thread_win32.c: set thread name breaking mswin builds on appveyor and at rubyci
- The commit [svn 59660 thread_win32.c: set thread name](https://github.com/ruby/ruby/commit/19d692920d2d207c3aa891fc79aa5a93c17f84c6) is breaking builds on both appveyor and at rubyci.
It appears to be using a function that is only sup... -
11:25 PM Revision c5683c9a (git): win32.c: fix function pointer
- * win32/win32.c (rb_w32_set_thread_description): fix the condition
if the API function pointer is found.
[ruby-core:82494] [Bug #13845]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@59678 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
08:20 PM Bug #13844: Toplevel returns should fire ensures
- See https://github.com/jruby/jruby/issues/4761 for our placeholder bug for this missing feature.
-
08:20 PM Bug #13844 (Closed): Toplevel returns should fire ensures
- In the following contexts, a return always fires the ensure that wraps it:
```
[] ~/projects/ruby $ ruby -e 'def foo; return; ensure; p :x; end; foo'
:x
[] ~/projects/ruby $ ruby -e 'def foo; 1.times { begin; return; ensure; p :x... -
07:36 PM Feature #4840: Allow returning from require
- Ahh great, thank you for the pointer, nobu!
-
04:49 PM Feature #4840: Allow returning from require
- test/ruby/test_syntax.rb:test_return_toplevel
-
03:49 PM Feature #4840: Allow returning from require
- Were any tests or specs added for this feature? I don't see anything recent added to language/return_spec.rb and the related commits don't show any additions to MRI's tests.
I believe we need at least one of these to be filled out. I'... - 04:05 PM Revision 9f675c5b (git): * 2017-08-29
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@59677 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
04:05 PM Revision c5e4070c (git): Increase STACKFRAME_FOR_CALL_CFUNC
- On below env, miniruby requires 568 and ruby requires 838 to pass.
* ruby -v: ruby 2.5.0dev (2017-08-28 trunk 59670) [x86_64-freebsd10.3]
* gcc8 (FreeBSD Ports Collection) 8.0.0 20170828 (experimental)
git-svn-id: svn+ssh://ci.ruby-lang... -
04:02 PM Bug #13843: [PATCH] RubyGems 2.6.13 - Align lib/rubygems/resolver.rb with rubygems/rubygems
- At rubygems/rubygems, the patch for resolver.rb was accepted first, then the patch to extend appveyor testing to include trunk was accepted.
[Appveyor results](https://ci.appveyor.com/project/segiddins/rubygems/build/634) and [Travis ... -
01:28 PM Bug #13843 (Rejected): [PATCH] RubyGems 2.6.13 - Align lib/rubygems/resolver.rb with rubygems/rubygems
- Currently, the file `lib/rubygems/resolver.rb` differs between ruby/ruby and rubygems/rubygems in the `search_for` method.
Attached patch aligns them and adds the test for it, which is also missing from ruby/ruby. Tested against MinG... -
02:21 PM Revision 4446f528 (git): compile.c: compile_if
- * compile.c (compile_if): extract from iseq_compile_each.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@59675 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
11:20 AM Revision 14638d85 (git): [DOC] Fix typo in rdoc of `transform_values!` [ci skip]
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@59674 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
10:55 AM Revision b3c70d4c (git): string.c: fix potential bug in String#split
- * string.c (rb_str_split_m): fix potential bug when rb_memsearch()
matches a octet in the middle of a multi-byte character sequence.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@59673 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
08:31 AM Revision c5da5b1e (git): Merge rubygems-2.6.13.
- see details for this update:
http://blog.rubygems.org/2017/08/27/2.6.13-released.html
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@59672 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
08:07 AM Bug #13842 (Closed): Backport request: Rubygems-2.6.13
- Rubygems-2.6.13 has been released now.
Its version was required to backport all stable versions of Ruby.
I created patches about rubygems 2.6.13.
For Ruby 2.2 and 2.3: These patches contain only security fixes of rubygems-2.6.13
... -
07:54 AM Revision 1a193018 (git): lib/csv.rb: refactor and optimize. This change
- includes the patch from marshall-lee.
close #1168
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@59671 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
01:48 AM Bug #13841 (Closed): Segmentation fault in Ruby CFUNC :to_s
- Hi, a segmentation fault was found in my environment.
~~~ text
E, [2017-08-25T16:21:37.798828 #632] ERROR -- : reaped #<Process::Status: pid 30125 SIGABRT (signal 6) (core dumped)> worker=2
I, [2017-08-25T16:21:37.826008 #30226] I... -
12:58 AM Bug #13167: Dir.glob is 25x slower since Ruby 2.2
- ahorek (Pavel Rosický) wrote:
> There's no need to call it for each directory because the result will always be same.
It is not same.
Path components in middle also should be replaced.
08/27/2017
-
04:22 PM Bug #13167: Dir.glob is 25x slower since Ruby 2.2
- https://github.com/ruby/ruby/pull/1685
I reverted nobu's change and instead of recursion for simple patterns I want to call "replace_real_basename" only for results. There's no need to call it for each directory because the result wil... -
04:18 PM Revision a2f5275e (git): compile.c: compile_ensure
- * compile.c (compile_ensure): extract from iseq_compile_each.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@59670 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
04:15 PM Revision 79992090 (git): compile.c: compile_resbody
- * compile.c (compile_resbody): extract from iseq_compile_each.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@59669 b2dd03c8-39d4-4d8f-98ff-823fe69b080e - 04:04 PM Revision fc1714be (git): * 2017-08-28
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@59668 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
04:04 PM Revision c1b32b5a (git): compile.c: compile_rescue
- * compile.c (compile_rescue): extract from iseq_compile_each.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@59667 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
02:27 PM Misc #13840 (Rejected): Collection methods - stability
- I'm trying to fix some method code (`Gem::Resolver#search_for`) in rubygems.
Regardless, in simplifying the code, I was left with one question regarding all of the sort/filter group methods in ruby.
Which ones are considered stable... -
06:32 AM Revision 21e4ade5 (git): lib/net/imap.rb: Accept continuation requests without response text
- The IMAP server of DOCOMO returns such continuation requests.
[ruby-list:50558]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@59666 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
08/26/2017
-
11:39 PM Feature #13828 (Closed): Win32ole extension should support licensed COM servers
- Applied in changeset trunk|r59665.
----------
* ext/win32ole/win32ole.c (fole_initialize): support licensed COM server. Thanks to Gray Wolf. [Feature :#13828] -
11:39 PM Revision 917beef3 (git): * ext/win32ole/win32ole.c (fole_initialize): support licensed COM server. Thanks to Gray Wolf. [Feature :#13828]
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@59665 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
09:02 PM Revision 6582a2f6 (git): vcs.rb: refresh after dcommit
- * tool/vcs.rb (VCS::GIT#commit): refresh until sync after dcommit.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@59664 b2dd03c8-39d4-4d8f-98ff-823fe69b080e - 08:55 PM Revision 6de143f6 (git): * 2017-08-27
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@59663 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
08:55 PM Revision 9cfc7442 (git): NEWS: Thread#name= on Windows [ci skip]
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@59662 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
04:13 PM Feature #13839: String Interpolation Statements - Yes templating is not a key factor for large modern PHP projects, but you need to go back in late 90s. That was the start of the web. A lot of people wanted to publish their things, so they wrote HTML pages. Often they knew nothing about...
-
07:23 AM Feature #13839: String Interpolation Statements
- > I was listening a talk by Rasmus Lerdorf, the creator of PHP.
> ...
I do not think that templating was the killer feature of PHP.
I have not systematically analyzed the codebase of phpBB, mediawiki,
drupal or wordpress but I doubt... -
02:14 AM Feature #13839: String Interpolation Statements - k0kubun (Takashi Kokubun) wrote:
> Ah okay, so expected feature is only "%{3.times do}Hello #{'World'}%{end}" and a multi-line complex usage would be:
> ...
Yes, that's it! :) I just wanted to improve string interpolation with %{statem... -
02:04 AM Feature #13839: String Interpolation Statements
- Ah okay, so expected feature is only "%{3.times do}Hello #{'World'}%{end}" and a multi-line complex usage would be:
~~~
<<EOS
%{if true}
Hello #{'world'}
%{end}
EOS
~~~ -
01:53 AM Feature #13839: String Interpolation Statements - > You should write expected code in valid Ruby syntax. Guessing from "%{3.times do}Hello #{'World'}%{end}", probably you intended:
> ...
It was an idea that we could use a different notation: %{statement} instead of {% statement %} to b... -
01:46 AM Feature #13839 (Feedback): String Interpolation Statements
- You wrote:
~~~
{% if true %}
Hello #{'World'}
{% end %}
Template.new('...').render(binding)
~~~
You should write expected code in valid Ruby syntax. Guessing from "%{3.times do}Hello #{'World'}%{end}", probably you intende... -
01:34 AM Feature #13839: String Interpolation Statements - Thanks for your feedback Jeremy. :) (I have much gratitude for all your work in Ruby!)
Yes, I didn't think of this as a replacement for a full featured template engine (with cache, helpers and so), but more as a quick and powerful way... -
02:22 PM Revision 420efa9c (git): win32.c: fix return value
- * win32/win32.c (rb_w32_set_thread_description_str): return the
result when name is nil.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@59661 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
02:26 AM Feature #13801: Implement case equality test for Set#===
- > I expect Set to act almost like Array [...]
But why? Aside from both being collections, there is no connection. Ruby's Set isn't even implemented with an Array.
The core mathematical definition of Set is based on element member... -
12:30 AM Revision 19d69292 (git): thread_win32.c: set thread name
- * thread_win32.c (native_set_another_thread_name): set thread name
by SetThreadDescription.
* win32/win32.c (rb_w32_set_thread_description): dynamically try
SetThreadDescription.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@59...
08/25/2017
-
11:44 PM Feature #13839: String Interpolation Statements
- It might be better to compare this to Erubi, the current default ERB template processor in Rails and Tilt. While this approach is fast for small strings, it's actually slower for large strings (probably due to the use of `+=` instead of...
-
10:34 PM Feature #13839 (Rejected): String Interpolation Statements - Hello!
Here is a KISS implementation of a template engine in Ruby:
~~~ ruby
class Template
attr_reader :input
def initialize(input)
@input = input
end
def output
"output = %\0" + @input.gsub("{%", "\0... - 03:47 PM Revision c150c787 (git): * 2017-08-26
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@59659 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
03:47 PM Revision 11d419ad (git): `$IGNORECASE` is no longer effective. [ci skip]
- * lib/English.rb: [DOC] `$IGNORECASE` is no longer effective.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@59658 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
12:01 PM Bug #13757: TestBacktrace#test_caller_lev segaults on PPC
- BTW, very likely unrelated, but I noticed, that on PCC64 (BE), the C level backtrace is not correctly collected. It looks like:
~~~
-- C level backtrace information -------------------------------------------
[0x4ef7a734]
[0x4ef7a8... -
11:54 AM Bug #13757: TestBacktrace#test_caller_lev segaults on PPC
- Ok, so I did my homework :) It started with r59047 and it is issue for ppc64/ppc64le. No other Fedora architectures are affected. Since this release, the test suite always get stuck at TestBacktrace#test_caller_lev. Later, since r59159, ...
-
08:13 AM Revision 20c5f607 (git): csv.rb: optimize CSV::Table#to_a and #to_csv
- * lib/csv.rb (CSV::Table#to_a, #to_csv): use Array#push instead of
Array#concat for performance improvement. This performance improvement is
proposed by zdennis <zach.dennis@gmail.com>. The patch is from
Mau Magnaguagno <maumagnagu... -
03:41 AM Revision c0baa381 (git): compile.c: unreachable chunk
- * compile.c (iseq_peephole_optimize): remove unreachable chunk
which appeared by useless jump elimination.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@59656 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
03:33 AM Revision ed3a575b (git): compile.c: useless jump elimination
- * compile.c (iseq_peephole_optimize): eliminate useless if/unless
just before jump.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@59655 b2dd03c8-39d4-4d8f-98ff-823fe69b080e - 02:37 AM Revision 5ccf7b06 (git): * 2017-08-25
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@59654 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
02:37 AM Revision 0faeb903 (git): compile.c: moved comments [ci skip]
- * compile.c (iseq_peephole_optimize): moved comments inside proper
blocks.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@59653 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
02:16 AM Feature #13801: Implement case equality test for Set#===
- Here's a counterexample with Array:
~~~ ruby
[1, 2, 3] === 2 #=> false
~~~
Array#=== doesn't look inside the array. I expect Set to act almost like Array, so it would be weird if Set#=== looked inside the container but Array#=== ... -
02:03 AM Bug #13835: Using 'open-uri' with 'tempfile' causes an exception
- Turns out that `open(temp_file, 'a')` works with the original open, but fails after loading open-uri.
This is because the instances of Tempfile respond to `to_path`, just like instances of File or Pathname. So `open(temp_file, 'a')` a... -
01:55 AM Feature #11105: ES6-like hash literals
- It makes many conflicts with the current syntax.
I don't think it is easy to resolve. -
01:04 AM Feature #13667: Add Coverage.running? to quickly check if Coverage is enabled.
- I also think `running?` is better. And I feel `#test_coverage_running?` is good enough :)
-
12:56 AM Feature #13667: Add Coverage.running? to quickly check if Coverage is enabled.
- Sorry for the late reply. I'm positive for this proposal.
There is the same request #13838, which reminds me of this ticket. That issue proposes `Coverage.enabled?`. I'm unsure, but `running?` seems a bit better to me because the s... -
01:01 AM Feature #13838: Add the ability to detect Coverage status
- Sorry I overlooked the issue :)
-
12:57 AM Feature #13838 (Closed): Add the ability to detect Coverage status
- I think this is a duplicate of #13667. Let us discuss this issue in that ticket. Thank you!
-
12:30 AM Feature #13838 (Closed): Add the ability to detect Coverage status
- ## Description
I want to detect current status of Coverage, which is enabled or not.
Now we can detect status only trying `Coverage.peek_result` or `Coverage.result` and catch RuntimeError.
Attached patch enable us to detect status ...
08/24/2017
-
10:26 PM Feature #11105: ES6-like hash literals
- This ES6 syntax for hash literals looks strange to me. I have never seen it before today, but I have not written JavaScript for a few years, and I am not using Ruby for web development.
Two things puzzle me:
1. What is the key in `... -
03:55 AM Feature #11105: ES6-like hash literals
- This syntax is now widely known and popular in the JavaScript/ES world. It is frequently used in everyday code and we've grown used to it.
-
07:40 AM Feature #8781: Use require_relative() instead of require() if possible
- Martin Dürst wrote back then:
> On the other hand, 'require' has a tighter coupling to the file
> ...
Both have a similar requirement - you need to pass in the name of
the file at question.
Both also require some information to t... -
07:31 AM Revision 7971a124 (git): compile.c: show failed instructions
- * compile.c (iseq_set_sequence): show failed instructions at
adjuststack mismatch.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@59652 b2dd03c8-39d4-4d8f-98ff-823fe69b080e - 07:26 AM Revision 20c29411 (git): * 2017-08-24
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@59651 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
07:26 AM Revision 37228c0f (git): compile.c: free before adjust error
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@59650 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
08/23/2017
-
04:47 PM Bug #13837: Class attributes get overshadowed by local variables
- shevegen (Robert A. Heiler) wrote:
> Even the old pickaxe mentions that ruby may behave slightly unexpected
> ...
I still can't consider this correct behavior. Aren't the multi-line and the single-line ways of writing `if` supposed to ... -
04:29 PM Bug #13837: Class attributes get overshadowed by local variables
- I think hanmac already gave the correct answer so there is no point in me adding
much to it. :)
Note that you could specifically point ruby to call the getter method in the
line hanmac pointed out, rather than using:
bar = 0... -
12:27 PM Bug #13837: Class attributes get overshadowed by local variables
- ruby does parse the lines before exceute them.
so when ruby does read this:
~~~ ruby
bar = 0 if bar.nil?
~~~
it finds that you assign a local variable bar in this contect.
now it does always use the local variable instead of me... -
09:37 AM Bug #13837 (Closed): Class attributes get overshadowed by local variables
- ~~~ ruby
irb(main):001:0> RUBY_VERSION
=> "2.4.1"
irb(main):002:0> class Foo
irb(main):003:1> attr_accessor :bar
irb(main):004:1> def initialize
irb(main):005:2> self.bar = 1
irb(main):006:2> end
irb(main):007:1> def ... -
04:01 AM Bug #13832 (Closed): cfp consistency error occurred in vm_call_cfunc on non-optimized ruby
- Applied in changeset trunk|r59649.
----------
gc.c: restore cfp at finalizer
* gc.c (run_finalizer): restore cfp for the case an exception
raised in a finalizer. [ruby-core:82432] [Bug #13832] -
04:01 AM Revision 1fe73fc9 (git): gc.c: restore cfp at finalizer
- * gc.c (run_finalizer): restore cfp for the case an exception
raised in a finalizer. [ruby-core:82432] [Bug #13832]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@59649 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
03:14 AM Revision 9b2d518a (git): skip unless finalizers run
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@59648 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
02:26 AM Revision 0f711026 (git): gc.c: run all finalizers
- * gc.c (run_finalizer): revert r59155 partially. finalizing loop
should continue even after an exception is rescued.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@59647 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
02:23 AM Bug #13836 (Closed): Null pointer dereference in defined_expr0()
- Applied in changeset trunk|r59644.
----------
parse.y: primary should not be 0
* parse.y (primary): should not be 0, since it can be a receiver.
[ruby-core:82447] [Bug #13836] - 02:23 AM Revision e96ba1d6 (git): * 2017-08-23
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@59646 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
02:23 AM Revision e553df86 (git): remove debug code.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@59645 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
12:09 AM Bug #13794: Infinite loop of sched_yield
- charlie@atech.media wrote:
> File sched_yield_1.patch added
> The patch above does not work because
> native_reset_timer_thread runs after fork in the parent.
> Attached an alternative patch that runs in gvl_atfork and
> appears ...