| Age | Commit message (Collapse) | Author |
|
https://github.com/rubygems/rubygems/commit/32a5e9057a
|
|
https://github.com/rubygems/rubygems/commit/9a1b891435
|
|
https://github.com/rubygems/rubygems/commit/bcffd92c48
|
|
For the remote object `ro`, method chain like `ro.foo.bar` the
result of `ro.foo` is stored in `@result`, but cleared just
before `setup_message` and it seems GCed on specific machine.
```
1) Error:
DRbTests::TestDRbCore#test_05_eq:
RangeError: "140" is recycled object
(druby://localhost:36141) /tmp/ruby/v3/src/trunk-repeat20-asserts/lib/drb/drb.rb:366:in `_id2ref'
(druby://localhost:36141) /tmp/ruby/v3/src/trunk-repeat20-asserts/lib/drb/drb.rb:366:in `to_obj'
(druby://localhost:36141) /tmp/ruby/v3/src/trunk-repeat20-asserts/lib/drb/drb.rb:1528:in `to_obj'
(druby://localhost:36141) /tmp/ruby/v3/src/trunk-repeat20-asserts/lib/drb/drb.rb:1847:in `to_obj'
(druby://localhost:36141) /tmp/ruby/v3/src/trunk-repeat20-asserts/lib/drb/drb.rb:620:in `recv_request'
(druby://localhost:36141) /tmp/ruby/v3/src/trunk-repeat20-asserts/lib/drb/drb.rb:931:in `recv_request'
(druby://localhost:36141) /tmp/ruby/v3/src/trunk-repeat20-asserts/lib/drb/drb.rb:1656:in `init_with_client'
(druby://localhost:36141) /tmp/ruby/v3/src/trunk-repeat20-asserts/lib/drb/drb.rb:1668:in `setup_message'
(druby://localhost:36141) /tmp/ruby/v3/src/trunk-repeat20-asserts/lib/drb/drb.rb:1632:in `perform'
(druby://localhost:36141) /tmp/ruby/v3/src/trunk-repeat20-asserts/lib/drb/drb.rb:1725:in `block (2 levels) in main_loop'
(druby://localhost:36141) /tmp/ruby/v3/src/trunk-repeat20-asserts/lib/drb/drb.rb:1721:in `loop'
(druby://localhost:36141) /tmp/ruby/v3/src/trunk-repeat20-asserts/lib/drb/drb.rb:1721:in `block in main_loop'
/tmp/ruby/v3/src/trunk-repeat20-asserts/test/drb/drbtest.rb:206:in `test_05_eq'
```
To prevent collecting, clear `@result` just after `setup_message`
and `setup_message` can get the last result object.
Notes:
Merged: https://github.com/ruby/ruby/pull/5439
|
|
https://github.com/rubygems/rubygems/commit/1791b5b9e5
|
|
library presence
https://github.com/rubygems/rubygems/commit/ecd495ce1b
|
|
With this patch, handwriting version comparisons become a little bit easier.
before:
SomeGem.version <=> Gem::Version.new('1.3')
after:
SomeGem.version <=> '1.3'
https://github.com/rubygems/rubygems/commit/7e0dbb79f2
|
|
https://github.com/ruby/optparse/commit/dab72c543d
|
|
Specify the main page and the page directory. Also in Rakefile,
extract and use the same options from the gemspec file.
https://github.com/ruby/optparse/commit/d182cd60b5
|
|
Implements [Feature #17524]
https://github.com/ruby/resolv/commit/993a1a374f
|
|
https://github.com/rubygems/rubygems/commit/c29cd23826
|
|
last line
https://github.com/ruby/reline/commit/05024b968e
|
|
Solaris requires that the pointer errret_int is alined to an integer,
however, with VWA, strings are no longer aligned to an integer, so use a
Fiddle::Pointer with a malloc'd region instead.
https://github.com/ruby/reline/commit/5fcd89ab0c
|
|
https://github.com/rubygems/rubygems/commit/b55a1393ca
|
|
Fix version error message
Add tests to fetch error messages
Fix default version since is not necessary
https://github.com/rubygems/rubygems/commit/070620ebe4
|
|
Before:
```
$ gem install sfdsfdsfsdide --force
ERROR: While executing gem ... (NoMethodError)
undefined method `spec' for nil:NilClass
@always_install << newest.spec
^^^^^
```
After:
```
$ gem install sfdsfdsfsdide --force
ERROR: Could not find a valid gem 'sfdsfdsfsdide' (>= 0) in any repository
```
https://github.com/rubygems/rubygems/commit/4e2bfd1101
|
|
contains only development script
https://github.com/rubygems/rubygems/commit/01017ee8ca
|
|
`response_body_permitted?` is a method of request.
|
|
On JRuby, sometimes we get the following error in CI when running a
realworld test that checks that `gem install rails` succeeds:
```
ERROR: While executing gem ... (NoMethodError)
undefined method `ignored=' for nil:NilClass
/home/runner/.rubies/jruby-9.3.2.0/lib/ruby/stdlib/rubygems/stub_specification.rb:193:in `to_spec'
org/jruby/RubyArray.java:2642:in `map'
/home/runner/.rubies/jruby-9.3.2.0/lib/ruby/stdlib/rubygems/specification.rb:758:in `_all'
/home/runner/.rubies/jruby-9.3.2.0/lib/ruby/stdlib/rubygems/specification.rb:956:in `each'
org/jruby/RubyEnumerable.java:1710:in `any?'
/home/runner/.rubies/jruby-9.3.2.0/lib/ruby/stdlib/rubygems/resolver/activation_request.rb:111:in `installed?'
/home/runner/.rubies/jruby-9.3.2.0/lib/ruby/stdlib/rubygems/request_set.rb:173:in `block in install'
```
I'm not sure how this error is happening, but I think there's no need to
copy the `@ignored` instance variable when materializing stub
specifications. This instance variable is used to not print a warning
about missing extensions more than once for each gem upon gem
activation, but as far as I can see, it's only used by methods that work
on specification stubs. Once specifications are materialized, I think
it can be safely ignored.
https://github.com/rubygems/rubygems/commit/301cecd5a7
|
|
When we have no backtrace locations, we can't have the highlight,
so just return the message.
https://github.com/ruby/error_highlight/commit/9f5c639494
|
|
(https://github.com/ruby/optparse/pull/28)
https://github.com/ruby/optparse/commit/e4f2682128
|
|
https://github.com/rubygems/rubygems/commit/48ea2778e9
|
|
Calculate the checksum of the content, not the given pathname at
the build time itself.
https://github.com/rubygems/rubygems/commit/b60ee97ee9
|
|
Has been deprecated since ebff9dc10e6e72239c23e50acc7d3cbfdc659e7a.
|
|
Incorrect arguments can cause SEGV.
https://github.com/ruby/reline/commit/a58748bcf9
|
|
https://github.com/ruby/reline/commit/9ab5850444
|
|
https://github.com/ruby/reline/commit/695212d5d2
|
|
https://github.com/ruby/reline/commit/af4d77ba09
|
|
https://github.com/ruby/reline/commit/abc1e4ee88
|
|
https://github.com/ruby/reline/commit/0451ed7a28
|
|
https://github.com/ruby/reline/commit/c559d0f7a9
|
|
The kill-line was called when C-u was entered, so it is now called unix-line-discard.
In readline(3):
> unix-line-discard (C-u)
> Kill backward from point to the beginning of the line.
> The killed text is saved on the kill-ring.
https://github.com/ruby/reline/commit/27570d195e
|
|
(https://github.com/ruby/irb/pull/323)
https://github.com/ruby/irb/commit/1c03bd3373
|
|
https://github.com/rubygems/rubygems/commit/a053b7e4d4
|
|
`rubygems-update` version
https://github.com/rubygems/rubygems/commit/b0badcd00a
|
|
This makes it easier to test the upgrade process locally and should be
more efficient in certain cases where the user has already upgraded in
the past.
https://github.com/rubygems/rubygems/commit/ed6cc88494
|
|
https://github.com/ruby/drb/commit/9a1ff286bc
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/5350
|
|
Since we're at it. This generates a bunch of warnings and seems like a
brittle way to test things, so let's get rid of it.
https://github.com/rubygems/rubygems/commit/f5d45520e0
Notes:
Merged: https://github.com/ruby/ruby/pull/5350
|
|
It reduces memory usage about 204kb (1.4%).
https://github.com/rubygems/rubygems/commit/b7d4b8c8a6
Notes:
Merged: https://github.com/ruby/ruby/pull/5350
|
|
Probably `RUBY_VERSION` seems overwritten somewhere in the tests.
Notes:
Merged: https://github.com/ruby/ruby/pull/5349
Merged-By: nobu <nobu@ruby-lang.org>
|
|
https://github.com/ruby/irb/commit/b1d9c34441
|
|
https://github.com/ruby/irb/commit/a4b95d6634
|
|
https://github.com/ruby/reline/commit/3f6ea92268
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/5342
|
|
https://github.com/ruby/irb/commit/b80ec5821e
|
|
https://github.com/ruby/irb/commit/f36ad549c4
|
|
https://github.com/ruby/reline/commit/9b209ee1ea
|
|
https://github.com/ruby/reline/commit/b545459fca
|
|
https://github.com/ruby/reline/commit/20fcd22564
|