| Age | Commit message (Collapse) | Author |
|
When extracting files from the tarball, a mode is retrieved from
the header. Occasionally you'll encounter a gem that was packaged
on a system whose permission bits result in a value that is larger
than the value that File.chmod will allow (anything >= 2^16). In
that case the extraction fails with a RangeError, which is pretty
esoteric.
If you extract the tarball with the tar and gunzip utilities, the
file permissions end up being just the bottom 16 bits masked off
from the original value. I've mirrored that behavior here. Per the
tar spec:
> Modes which are not supported by the operating system restoring
> files from the archive will be ignored.
I think that basically means what I've done here.
---
This commit also changes the behavior very slightly with regard to
when the chmod is called. Previously it was called while the file
descriptor was still open, but after the write call.
When write flushes, the file permissions are changed to the mode
value from the File.open call, undoing the changes made by
FileUtils.chmod. CRuby appears to flush the buffer after the
chmod call, whereas TruffleRuby flushes before the chmod call.
So the file permissions can change depending on implementation.
Both implementations end up getting the correct file permissions
for the bottom 9 bits (user, group, world), but differ with
regard to the sticky bit in the next 3.
To get consistent behavior, this commit changes it to close the
file descriptor before attempting to chmod anything, which makes
it consistent because the write flushes in both cases.
https://github.com/rubygems/rubygems/commit/22ce076e99
|
|
RubyGems.org already has refused connection requests using older than
TLS 1.2.
|
|
https://github.com/rubygems/rubygems/commit/c03e7e1564
|
|
https://github.com/rubygems/rubygems/commit/d7956e9ce5
|
|
https://github.com/github/codeql/discussions/10120#discussioncomment-3485880
|
|
Notes:
Merged-By: k0kubun <takashikkbn@gmail.com>
|
|
https://github.com/ruby/irb/commit/fd047512b3
|
|
https://github.com/ruby/irb/commit/a15f68ffdb
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/6376
|
|
* Add rb_callable_method_entry_or_negative
* YJIT: Implement specialized respond_to?
This implements a specialized respond_to? in YJIT.
* Update yjit/src/codegen.rs
Co-authored-by: Maxime Chevalier-Boisvert <maximechevalierb@gmail.com>
Notes:
Merged-By: maximecb <maximecb@ruby-lang.org>
|
|
|
|
|
|
|
|
`yes-fake` depends on it when `arch=noarch` is given, but the rule to
generate it from fake.rb.in is ignored now.
|
|
* Initial support for VM_CALL_ARGS_SPLAT
This implements support for calls with splat (*) for some methods. In
benchmarks this made very little difference for most benchmarks, but a
large difference for binarytrees. Looking at side exits, many
benchmarks now don't exit for splat, but exit for some other
reason. Binarytrees however had a number of calls that used splat args
that are now much faster. In my non-scientific benchmarking this made
splat args performance on par with not using splat args at all.
* Fix wording and whitespace
Co-authored-by: Maxime Chevalier-Boisvert <maximechevalierb@gmail.com>
* Get rid of side_effect reassignment
Co-authored-by: Maxime Chevalier-Boisvert <maximechevalierb@gmail.com>
Notes:
Merged-By: maximecb <maximecb@ruby-lang.org>
|
|
* YJIT: Add Opnd#sub_opnd to use only 8 bits
* Add with_num_bits and let arm64_split use it
* Add another assertion to with_num_bits
* Use only with_num_bits
Notes:
Merged-By: maximecb <maximecb@ruby-lang.org>
|
|
Co-authored-by: Nobuyoshi Nakada <nobu@ruby-lang.org>
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/6373
Merged-By: nobu <nobu@ruby-lang.org>
|
|
Add the `--with-gmp-dir` to specify the prefix directory of GMP.
The`--without-gmp` option is preserved for convenience. It can
be used to force to reject using GMP even if the `--with-gmp-dir`
option is specified.
Notes:
Merged-By: mrkn <mrkn@ruby-lang.org>
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/6371
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/6371
|
|
Currently, miniruby is rebuild **always** when yjit is enabled, even
if nothing is changed.
Notes:
Merged: https://github.com/ruby/ruby/pull/6371
|
|
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/6370
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/6370
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/6370
|
|
Use the same regexp to replace "(#NNNN)" and "GH-NNNN" style
references in vcs.rb, too.
|
|
https://github.com/ruby/irb/commit/6bbde84369
|
|
* Check rpath flag earlier
* Manage OPT_DIR at once
Notes:
Merged-By: mrkn <mrkn@ruby-lang.org>
|
|
file doesn't exist
If history file didn't exist when irb was started, @loaded_history_mtime
would be nil. However, if the history file didn't exist before, but it
exists when saving history, that means the history file was modified,
and we should handle it the same way as we handle the other case where
the history file was modified.
Fixes #388
https://github.com/ruby/irb/commit/8d277aafcb
|
|
|
|
* Remove CODEOWNERS to switch to auto-request-review
* Random change to test reviews
* Revert "Random change to test reviews"
This reverts commit 814b10d062d82d953019ea4afadc3f8fcf638379.
Notes:
Merged-By: k0kubun <takashikkbn@gmail.com>
|
|
|
|
https://github.com/ruby/ruby/actions/runs/3041702828/jobs/4899106526#step:14:1219
|
|
because it doesn't seem to be working. It's a bit annoying that
synchronized doesn't work, but in many cases, opened and
ready_for_review should be enough. As a last resort, you could
close/reopen it.
Also, the token scope needs to be public_repo instead of repo:status.
|
|
|
|
We need to use pull_request_target instead of pull_request to use secrets.
pull_request_target seems to be executed from the default branch, so
pushing this to master to test this.
|
|
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/6362
|
|
Instead of checking for uniqueness for every spec.
https://github.com/rubygems/rubygems/commit/97d28c9665
|
|
https://github.com/rubygems/rubygems/commit/9d7bd177b0
|
|
Already done by the gem version promoter.
https://github.com/rubygems/rubygems/commit/aae2cc9fe0
|
|
https://github.com/rubygems/rubygems/commit/c4e2737f2c
|
|
https://github.com/rubygems/rubygems/commit/3cea25a39d
|
|
https://github.com/rubygems/rubygems/commit/823cb1fef9
|
|
Specs in a SpecSet with the same name are only sorted by platform
priority when they are read. No need to sort everything eagerly.
https://github.com/rubygems/rubygems/commit/aeafff52df
|
|
|
|
UTF-16/UTF-32
* And simplify callers of get_actual_encoding().
* See [Feature #18949].
* See https://github.com/ruby/ruby/pull/6322#issuecomment-1242758474
|
|
It is no longer necessary to add it to `CFLAGS`/`CPPFLAGS` later.
Furthermore, as `CPPFLAGS` is used also with C++ compiler, the option
particular to C such as `-std=gnu99` results in an error.
Notes:
Merged: https://github.com/ruby/ruby/pull/6361
Merged-By: nobu <nobu@ruby-lang.org>
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/6357
Merged-By: nobu <nobu@ruby-lang.org>
|