| Age | Commit message (Collapse) | Author |
|
https://github.com/ruby/bigdecimal/commit/3ede8860a6
|
|
|
|
This new page would be linked from method strftime in Time, Date, and DateTime, replacing the text there.
Notes:
Merged-By: BurdetteLamar <BurdetteLamar@Yahoo.com>
|
|
|
|
|
|
Update RBS to v2.6.0 and specify RBS commit hash to fix test failure on test-bundled-gems
Notes:
Merged-By: pocke <p.ck.t22@gmail.com>
|
|
|
|
|
|
302f353fd9223d020e48495eaa7a03ce5d539409 seems break the rubyspec.
@nobu please check it.
|
|
|
|
https://github.com/ruby/stringio/commit/16847fea32
|
|
Refactor gen_opt_mod in YJIT
Notes:
Merged-By: maximecb <maximecb@ruby-lang.org>
|
|
handle case in YJIT stats where 0 exits causes NaN in the display
Notes:
Merged-By: maximecb <maximecb@ruby-lang.org>
|
|
https://github.com/rubygems/rubygems/commit/b1826876d0
|
|
http://rubyci.s3.amazonaws.com/ubuntu2004-arm/ruby-master/log/20220630T063003Z.log.html.gz
```
[19606/21662] TestAst#test_not_cared:test/rubygems/test_gem_ext_cargo_builder/custom_name/build.rb(none):18: warning: `*' interpreted as argument prefix
(none):19: warning: `*' interpreted as argument prefix
= 0.00 s
```
https://github.com/rubygems/rubygems/commit/c98f9326e8
|
|
Statically determined value should be set statically.
|
|
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/6065
|
|
|
|
If `XDG_RUNTIME_DIR` is available, test-bundled-gems fails with
old debug.gem tests.
Notes:
Merged: https://github.com/ruby/ruby/pull/6081
|
|
|
|
This allows us to delete the disassembly code path for reference
updating.
Notes:
Merged: https://github.com/ruby/ruby/pull/6062
|
|
This function shouldn't leak and is only needed during instruction
assembly
Notes:
Merged: https://github.com/ruby/ruby/pull/6069
|
|
We need to dump relative offsets for inline storage entries so that
loading iseqs as an array works as well. This commit also has some
minor refactoring to make computing relative ISE information easier.
This should fix the iseq dump / load as array tests we're seeing fail in
CI.
Co-Authored-By: John Hawthorn <john@hawthorn.email>
Notes:
Merged: https://github.com/ruby/ruby/pull/6069
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/6077
|
|
https://github.com/rubygems/rubygems/commit/3f83236c02
|
|
This fails if there are any unused rust-bindgen "allow" entries. For
that target we turn on Rust warnings (there are a lot) and grep for the
ones that correspond to unused allow entries.
I've added check-yjit-bindgen-unused as a dependency of
check-yjit-bindings, so unused allow entries will now fail CI.
This change also removes our single unused allow entry (VM_CALL.*) which
was known to be bad.
Notes:
Merged-By: maximecb <maximecb@ruby-lang.org>
|
|
|
|
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/6064
Merged-By: nobu <nobu@ruby-lang.org>
|
|
|
|
https://github.com/rubygems/rubygems/commit/3a9205df36
|
|
https://github.com/rubygems/rubygems/commit/c9adf3ef1c
|
|
https://github.com/rubygems/rubygems/commit/14d3f80df6
|
|
https://github.com/rubygems/rubygems/commit/5ab8aa2a45
|
|
https://github.com/rubygems/rubygems/commit/6d841ccbd4
|
|
I think `gem env home` and `gem env path` read very nice.
https://github.com/rubygems/rubygems/commit/b89da79456
|
|
(https://github.com/ruby/fileutils/pull/96)
* Changes to examples
https://github.com/ruby/fileutils/commit/346a71b2cb
|
|
|
|
Some context tests assigns USE_COLORIZE to false and never change it
back. This can potentially affect other tests' result as the default
should be nil (activated) instead.
https://github.com/ruby/irb/commit/986eb16ece
|
|
Under POSIX behavior of leading // is implementation defined. Musl does
preserve it in realpath, glibc does not. That means the test was failing
when executed on alpine linux. Original issue #508 was about // in the
path, not about leading ones. When executed in such environment, the
test will still test what it should when the explicit mangling of the
path is not done.
Fixes #5652
https://github.com/rubygems/rubygems/commit/0fa7373bf6
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/6067
|
|
loaded
ruby/debug uses `irb/color` selectively:
https://github.com/ruby/debug/blob/0ac22406bb8f65bc76f9f5576a00c729cac693af/lib/debug/color.rb#L4
And in that case, `IRB.conf` won't be defined. So Color.colorable? needs
to consider that.
This also fixes the Ruby trunk CI.
https://github.com/ruby/irb/commit/b2cd07e795
|
|
* Use colorable: argument as the only coloring control
* Centalize color controling logic at Color.colorable?
There are 2 requirements for coloring output:
1. It's supported on the platform
2. The user wants it: `IRB.conf[:USE_COLORIZE] == true`
Right now we check 1 and 2 separately whenever we colorize things.
But it's error-prone because while 1 is the default of `colorable`
parameter, 2 always need to manually checked. When 2 is overlooked, it
causes issues like https://github.com/ruby/irb/pull/362
And there's 0 case where we may want to colorize even when the user
disables it. So I think we should merge 2 into `Color.colorable?` so it
can be automatically picked up.
* Add tests for all inspect modes
* Simplify inspectors' coloring logic
* Replace use_colorize? with Color.colorable?
* Remove Context#use_colorize cause it's redundant
https://github.com/ruby/irb/commit/1c53023ac4
|
|
https://github.com/ruby/rdoc/commit/f727854bd5
|
|
|
|
https://github.com/ruby/rdoc/commit/854b370763
|
|
https://github.com/ruby/rdoc/commit/c051eb90d1
|
|
Initialization depending on VM is separated.
https://github.com/ruby/rdoc/commit/030d10fccd
|
|
|