| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
| |
Monitor can be owned at the beginning of this method.
|
|
|
|
|
|
|
| |
This reverts commit d9978ce5d397866afae536db2aa708af3b7a4b2f.
Untaint was tentatively restored due to test failures. But now, the
failed tests have been removed, so we can revert the tentative fix.
|
|
|
|
| |
Partly reverted 7d463e360b9c4718b17378eb52783116a01b884b
|
|
|
|
|
|
| |
`File.symlink? safe_lp` can raise SecurityError and raising an
exception can leave RUBYGEMS_ACTIVATION_MONITOR locking. This
patch release it correctly.
|
| |
|
| |
|
|
|
|
| |
This reverts commit 8b27c23b5d55bd707a89bb5d95d2bdba9e132c1a.
|
|
|
|
| |
https://rubyci.org/logs/rubyci.s3.amazonaws.com/debian9/ruby-master/log/20191111T093005Z.fail.html.gz
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Fix gem pristine not accounting for user installed gems. Pull request
#2914 by Luis Sagastume.
* Refactor keyword argument test for Ruby 2.7. Pull request #2947 by
SHIBATA Hiroshi.
* Fix errors at frozen Gem::Version. Pull request #2949 by Nobuyoshi
Nakada.
* Remove taint usage on Ruby 2.7+. Pull request #2951 by Jeremy Evans.
* Check Manifest.txt is up to date. Pull request #2953 by David Rodríguez.
* Clarify symlink conditionals in tests. Pull request #2962 by David
Rodríguez.
* Update command line parsing to work under ps. Pull request #2966 by
David Rodríguez.
* Properly test `Gem::Specifications.stub_for`. Pull request #2970 by
David Rodríguez.
* Fix Gem::LOADED_SPECS_MUTEX handling for recursive locking. Pull request
#2985 by MSP-Greg.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I noticed that some files in rubygems were executable, and I could think
of no reason why they should be.
In general, I think ruby files should never have the executable bit set
unless they include a shebang, so I run the following command over the
whole repo:
```bash
find . -name '*.rb' -type f -executable -exec bash -c 'grep -L "^#!" $1 || chmod -x $1' _ {} \;
```
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/1de8f39ac4
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/bde88f00a1
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/05146bb2fd
|
|
|
|
|
|
|
|
| |
The arity of this method has been -1 since the import, so the
option has been passed always, even if Zlib::GzipReader#initialize
does not take the option. Actually it takes the option since 1.9.
https://github.com/rubygems/rubygems/commit/2fcde0f4e0
|
| |
|
|
|
|
|
|
| |
And test the fix we're adding.
https://github.com/rubygems/rubygems/commit/6f86637b98
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/cc255b774a
|
|
|
|
|
|
| |
Co-authored-by: Yusuke Endoh <mame@ruby-lang.org>
https://github.com/rubygems/rubygems/commit/92892bbc3a
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/506c5bce49
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/b3b5c2d379
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/8a7e27381c
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/1d18b12a26
|
|
|
|
|
|
| |
Previously it wouldn't play nice with the bundler version finder.
https://github.com/rubygems/rubygems/commit/d8bb81556d
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/ba021fb4be
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/8ac0647659
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/b1d825ab3a
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fixes #2290.
1. `Gem::Specification.date` returns SOURCE_DATE_EPOCH when defined,
2. this commit makes RubyGems set it _persistently_ when not provided.
This combination means that you can build a gem, check the build time,
and use that value to generate a new build -- and then verify they're
the same.
https://github.com/rubygems/rubygems/commit/d830d53f59
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/5b81f364ae
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Cfuncs that use rb_scan_args with the : entry suffer similar keyword
argument separation issues that Ruby methods suffer if the cfuncs
accept optional or variable arguments.
This makes the following changes to : handling.
* Treats as **kw, prompting keyword argument separation warnings
if called with a positional hash.
* Do not look for an option hash if empty keywords are provided.
For backwards compatibility, treat an empty keyword splat as a empty
mandatory positional hash argument, but emit a a warning, as this
behavior will be removed in Ruby 3. The argument number check
needs to be moved lower so it can correctly handle an empty
positional argument being added.
* If the last argument is nil and it is necessary to treat it as an option
hash in order to make sure all arguments are processed, continue to
treat the last argument as the option hash. Emit a warning in this case,
as this behavior will be removed in Ruby 3.
* If splitting the keyword hash into two hashes, issue a warning, as we
will not be splitting hashes in Ruby 3.
* If the keyword argument is required to fill a mandatory positional
argument, continue to do so, but emit a warning as this behavior will
be going away in Ruby 3.
* If keyword arguments are provided and the last argument is not a hash,
that indicates something wrong. This can happen if a cfunc is calling
rb_scan_args multiple times, and providing arguments that were not
passed to it from Ruby. Callers need to switch to the new
rb_scan_args_kw function, which allows passing of whether keywords
were provided.
This commit fixes all warnings caused by the changes above.
It switches some function calls to *_kw versions with appropriate
kw_splat flags. If delegating arguments, RB_PASS_CALLED_KEYWORDS
is used. If creating new arguments, RB_PASS_KEYWORDS is used if
the last argument is a hash to be treated as keywords.
In open_key_args in io.c, use rb_scan_args_kw.
In this case, the arguments provided come from another C
function, not Ruby. The last argument may or may not be a hash,
so we can't set keyword argument mode. However, if it is a
hash, we don't want to warn when treating it as keywords.
In Ruby files, make sure to appropriately use keyword splats
or literal keywords when calling Cfuncs that now issue keyword
argument separation warnings through rb_scan_args. Also, make
sure not to pass nil in place of an option hash.
Work around Kernel#warn warnings due to problems in the Rubygems
override of the method. There is an open pull request to fix
these issues in Rubygems, but part of the Rubygems tests for
their override fail on ruby-head due to rb_scan_args not
recognizing empty keyword splats, which this commit fixes.
Implementation wise, adding rb_scan_args_kw is kind of a pain,
because rb_scan_args takes a variable number of arguments.
In order to not duplicate all the code, the function internals need
to be split into two functions taking a va_list, and to avoid passing
in a ton of arguments, a single struct argument is used to handle
the variables previously local to the function.
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/d4fc383497
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/95c1f4e179
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/f5972338e0
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/d1bb122651
|
|
|
|
|
|
| |
is specified
https://github.com/rubygems/rubygems/commit/547947bbf0
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/ab186266b7
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/dc70c5a192
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/4ba4ffebbe
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/a16eacd650
|
|
|
|
|
|
|
| |
Instead, display an informative message saying that uninstallation of
specific versions is being skipped because of being default gems.
https://github.com/rubygems/rubygems/commit/b44845aa1d
|
|
|
|
|
|
| |
instance
https://github.com/rubygems/rubygems/commit/9a401646e1
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/fc224e9717
|
|
|
|
| |
Mostly requires adding ** in either calls or method definitions.
|
|
|
|
|
|
|
| |
`Kernel#pp` has wrapper, but `PP` does not.
https://github.com/ruby/ruby/runs/207405029#step:10:141
`NameError: uninitialized constant Bundler::Molinillo::Resolver::Resolution::PP`
|
|
|
|
|
|
| |
It is defined since ruby 1.9.2.
https://github.com/rubygems/rubygems/commit/84981ca908
|
|
|
|
| |
Installed path may contain symbolic links.
|
| |
|
|
|
|
|
|
| |
This reverts commit 260ef51a73c067599826c8ab110c53994c1b6226.
This broke the stable versions of Ruby like 2.4 and 2.5
|