| Age | Commit message (Collapse) | Author |
|
On macOS, GNU coreutils `id` is limited to NGROUPS_MAX groups,
because of the backward compatibility of getgroups(2).
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/2822
|
|
This removes the warning that was added in
3802fb92ff8c83eed3e867db20f72c53932f542d, and switches the behavior
so that the eval does not use the binding's __FILE__ and __LINE__
implicitly.
Fixes [Bug #4352]
Notes:
Merged: https://github.com/ruby/ruby/pull/2816
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/2794
|
|
https://github.com/bundler/bundler/commit/29d932d72d
|
|
* MinGW - skip spec in spec/ruby/optional/capi/thread_spec.rb
C-API Thread function rb_thread_call_without_gvl
-- runs a C function with the global lock unlocked and unlocks IO with the generic RUBY_UBF_IO
stops/freezes spec tests
See https://bugs.ruby-lang.org/issues/16265
* MinGW - skip test test/resolv/test_dns.rb
Test times out in CI (both AppVeyor & Actions), cannot repo locally
* MinGW - skip test test/ruby/test_thread_queue.rb
* Add Actions mingw.yml
|
|
[Bug #16406]
|
|
* Deciding lambdaness of (f << g) using g
* Use version guards for spec changes
Notes:
Merged-By: XrXr
|
|
|
|
|
|
|
|
|
|
[Misc #16449][ruby-core:96458]
|
|
[Bug #16437]
|
|
We want to introduce consistency and better compatibility with unixen,
but the Windows APIs doues not have consistency fundamentally and
we can not found any logical way...
This reverts commit 61aff0cd189e67fa6f2565639ad0128fa33b88fc.
|
|
|
|
But not changes another cases, such as "file.rb."
[Bug #15267]
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/2289
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/2289
|
|
[Feature #16419]
|
|
Fixed misspellings reported at [Bug #16437], for default gems.
|
|
Fixed misspellings reported at [Bug #16437], only in ruby and rubyspec.
|
|
|
|
|
|
Since `did_you_mean` dropped its dependency on it.
Notes:
Merged: https://github.com/ruby/ruby/pull/2753
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/2753
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/2753
|
|
|
|
|
|
Thread#to_s returns simple Object#to_s until Ruby 2.4.
|
|
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/2738
|
|
This reverts commit 2a22a6b2d8465934e75520a7fdcf522d50890caf.
Revert [Feature #13083]
|
|
This reverts commit 452bee3ee8d68059fabd9b1c7a75661b14e3933e.
|
|
This reverts commit 31110d820cc1258cbc84b46ecc65b254c7d5529a.
|
|
This reverts commit 782d1b8fb0a039cedef9ad9c94f432dad51901e6.
|
|
* Process.clock_getres specs use 10_000 but that's quite slow for
the Process.times spec.
|
|
`* 1e6` makes a spurious result about floating point number's precision.
```
irb(main)[01:0]> 16.028
=> 16.028
irb(main)[02:0]> (16.028 * 1e6)
=> 16027999.999999998
```
|
|
|
|
|
|
|
|
https://github.com/ruby/spec/commit/51047687c0
https://github.com/ruby/spec/commit/2b87b467cc
|
|
|
|
1243255c3a36433041012b6107a5ac48658a0895 broke ci.rvm.jp tests like
http://ci.rvm.jp/results/trunk_clang_39@silicon-docker/2445098.
253232c028a5565dbeecc05fab5e81b35ab58bcc works only if getrusage is supported.
|
|
|
|
|
|
Asynchronous events such as signal trap, finalization timing,
thread switching and so on are managed by "interrupt_flag".
Ruby's threads check this flag periodically and if a thread
does not check this flag, above events doesn't happen.
This checking is CHECK_INTS() (related) macro and it is placed
at some places (laeve instruction and so on). However, at the end
of C methods, C blocks (IMEMO_IFUNC) etc there are no checking
and it can introduce uninterruptible thread.
To modify this situation, we decide to place CHECK_INTS() at
vm_pop_frame(). It increases interrupt checking points.
[Bug #16366]
This patch can introduce unexpected events...
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/2683
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/2683
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/2683
|