| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Disallow:
* Only year-month
* Only year-month-day
* Preceding whitespace
* Trailing whitespace
Fixes [Bug #19293]
|
| |
|
|
|
|
| |
This commit applies https://github.com/ruby/rbs/pull/1374.
|
|
|
|
|
| |
We no longer need a reference to the array when allocating the buffer
because we no longer allocate through the transient heap.
|
| |
|
|
|
|
| |
RARRAY_CONST_PTR now does the same things as RARRAY_CONST_PTR_TRANSIENT.
|
|
|
|
| |
RARRAY_PTR_USE now does the same things as RARRAY_PTR_USE_TRANSIENT.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(https://github.com/ruby/irb/pull/640)
* Unpend rdoc dialog tests
Without these tests, we don't have any coverage on autocompletion's rdoc
dialog, which is what caused #638 to happen.
* Pull ri doc on CI for the doc dialog test
* Assert different screen result on CI and local machine
https://github.com/ruby/irb/commit/3ac96be660
|
| |
|
|
|
|
|
| |
Command line options should have higher precedence than the same
options in shebang and `RUBYOPT`.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
To make the example code verbatim.
Fixes ruby/ruby#8061
https://github.com/ruby/getoptlong/commit/85fe502916
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Closes [Feature #19729]
Previously 2 bits of the flags on each RVALUE are reserved to store the
number of GC cycles that each object has survived. This commit
introduces a new bit array on the heap page, called age_bits, to store
that information instead.
This patch still reserves one of the age bits in the flags (the old
FL_PROMOTED0 bit, now renamed FL_PROMOTED).
This is set to 0 for young objects and 1 for old objects, and is used as
a performance optimisation for the write barrier. Fetching the age_bits
from the heap page and doing the required math to calculate if the
object was old or not would slow down the write barrier. So we keep this
bit synced in the flags for fast access.
|
| |
|
|
|
|
|
| |
When we extract bigdecimal as bundled gems, this test will be failed
with `make test-all`.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
git sources
Previously, when sorting and comparing git Gemfile vs lockfile sources during
`bundler/setup` to figure out whether we need to re-resolve or not, we
would try to find the default branch if nothing more specific was
specified in the Gemfile.
If the git cache has been deleted thought, that would fail.
The error would still be swallowed (and the branch would simply not be
displayed), but trying to clone would still generate the side effect of
creating the parent folder for the clone.
That could affect non-writable systems that don't expect `bundler/setup`
to write to the filesystem at all.
To fix this, override `Bundler::Source::Git#identifier` to use
exclusively static information, so it does not even try to clone the
repo nor generate any side effects.
https://github.com/rubygems/rubygems/commit/582eb2ef39
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/46cd9be69a
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/57cfe7cf8d
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/c431a1df52
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/802457b0a1
|
| |
|
|
|
|
|
|
| |
(https://github.com/ruby/irb/pull/639)
https://github.com/ruby/irb/commit/621c8c2b7d
|
| |
|
|
|
|
|
|
|
|
| |
(https://github.com/ruby/irb/pull/638)
The caller should be the dialog itself, not Reline.
https://github.com/ruby/irb/commit/418c2b945e
|
| |
|
|
|
|
|
|
|
| |
Although MinGW provides this header but not the function, Windows
version ruby provides the function.
https://github.com/ruby/etc/commit/f7fa1884fa
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
OpenSSL::Cipher#pkcs5_keyivgen
(https://github.com/ruby/openssl/pull/647)
OpenSSL::Cipher#pkcs5_keyivgen should only be used when it is
absolutely necessary for compatibility with ancient applications.
Having an example can be misleading. We already have another example
for OpenSSL::Cipher in which PBKDF2 is used to derive a key.
As described in the rdoc of OpenSSL::Cipher#pkcs5_keyivgen, it is
compatible with PKCS#5 PBES1 (PKCS#5 v1.5) only when used in combination
of a hash function MD2, MD5, or SHA-1, and a cipher DES-CBC or RC2-CBC.
This example uses MD5 as the hash function and combines it with AES.
This is considered insecure and also using a non-standard technique to
derive longer keys.
https://github.com/ruby/openssl/commit/e379cc0cca
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(https://github.com/ruby/openssl/pull/646)
Add OpenSSL::PKey.new_raw_private_key, #raw_private_key and public
equivalents. These methods are useful for importing and exporting keys
that support "raw private/public key". Currently, OpenSSL implements
X25519/X448 and Ed25519/Ed448 keys.
[rhe: rewrote commit message]
https://github.com/ruby/openssl/commit/3f29525618
Co-authored-by: Bart de Water <bartdewater@gmail.com>
|
|
|
|
|
|
|
| |
Commit messages written on GitHub's Web UI apparently use \r\n as a
line separator and do not have a \n at the end of message, unlike those
normally made with the git CLI. This breaks the expectation of the
regexps used later.
|
|
|
|
| |
https://github.com/ruby/etc/commit/b95ddef386
|
|
|
|
|
|
|
| |
Fixes https://github.com/ruby/etc/pull/22.
Build failure when the ruby installed directory name contains spaces.
https://github.com/ruby/etc/commit/1ab19d5815
|
|
|
|
| |
https://github.com/ruby/etc/commit/365398ea47
|
|
|
|
| |
Add comment for 7299c8c0f165247853fac2fe337e7c2678e653c9.
|
|
|
|
|
|
|
|
|
|
|
|
| |
## What was the end-user or developer problem that led to this PR?
The old URL https://github.com/testdouble/standard is mentioned.
## What is your fix for the problem, implemented in this PR?
This PR updates to the new URL https://github.com/standardrb/standard.
https://github.com/rubygems/rubygems/commit/eeafba72fc
|
|
|
|
|
|
| |
This reverts commit 074bf01e13db1ac0407786a3bc1b85c13135fd36, "Test
`Comparable#clamp` with inverse arguments as well as a Range".
The test is already in another method.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
I don't use that these days. I'd like to remove this to ease a change
I'm writing. I'll resurrect this when I need this again.
|
|
|
|
|
| |
assert_not_nil could allocate objects which may trigger the major GC, so
don't run the assertions until the major GC has been ran.
|