| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
```
1)
TracePoint#inspect returns a String showing the event, method, path and line for a :call event FAILED
Expected "#<TracePoint:call 'call' /tmp/ruby/src/trunk/spec/ruby/core/objectspace/define_finalizer_spec.rb:33>" =~ /\A#<TracePoint:call [`']trace_point_spec_test_call' \/tmp\/ruby\/src\/trunk\/spec\/ruby\/core\/tracepoint\/inspect_spec.rb:43>\z/
to be truthy but was nil
```
This kind of failures comes because of finaizers.
So check the current file or not.
|
|
|
|
|
|
|
|
https://bugs.ruby-lang.org/issues/20478
|
|
I don't understand what was the idea of "!=" here.
https://github.com/rubygems/rubygems/commit/06d5f1dcf1
|
|
used in config
https://github.com/rubygems/rubygems/commit/a0af1baa2b
|
|
https://github.com/rubygems/rubygems/commit/e31df2d6ef
|
|
Pathname problem
Recent refactorings in test suite to not load `pathname` for launching
Bundler subprocesses make some specs fail due to the warnings Ruby prints
when autoloading `pathname` under a namespace. But enabling this spec
also reproduces the hard error it produces on truffleruby.
https://github.com/rubygems/rubygems/commit/e47cd78081
|
|
When launching bundler subprocesses for end to end testing, all of them
will load the `spec/support/rubygems_version_manager.rb` file passed as
a ruby's `-r` flag.
Unfortunately this file depends on `pathname`, so unless we drop that
dependency, we can't really test support for including the `pathname`
gem in the `Gemfile`.
This commit implements some refactorings to avoid loading `pathname`
inside `bundler` test subprocesses.
https://github.com/rubygems/rubygems/commit/c1f948788c
|
|
https://github.com/rubygems/rubygems/commit/f7c7bae940
|
|
Not that I need it, but reads better.
https://github.com/rubygems/rubygems/commit/db3eca7b92
|
|
https://github.com/rubygems/rubygems/commit/77bc6f1ecc
|
|
https://github.com/rubygems/rubygems/commit/10f2ce1afb
|
|
internally
https://github.com/rubygems/rubygems/commit/6b3f555211
|
|
https://github.com/rubygems/rubygems/commit/279740ed52
|
|
https://github.com/rubygems/rubygems/commit/57576e27a1
|
|
https://github.com/rubygems/rubygems/commit/2d9eeadb62
|
|
https://github.com/rubygems/rubygems/commit/1f6e028201
|
|
This reverts commit a8f5284045e3aba1b45691142e5c01bf1d24d519.
Sorry, I didn't mean to push this one since I reverted the reline
change.
|
|
|
|
This significantly reduces memory usage.
https://github.com/rubygems/rubygems/commit/8a76506c90
|
|
take more than a minute
I expect to make occasional CI hangs easier to investigate.
Implementation was adapted from tty-command.
https://github.com/rubygems/rubygems/commit/39c92955bf
|
|
Upstream PR was merged and released.
https://github.com/rubygems/rubygems/commit/d6afbfd664
|
|
https://github.com/rubygems/rubygems/commit/ffd3711d00
|
|
https://github.com/rubygems/rubygems/commit/f513ea49b5
|
|
Gemfile as "local app"
https://github.com/rubygems/rubygems/commit/6aa2ac337f
|
|
any other gem
For backwards compatibility, make sure default gems are still used as a
last resort when materializing, in case no remote, cached, or installed
specs are found.
https://github.com/rubygems/rubygems/commit/93788f689f
|
|
|
|
A prime number 73 is not good for counting.
|
|
|
|
They were initially made frozen to avoid false positives for cases such
as:
str = str.dup if str.frozen?
But this may cause bugs and is generally confusing for users.
[Feature #20205]
Co-authored-by: Jean Boussier <byroot@ruby-lang.org>
|
|
https://github.com/rubygems/rubygems/commit/4bf455a498
|
|
https://github.com/rubygems/rubygems/commit/71bcf354f5
|
|
|
|
Most of the commands run by these specs actually prompt for user input
but for some reason `Open3` outside of Windows ignores that and goes on
with no user input. Windows does not like this.
This commit refactors these specs so that:
* They don't prompt for user input when not necessary.
* They pass proper user input when necessary.
As long as no user input is needed, most specs pass, so it allows to
remove the `:readline` tag from most of them.
https://github.com/rubygems/rubygems/commit/3dfabcdae4
|
|
were not used
https://github.com/rubygems/rubygems/commit/5ce9a7ff17
|
|
cache
Even if all gems are properly installed and no resolve is needed, we
recently started always reading all packages in `vendor/cache` and
extracting specifications from them.
This commit fixes the problem by longer making considering cached specs
the default and only enable them when a resolve is actually needed.
https://github.com/rubygems/rubygems/commit/edeb2c42bf
|
|
This was an offramp for generated etags to allow existing caches
to be served until people could upgrade. It has been about 6 months
since the transitional version was released, so we can remove this
transitional code now.
https://github.com/rubygems/rubygems/commit/4ec8cfe611
|
|
https://github.com/rubygems/rubygems/commit/592a2fcd54
|
|
|
|
|
|
|
|
If `cache_all_platforms` setting is enabled, the secondary source was
no longer considering cached gems.
That means that if the remote secondary source has removed its gems,
then this was now resulting in an error while before the previously
cached gem from the source would still be used.
This commit restores previous behavior.
https://github.com/rubygems/rubygems/commit/2d2cd00255
|
|
If one upgrades the default copy of Bundler through `gem update
--system`, and then reinstalls Ruby without removing the previous copy.
Then the new installation will have a correct default bundler gemspec,
but a higher copy installed in site_dir.
This causes a crash when running Bundler and prints the bug report
template.
This could probably be fixed in Ruby install script, by removing any
previous Bundler default copies, but if the problem is already there, I
think it's best to print a proper user error.
https://github.com/rubygems/rubygems/commit/ada6de765d
|
|
[Bug #20421]
The bug was fixed in Ruby 3.3 via 9dcdffb8bf8a3654fd78bf1a58b30c8e13888a7a
|
|
This gets in the middle if we ever start allowing to build as if using a
different RubyGems version than the one being run.
This could be useful to make `gem rebuild` a little more usable, and
it's already done by Bundler specs which already make this method a noop
when they need this.
I'm not sure forcefully setting this, even if user explicitly specified
something else is helpful.
Since this could potentially prevent gems explicitly setting a constant
RubyGems version from building, I changed the error of incorrect
RubyGems version from a hard error to a warning, since it will start
happening in those cases if we stop overwriting the version.
https://github.com/rubygems/rubygems/commit/45676af80d
|
|
For that particular spec, the empty lines' presence is not relevant.
So let's remove them to make the spec easier to maintain.
|
