| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
| |
I think the wrong terminating argument cannot work.
To stop the noisy CI failures, the spec is tentatively suspended.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This spec fails too often
https://github.com/ruby/ruby/runs/529546249
https://github.com/ruby/ruby/runs/524933256
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This freezes the clone even if the receiver is not frozen. It
is only for consistency with freeze: false not freezing the clone
even if the receiver is frozen.
Because Object#clone is now partially implemented in Ruby and
not fully implemented in C, freeze: nil must be supported to
provide the default behavior of only freezing the clone if the
receiver is frozen.
This requires modifying delegate and set, to set freeze: nil
instead of freeze: true as the keyword parameter for
initialize_clone. Those are the two libraries in stdlib that
override initialize_clone.
Implements [Feature #16175]
|
| |
|
|
|
|
| |
Like `Symbol#to_proc` (f0b815dc670b61eba1daaa67a8613ac431d32b16)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
As a semantics, Hash#each yields a 2-element array (pairs of keys and
values). So, `{ a: 1 }.each(&->(k, v) { })` should raise an exception
due to lambda's arity check.
However, the optimization that avoids Array allocation by using
rb_yield_values for blocks whose arity is more than 1 (introduced at
b9d29603375d17c3d1d609d9662f50beaec61fa1 and some commits), seemed to
overlook the lambda case, and wrongly allowed the code above to work.
This change experimentally attempts to make it strict; now the code
above raises an ArgumentError. This is an incompatible change; if the
compatibility issue is bigger than our expectation, it may be reverted
(until Ruby 3.0 release).
[Bug #12706]
|
| |
|
| |
|
|
|
|
|
|
| |
[Bug #16497]
https://github.com/ruby/stringio/commit/4958a5ccab
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
FreeBSD
```
$ ruby -rsyslog -e 'Syslog.open("rubyspec", Syslog::LOG_PERROR) {|s| s.log(Syslog::LOG_ALERT, "Hello") }'
rubyspec 78462 - - Hello
```
Linux
```
$ ruby -rsyslog -e 'Syslog.open("rubyspec", Syslog::LOG_PERROR) {|s| s.log(Syslog::LOG_ALERT, "Hello") }'
rubyspec: Hello
```
https://github.com/freebsd/freebsd/commit/591ef7c8076109cff3c41f9bb50da996a34121e9
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, if an object has a singleton class, and you call
Object#method on the object, the resulting string would include
the object's singleton class, even though the method was not
defined in the singleton class.
Change this so the we only show the singleton class if the method
is defined in the singleton class.
Fixes [Bug #15608]
|
|
|
|
|
|
|
|
|
| |
When providing a single array to a block that takes a splat, pass the
array as one argument of the splat instead of as the splat itself,
even if the block also accepts keyword arguments. Previously, this
behavior was only used for blocks that did not accept keywords.
Implements [Feature#16166]
|
|
|
|
|
| |
As `String#split` with the default argument drops trailing newline
as a separator, preceding `String#chomp` is futile.
|
| |
|
|
|
|
|
|
| |
openbsd current seems to behave the same as other OSs.
https://rubyci.org/logs/rubyci.s3.amazonaws.com/openbsd-current/ruby-master/log/20200305T063005Z.fail.html.gz
|
| |
|
|
|
|
|
|
|
|
| |
Bumps [rake](https://github.com/ruby/rake) from 10.5.0 to 12.3.3.
- [Release notes](https://github.com/ruby/rake/releases)
- [Changelog](https://github.com/ruby/rake/blob/master/History.rdoc)
- [Commits](https://github.com/ruby/rake/compare/v10.5.0...v12.3.3)
Signed-off-by: dependabot[bot] <support@github.com>
|
| |
|
| |
|
|
|
|
| |
Fixes [Bug #13675]
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
So its arity should be -2 instead of -1.
[Bug #16640]
https://bugs.ruby-lang.org/issues/16640#change-84337
|
| |
|
|
|
|
| |
IP_MAX_MEMBERSHIPS seems not to be defined on Android
|
|
|
|
|
|
|
|
|
|
|
| |
FreeBSD's GETNAMEINFO(3) says:
> If a link-layer address or UNIX-domain address is passed to
> getnameinfo(), its ASCII representation will be stored in host. The
> string pointed to by serv will be set to the empty string if non-NULL;
> flags will always be ignored.
Android seems to behave like FreeBSD.
|
|
|
|
| |
User/group system on Android seems different from normal Linux.
|
|
|
|
|
|
| |
on Android
SOCK_SEQPACKET seems not to be supported on Android
|
|
|
|
|
| |
LOG_PERROR is defined on Android, but not implemented yet.
See also f3c4e620ac612eab6370b1fb82feaa4e651542bb.
|
|
|
|
| |
There is no /etc/passwd on Android
|
|
|
|
| |
There seems to be no _CS_PATH on Android.
|
|
|
|
| |
because there is no /tmp on Android.
|
|
|
|
|
| |
in the same way as FreeBSD and OpenBSD.
I guess that the spec makes too strong assumption.
|
|
|
|
|
|
|
| |
Android
nl_langinfo(CODESET) always returns UTF-8 on Android, regardless to
LC_ALL=C.
|
|
|
|
|
| |
I couldn't find a robust way to get the home path except ENV["HOME"] on
Android Termux.
|
|
|
|
|
|
|
|
| |
This behavior was deprecated in 2.7 and scheduled to be removed
in 3.0.
Calling yield in a class definition outside a method is now a
SyntaxError instead of a LocalJumpError, as well.
|
|
|
|
| |
MSpec requires Ruby 2.4 or more recent.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Under some Ext4 filesystem settings, a timestamp is limited up to
0x37fffffff (2446-05-10).
https://ext4.wiki.kernel.org/index.php/Ext4_Disk_Layout#Inode_Timestamps
> Therefore, timestamps should not overflow until May 2446.
Actually the spec fails under one of our CI environments, like:
```
1)
File.utime allows Time instances in the far future to set mtime and atime FAILED
Expected 2446 == 559444
to be truthy but was false
```
https://rubyci.org/logs/rubyci.s3.amazonaws.com/arch/ruby-master/log/20200208T180002Z.fail.html.gz
|
| |
|
|
|
|
|
|
| |
RDoc says nothing about them. Added an example that
ConditionVariable#wait can be woken up by
ConditionVariable#signal, instead.
|
| |
|
|
|
|
|
| |
Check if threads are stopped by Thread#stop? instead of the status
name.
|
| |
|
| |
|
|
|
|
|
|
|
| |
These specs were probably added in the commit to fully
separate keyword arguments after the release of 2.7.0, but
apparently not tested on 2.7 before hand. The enclosing
ruby_version guard for these specs limits them to 2.7.
|