| Age | Commit message (Collapse) | Author |
|
https://github.com/rubygems/rubygems/commit/440343b791
|
|
https://github.com/ruby/uri/commit/a0dd612e90
|
|
https://github.com/ruby/uri/commit/f0847c266c
|
|
I don't want to make bundled_gems.rb more complex and complicate.
Revert "Fixed warning condition with LoadError"
This reverts commit 3a9e48b9a4860022f43d8101c0f3249299437886.
Revert "Only warn fiddle as optional dependency"
This reverts commit ff3f61556fb62d12d57d017f4c54f1a8fd5208be.
Revert "Only `warn` about bundled gems when require succeeds"
This reverts commit a70adce1ce5fae8eaae385214ac0d2e7d17c1103.
Notes:
Merged: https://github.com/ruby/ruby/pull/12072
|
|
default gem
* This is notably necessary on TruffleRuby, which is updating to Ruby 3.3 which introduces Prism as a default gem.
* Using the existing path is not an option as it would end up in truffleruby/lib/build/libprism.so and
"truffleruby/lib/include/#{header}" which are not good places for such files.
https://github.com/ruby/prism/commit/5d16473e69
|
|
https://github.com/rubygems/rubygems/commit/5a094cbfab
|
|
|
|
`paths-ignore` cannot be used for required status checks.
|
|
https://github.com/ruby/pp/commit/b192896a1d
|
|
|
|
https://github.com/ruby/pp/commit/af2229e8e6
|
|
Right now attempting to pretty print a BasicObject or any other
object lacking a few core Object methods will result in an error
```
Error: test_basic_object(PPTestModule::PPInspectTest): NoMethodError: undefined method `is_a?' for an instance of BasicObject
lib/pp.rb:192:in `pp'
lib/pp.rb:97:in `block in pp'
lib/pp.rb:158:in `guard_inspect_key'
lib/pp.rb:97:in `pp'
test/test_pp.rb:131:in `test_basic_object'
128:
129: def test_basic_object
130: a = BasicObject.new
=> 131: assert_match(/\A#<BasicObject:0x[\da-f]+>\n\z/, PP.pp(a, ''.dup))
132: end
133: end
134:
```
With some fairly small changes we can fallback to `Object#inspect`
which is better than an error.
https://github.com/ruby/pp/commit/4e9f6c2de0
|
|
[Bug #20808]
The previous implementation assumed all members are accessible,
but it's possible for users to change the visibility of members or
to entirely remove the accessor.
https://github.com/ruby/pp/commit/fb19501434
|
|
checksums in fresh lockfiles
https://github.com/rubygems/rubygems/commit/50b9ef8589
|
|
(https://github.com/ruby/reline/pull/778)
Flatten recursive method
Remove CompletionState::COMPLETE
https://github.com/ruby/reline/commit/aa5b278f3d
|
|
https://github.com/rubygems/rubygems/commit/506a863b36
|
|
https://github.com/ruby/securerandom/commit/9703d96a76
|
|
https://github.com/ruby/resolv/commit/c4837aae9b
|
|
https://github.com/ruby/uri/commit/9997c1acee
https://github.com/ruby/uri/commit/c191b627cb
|
|
|
|
(https://github.com/ruby/reline/pull/759)
* Remove garbage(nil) from Reline::Unicode.split_by_width result
* Remove unused width from Reline::Unicode vi_ ed_ em_ method return value
* Remove unused height from Unicode.split_by_width return value
* Rename split_by_width to split_line_by_width and add legacy split_by_width for IRB
https://github.com/ruby/reline/commit/f32446ebc4
|
|
https://github.com/rubygems/rubygems/commit/d070fa10c1
Co-authored-by: Artem Ignatyev <zazubrik@gmail.com>
|
|
https://github.com/rubygems/rubygems/commit/bc2537de71
|
|
https://github.com/rubygems/rubygems/commit/98641d21a2
|
|
https://github.com/rubygems/rubygems/commit/43c0c41c6b
|
|
It's defined in the superclass already.
https://github.com/rubygems/rubygems/commit/e269f5477b
|
|
set source
https://github.com/rubygems/rubygems/commit/3749273ec6
|
|
https://github.com/rubygems/rubygems/commit/ffd2fbaf6c
|
|
existing lockfile
https://github.com/rubygems/rubygems/commit/0a9c1ce60d
|
|
We did this because RubyGems `require` would call `gem` on self, so
defining a `gem` method in the CLI would cause conflicts. However, this
is not the case since
https://github.com/rubygems/rubygems/commit/439c4464890958fec17b3aa65b9d3a4dbdd3bf90,
so this should no longer be necessary.
https://github.com/rubygems/rubygems/commit/3e5c861046
|
|
https://github.com/ruby/uri/commit/3011eb6f6e
|
|
Fixed https://github.com/ruby/uri/issues/125
https://github.com/ruby/uri/commit/1f3d3df02a
|
|
https://github.com/ruby/time/commit/539b151049
|
|
https://github.com/ruby/optparse/commit/080360ffd4
|
|
https://github.com/ruby/pstore/commit/a63a70a830
|
|
https://github.com/ruby/singleton/commit/256c91171b
|
|
(https://github.com/ruby/reline/pull/777)
https://github.com/ruby/reline/commit/4d90743409
|
|
* test_yamatanooroti: close tempfile before unlink
* test_yamatanooroti: omit because of windows does not support job control
* test_yamatanooroti: change startup message detection for windows
* windows.rb: can call win32api using nil as NULL for pointer argument
Exception occurred when interrupted with Ctrl+C on legacy conhost
* windows.rb: fix get_screen_size
return [window height, buffer width] insted of [buffer height, buffer width]
* windows.rb: import scroll_down() from ansi.rb
* windows.rb: add auto linewrap control if VT output not supported (legacy console)
* unfreeze WIN32API pointer arguments
They internally duplicate arguments so api functions write to another place.
This breaks the console mode detection with ruby-head.
* remove useless code from Win32API#call
argument repacking and return value tweaking is not needed for Reline::Windows requirements.
* Correctly handle top of console viewport
* Revert "remove useless code from Win32API#call"
This reverts commit https://github.com/ruby/reline/commit/060ba140ed43.
* Revert "windows.rb: can call win32api using nil as NULL for pointer argument"
This reverts commit https://github.com/ruby/reline/commit/93a23bc5d0c9.
https://github.com/ruby/reline/commit/47c1ffbabe
|
|
https://github.com/ruby/benchmark/commit/a5d77ceae0
|
|
highest length among the labels to adjust the correct ljust. Instead of printing the result during the report generation, now it is waiting to print the result once it is generated.
Benchmark.bm { |x|
x.item("aaaa") { 1 }
x.item("aaaaaaaa") { 0 }
}
After
user system total real
aaaa 0.000005 0.000002 0.000007 ( 0.000003)
aaaaaaaa 0.000001 0.000001 0.000002 ( 0.000002)
Before
user system total real
aaaa 0.000005 0.000001 0.000006 ( 0.000003)
aaaaaaaa 0.000002 0.000001 0.000003 ( 0.000003)
https://github.com/ruby/benchmark/commit/3e74533ead
|
|
https://github.com/ruby/ostruct/commit/b38680089f
|
|
https://github.com/ruby/ostruct/commit/85a773bb41
|
|
(https://github.com/ruby/irb/pull/1029)
https://github.com/ruby/irb/commit/b21432daf7
|
|
After having a second look at this deprecation, the explanation that
we're giving does not make a lot of sense. When working only with local
gems, Bundler will indeed generate a different lockfile depending on
the latest installed version of each gem is at `bundle install` time.
That's the same situation that happens with remote sources: Bundler will
generate a different lockfile depending on the latest version of each
gem available remotely.
So, I don't think "a consistent lockfile not getting generated" is a
good motivation for deprecating this.
Also, this deprecation brings additional challenges, since for example,
it should arguably not get printed when using `bundle install --local`?
The original problem when this deprecation was introduced was an
incorrect message about a missing gem having been yanked.
So, I think a better solution is to, as long as we give proper error
messages when things go wrong, let users do what's best for them and
undo the deprecation.
https://github.com/rubygems/rubygems/commit/17499cb83f
|
|
https://github.com/ruby/uri/commit/af8d9d6bb1
|
|
https://github.com/ruby/net-http/commit/28a4bf9295
|
|
https://github.com/ruby/delegate/commit/713059a5e9
|
|
https://github.com/ruby/delegate/commit/6daeb4248f
|
|
(https://github.com/ruby/logger/pull/103)
`Logger#with_level` was recently added to enable configuring a
`Logger`'s level for the duration of a block. However, the configured
level is always tied to the currently running `Fiber`, which is not
always ideal in applications that mix `Thread`s and `Fiber`s.
For example, Active Support has provided a similar feature
(`ActiveSupport::Logger#log_at`) which, depending on configuration, can
be isolated to either `Thread`s or `Fiber`s.
This commit enables subclasses of `Logger` to customize the level
isolation. Ideally, it will enable replacing most of Active Support's
`#log_at`, since both methods end up serving the same purpose.
https://github.com/ruby/logger/commit/dae2b832cd
|
|
dependencies
https://github.com/rubygems/rubygems/commit/5e933968a2
|