| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Pick from https://github.com/rubygems/rubygems/commit/5ace20dbecfeaf09fba5f616193f3cfcff70ba00
|
|
|
|
|
|
|
|
|
|
|
| |
Given an existing application using native gems (e.g., nokogiri)
And a lockfile generated with a stable ruby version
When we test the application against ruby-head and `bundle install`
Then bundler should fall back to the generic ruby platform gem
Note that this test has been passing since 45931ac9
https://github.com/rubygems/rubygems/commit/0ecc6de378
|
|
|
|
|
|
| |
inline gemfile
https://github.com/rubygems/rubygems/commit/fa6e6ea95c
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Prior to this commit `bundle binstubs --standalone --all` would output a
warning about not being able to generate a standalone binstub for
bundler.
This warning predates the `--all` option, and I don't think it makes
sense in this context. The warning makes good sense when explicitly
trying to generate a bundler standalone binstub with `bundle binstubs
bundler --standalone`, since that command won't do what the user might
have expected. But `--all` is not specifically asking for bundler, and
having it report each time that the bundler binstubs could not be
generated does not seem particularly helpful. The only way to make that
warning go away would be to stop using `--standalone --all`.
This commit skips the warning when running with the `--all` option.
https://github.com/rubygems/rubygems/commit/e6a72e19eb
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
* Add spec for eval and line coverage.
* Add test for main file coverage.
|
| |
|
|
|
| |
Also `Numeric#remainder` should.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This commit moves the classpath (and tmp_classpath) from instance
variables to the rb_classext_t. This improves performance as we no
longer need to set an instance variable when assigning a classpath to
a class.
I benchmarked with the following script:
```ruby
name = :MyClass
puts(Benchmark.measure do
10_000_000.times do |i|
Object.const_set(name, Class.new)
Object.send(:remove_const, name)
end
end)
```
Before this patch:
```
5.440119 0.025264 5.465383 ( 5.467105)
```
After this patch:
```
4.889646 0.028325 4.917971 ( 4.942678)
```
|
| |
|
| |
|
|
|
|
| |
from https://github.com/rubygems/rubygems/commit/0635c1423db5d7c461d53bf0c3329bca75de7609
|
|
|
|
|
|
|
| |
Let it deal with legacy gems with equivalent version and different
dependencies.
https://github.com/rubygems/rubygems/commit/b430babe97
|
|
|
|
| |
* It seems a better exception class too than NoMemoryError.
|
|
|
|
|
| |
* The limit depends on the implementation and platform, it seems unavoidable.
* See https://bugs.ruby-lang.org/issues/18518#note-9
|
|
|
|
|
|
|
|
|
|
|
|
| |
Running the file with shebang has a few issues.
* shebang is an OS dependent feature. Many modern UNIX-like OSes
support it, but not all, e.g., Windows.
* `env` command may not be in `/usr/bin`.
* "ruby" command may not be "ruby", when `--program-suffix` or other
configuration option is used.
https://github.com/ruby/syntax_suggest/commit/2edf241055
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
without a value
https://github.com/rubygems/rubygems/commit/c242311158
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/3bf8e59304
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This was already the behavior when a single `'external:internal'`
encoding specifier string was passed. This makes the behavior
consistent for the case where separate external and internal
encoding specifiers are provided.
While here, fix the IO#set_encoding method documentation to
state that either the first or second argument can be a string
with an encoding name, and describe the behavior when the
external encoding is binary.
Fixes [Bug #18899]
|
|
|
|
| |
Handle the integert and the float parts separately in round_half_even
to prevent error occursions in floating point calculation.
|
|
|
|
| |
from https://github.com/rubygems/rubygems/commit/72fd3dd2096af16d797ad0cd8e0d2a8869e240b3
|
|
|
|
|
| |
These tests do not only consume hundreds GiB bytes memory, result in
`rb_bug` when `RUBY_DEBUG` is enabled.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
HOMEPATH is set to "\WINDOWS\system32" when running per "runas" session.
This directory is not writable by ordinary users, leading to errors with many ruby tools.
Also config files in the home directory are not recognized.
Still keeping HOME at first which is not used by native Windows,
but by ruby specs and by MSYS2 environment.
|
|
|
|
|
|
|
| |
Dir.home returns an UTF-8 string since ruby-3.0, but the actual
encoding of the bytes was CP_ACP or CP_OEMCP.
That led to invalid bytes when calling Dir.home with an unicode
username.
|
| |
|
|
|
|
| |
It's resolved by https://github.com/ruby/ruby/commit/5bb43aeb890657ea586e3fabbf763e5b5670ffd7
|
|
|
|
| |
https://github.com/ruby/syntax_suggest/commit/4d53d31bc5
|
|
|
|
| |
https://github.com/ruby/syntax_suggest/commit/0d5201b24d
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
argument
Previously, only certain values of the 3rd argument triggered a
deprecation warning.
First step for fix for bug #18797. Support for the 3rd argument
will be removed after the release of Ruby 3.2.
Fix minor fallout discovered by the tests.
Co-authored-by: Nobuyoshi Nakada <nobu@ruby-lang.org>
|
| |
|
|
|
|
| |
* See https://bugs.ruby-lang.org/issues/19078#note-30
|
|
|
|
| |
Pick from https://github.com/rubygems/rubygems/commit/ba3adad4d80038ffd7bea015da2f11d3e8a2ff82
|
|
|
|
|
|
|
|
| |
https://github.com/rubygems/rubygems/pull/6147 when --parseable and
--groups used
together
https://github.com/rubygems/rubygems/commit/3b0b95c509
|
|
|
|
|
|
|
|
| |
explicit value.
- this is preparation for onboarding Rust based extension gem generator
https://github.com/rubygems/rubygems/commit/d32801bdbc
|
|
|
|
|
|
| |
response. - adds Bundler#safe_load_marshal and Bundler::SAFE_MARSHAL_CLASSES listing safe classes to deserialize
https://github.com/rubygems/rubygems/commit/e947c608cc
|
|
|
|
|
|
| |
requirements
https://github.com/rubygems/rubygems/commit/8f287479bc
|
|
|
|
|
|
| |
Ensure `bundle lock` handles pre flag just like bundle update does.
https://github.com/rubygems/rubygems/commit/b9e85e3157
|
|
|
|
|
|
|
|
|
| |
With `GemVersionPromoter#sort_versions` being so simple, we no longer
need to reach into the class's internals to make private methods public
in order to effectively test. We can just allow both cases to go through
the main method.
https://github.com/rubygems/rubygems/commit/6cbe891003
|
|
|
|
|
|
|
| |
Passing this flag allows bumping to the current version, even if that
version is prerelease. This works in concert with the current flags.
https://github.com/rubygems/rubygems/commit/a6409e3509
|