Age | Commit message (Collapse) | Author |
|
File.extname now returns a dot string at a name ending with a dot.
[Bug #15267]
Notes:
Merged: https://github.com/ruby/ruby/pull/2565
|
|
|
|
* {String|Symbol}#match{?} with nil returns falsy
To improve consistency with Regexp#match{?}
* String#match(nil) returns `nil` instead of TypeError
* String#match?(nil) returns `false` instead of TypeError
* Symbol#match(nil) returns `nil` instead of TypeError
* Symbol#match?(nil) returns `false` instead of TypeError
* Prefer exception
* Follow empty ENV
* Drop outdated specs
* Write ruby/spec for above
https://github.com/ruby/ruby/pull/1506/files#r183242981
* Fix merge miss
|
|
|
|
|
|
|
|
My previous fix in d0ed935d5bf8c3fce9800742a36e44fb7f63dda4 was
not correct, as pointed out by cremno on GitHub.
This simplifies things by just using Kernel#to_s. Also switch to
bind_call(obj) instead of bind(obj).call for better performance.
Notes:
Merged: https://github.com/ruby/ruby/pull/2554
|
|
This rescues some exceptions that could happen with a closed or
shutdown DRb socket. This can prevent the server from
exiting if an client socket is closed directly after it is
accepted.
Fixes [Bug #8039]
Notes:
Merged: https://github.com/ruby/ruby/pull/2554
|
|
This makes it so that client instances that call a method on a
server-side object that raise a subclass of Exception are handled
similarly to those that raise a subclass of StandardError.
Only reraise exceptions that we are fairly sure we don't want to
rescue.
Fixes [Bug #5618]
Notes:
Merged: https://github.com/ruby/ruby/pull/2554
|
|
inside method
Calling these methods without an argument does not have the
desired effect inside a method.
Fixes [Bug #13249]
Notes:
Merged: https://github.com/ruby/ruby/pull/2562
|
|
|
|
|
|
* Makes it easier to copy-paste and add code backticks.
|
|
|
|
This reverts commit e8124729fbeaf159ae615f61980ee10018ed5134.
It worked once, but soon after that it stopped working again
https://travis-ci.org/ruby/ruby/jobs/598491972
|
|
|
|
This reverts commit 43015275b9a7f2833c93ad11ea96ae4cb3b7acd7.
`assert_raise_message` in test-unit is different from
`assert_raise_with_message`. It checks the exception message
only, but not the exception class,
|
|
|
|
Still some CIs are failing:
https://ci.appveyor.com/project/ruby/ruby/builds/28141041/job/v4hfc99sjefqabkk
http://ci.rvm.jp/results/trunk-vm-asserts@silicon-docker/2317313
I'll fix them later.
|
|
|
|
|
|
|
|
|
|
because it started to run on Travis.
|
|
Follow up https://github.com/ruby/ruby/pull/2559
According to experiments in https://github.com/ruby/ruby/pull/2560,
disabling cache seems to make arm64 build succeed.
|
|
|
|
|
|
and let RUBY_DEBUG=1 job test it.
We usually don't use --jit-debug and we should test no --jit-debug by
default.
|
|
misc-16234
|
|
When ruby2_keywords is used on a method, keywords passed to the method
are flagged. When the hash is passed as the last element of an
argument splat to another method, the hash should be treated as a
keyword splat. When keyword splatting a hash, a duplicate of the
hash is made. So when auto-splatting the hash with the keyword
flag, a duplicate of the hash should also be made.
This fixes cases where the hash is later passed to another method
and would be treated as keywords there:
class Object
ruby2_keywords def foo(*a) bar(*a) end
def bar(*a) baz(*a) end
def baz(*a, **kw) [a, kw] end
end
foo(:a=>1)
Previously, this would pass the :a=>1 as keywords to bar and also as
keywords to baz. Now it only passes :a=>1 as keywords to bar, but bar
passes :a=>1 as a positional hash to baz (which in this case
generates a warning in 2.7).
|
|
|
|
|
|
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/2556
|
|
of "setting Encoding.default_internal".
|
|
https://github.com/ruby/ruby/commit/f94202fcc228d0348ca050a7b18a8f8a538a7305#commitcomment-35505076
Co-Authored-By: Ary Borenszweig <asterite@gmail.com>
|
|
replaced "anObject" with "obj". also marked up with simple `_`s
instead of `<i>`.
|
|
https://github.com/rubygems/rubygems/commit/a7a673ce22
|
|
https://github.com/rubygems/rubygems/commit/97e9768612
|
|
|
|
|
|
https://rubyci.org/logs/rubyci.s3.amazonaws.com/openbsd-current/ruby-master/log/20191015T070011Z.fail.html.gz
```
1) Failure:
TestProcess#test_kill_at_spawn_failure [/home/chkbuild/chkbuild/tmp/build/20191015T070011Z/ruby/test/ruby/test_process.rb:2276]:
[ruby-core:69304] [Bug #11166].
<#<Thread:0x000009f60a7cac40@/home/chkbuild/chkbuild/tmp/build/20191015T070011Z/ruby/test/ruby/test_process.rb:2272 dead>> expected but was
<nil>.
``
|
|
|
|
[Bug #16250]
|
|
|
|
Some OS-level security features cause these methods to not return
expected results. For example fs.protected_regular sysctl on Linux,
or pledge(2)/unveil(2) on OpenBSD.
Fixes [Bug #16002]
|
|
|
|
maintained at thread scope.
|
|
https://github.com/flori/json/commit/565c72ba9e
|
|
https://github.com/flori/json/commit/0e99a9aac5
|