| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
|
|
|
|
|
| |
Make core class updates section use a consistent format. Alphabetize
core class updates section by class name, and stdlib updates section
by library name. Minor formatting changes while here.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
http://rubyci.s3.amazonaws.com/ubuntu/ruby-master/log/20201203T123002Z.log.html.gz
```
/home/chkbuild/chkbuild/tmp/build/20201203T123002Z/ruby/test/ruby/test_io.rb:1830:
warning: method redefined; discarding old test_each_byte
/home/chkbuild/chkbuild/tmp/build/20201203T123002Z/ruby/test/ruby/test_io.rb:376:
warning: previous definition of test_each_byte was here
test/unit warning: method TestIO#test_each_byte is redefined
/home/chkbuild/chkbuild/tmp/build/20201203T123002Z/ruby/test/ruby/test_io.rb:1849:
warning: method redefined; discarding old test_each_char
/home/chkbuild/chkbuild/tmp/build/20201203T123002Z/ruby/test/ruby/test_io.rb:1799:
warning: previous definition of test_each_char was here
test/unit warning: method TestIO#test_each_char is redefined
```
|
| |
|
| |
|
|
|
|
| |
https://github.com/ruby/ipaddr/commit/d2ec7cc3ee
|
|
|
|
| |
https://github.com/ruby/ipaddr/commit/90b46678a5
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Remove jruby-9.1.17.0 from CI
https://github.com/ruby/forwardable/commit/08d92a9c39
|
|
|
|
| |
https://github.com/ruby/readline-ext/commit/897ffe26a6
|
|
|
|
| |
https://github.com/ruby/readline-ext/commit/6d55854434
|
| |
|
|
|
|
| |
https://github.com/ruby/io-wait/commit/664c93b2ff
|
|
|
|
| |
https://github.com/ruby/io-wait/commit/4434b10e46
|
|
|
|
| |
https://github.com/ruby/io-wait/commit/12cce69ddf
|
|
|
|
|
|
| |
See rubygems/rubygems@8a81183236c4475152798db99734e89779287331.
https://github.com/ruby/io-wait/commit/04857e0cf5
|
|
|
|
| |
https://github.com/ruby/io-nonblock/commit/8b7abbd1b5
|
|
|
|
| |
https://github.com/ruby/io-nonblock/commit/9fa3ad9c7a
|
|
|
|
|
|
| |
See rubygems/rubygems@8a81183236c4475152798db99734e89779287331.
https://github.com/ruby/io-nonblock/commit/e14f7952c1
|
|
|
|
| |
https://github.com/ruby/digest/commit/aa048ce345
|
|
|
|
| |
https://github.com/ruby/digest/commit/502a12587c
|
| |
|
|
|
|
|
| |
for an MJIT worker thread. We can't do it because its GET_EC() returns
NULL.
|
| |
|
|
|
|
|
|
|
|
|
| |
This commit deletes
{IO,ARGF,StringIO,Zib::GZipReader}#{bytes,chars,lines,codepoints}, which
have been deprecated since c47c095b9740e7c19d6fdca29ab661c1089221d4.
Note that String also has those methods. They are neither depreacted
nor deleted because they are not aliases of counterpart each_something.
|
|
|
|
| |
Thought it was not a bad idea to document these CAPI. [ci skip]
|
|
|
|
|
| |
new_prev_env is stored in the env_body memory block but this is not
a GC root, so new_prev_env could be freed.
|
|
|
|
|
| |
When we allocate new pages, allocate them on the end of the linked list.
Then when we compact we can move things to the head of the list
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Quantifier reduction when using +?)* and +?)+ should not be done
as it affects which text will be matched.
This removes the need for the RQ_PQ_Q ReduceType, so remove the
enum entry and related switch case.
Test that these are the only two patterns affected by testing all
quantifier reduction tuples for both the captured and uncaptured
cases and making sure the matched text is the same for both.
Fixes [Bug #17341]
|
| |
|
|
|
|
|
|
|
|
| |
Incremental sweeping should sweep until we find a slot for objects to
use. `heap_increment` was adding a page to the heap even though we
would sweep immediately after.
Co-authored-by: John Hawthorn <john@hawthorn.email>
|
|
|
|
| |
Has been deprecated since 373282f6656d3d3d989d261e7a95f8e81b5c9712.
|
| |
|
| |
|
|
|
|
| |
This reverts commit 1a5205536f0c0d6021450b11722919211847df86.
|
| |
|
| |
|
|
|
|
| |
Hyphenated names are safe in GNU make.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Although 'RubyGems' are always available in upstream Ruby, it might not
be available optionally when Ruby is delivered via packaging systems.
E.g. Linux distributions.
|
|
|
|
|
|
|
|
|
|
| |
Although 'did_you_mean' is always available in upstream Ruby, it might
not be available when speed, memory, disk or network bandwidth is a
concern. This is typically the case for production environment, where
'did_you_mean' is of limited usage.
Also it might not be available optionally when Ruby is delivered via
packaging systems. E.g. Linux distributions.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The OpenSSL engine of Digest uses the low-level API of OpenSSL, whose
use has been discouraged for years for multiple reasons.
A long-standing issue on a FIPS-enabled system is that using ::Digest
results in crashing the Ruby process, because the low-level API lacks
the mechanism to report an error (the policy violation) and thus kills
the process as a last resort[1][2]. Also, the upcoming OpenSSL 3.0 will
deprecate it for future removal[3]. Compiling with
-Wdeprecated-declarations will start to emit warnings.
A proper fix for this is to make it use the EVP API instead. This is a
non-trivial work as it requires backwards-incompatible changes to the
framework interface of Digest::Base and rb_digest_metadata_t.
It is more than 15 years ago that the openssl library became part of the
standard library. It has implemented the exactly same functionality as
OpenSSL::Digest, in fact, as a subclass of Digest::Class. There is not
much point in having an identical code in the digest library. Let's
just get rid of OpenSSL within digest. This leaves the C implementations
and the CommonCrypto engine for Apple systems.
A patch is being prepared for the openssl library to provide ::Digest
constants for better performance[4].
[1] https://bugs.ruby-lang.org/issues/6946
[2] https://bugs.ruby-lang.org/issues/13681
[3] https://www.openssl.org/docs/OpenSSL300Design.html
[4] https://github.com/ruby/openssl/pull/377
|
|
|
|
| |
Wrapping the example into a <code> block to avoid it being rendered as a link.
|
| |
|