| Age | Commit message (Collapse) | Author |
|
exec` context
https://github.com/rubygems/rubygems/commit/ad95a1dfaa
|
|
https://github.com/rubygems/rubygems/commit/0511d2c08d
|
|
https://github.com/rubygems/rubygems/commit/f530f8686d
|
|
|
|
https://github.com/ruby/ipaddr/commit/4685fca13d
|
|
methods, and prepare error highlighting to render on extremely small screens
https://github.com/ruby/error_highlight/commit/c565340958
|
|
the line
https://github.com/ruby/error_highlight/commit/0657bc1afa
|
|
https://github.com/ruby/error_highlight/commit/383490a4b4
|
|
https://github.com/rubygems/rubygems/commit/264c61eb8e
|
|
(https://github.com/ruby/reline/pull/765)
* use IO's encoding
* refactoring
* remove unused encoding params
* (for retriggering CI) remove unused encoding params
https://github.com/ruby/reline/commit/f09772adab
|
|
At the moment, this code is looking at the stat output to determine if a
temp directory can be written to. However, just because the stat bits
say that a directory is writable, does not make it so; and, likewise,
the operating system may in fact grant access to paths that the stat
bits and process UID say should be inaccessible.
These systems include:
* Posix ACL's
* Linux's capabilities like CAP_DAC_OVERRIDE
* Linux Security Modules like SELinux or AppArmor
* Syscall filters like Linux's seccomp
* Granular capability systems like FreeBSD's Capsicum
* OpenBSD's pledge and unveil
* Windows too has a rich ACL system for controlling filesystem access
The best thing to do is simply to try and access the path with
`File.writable?` and let the operating system tell us if the path can be
accessed.
Notes:
Merged: https://github.com/ruby/ruby/pull/11403
|
|
https://github.com/ruby/ipaddr/commit/b44d2a1173
|
|
https://github.com/ruby/ipaddr/commit/1f41cd7320
|
|
warning
(https://github.com/ruby/irb/pull/1019)
* Suppress "literal string will be frozen in the future" warning
Before change:
```console
$ ruby -W -I lib -e 'require "irb"; IRB.setup(nil); IRB::Irb.new.build_statement("1 + 2")'
/Users/zzz/src/github.com/ruby/irb/lib/irb.rb:1135: warning: literal string will be frozen in the future
```
After change:
```console
$ ruby -W -I lib -e 'require "irb"; IRB.setup(nil); IRB::Irb.new.build_statement("1 + 2")'
```
* Making build_statement not modify the given argument
Because improves readability and code quality.
Co-authored-by: tomoya ishida <tomoyapenguin@gmail.com>
---------
https://github.com/ruby/irb/commit/3da04b9786
Co-authored-by: tomoya ishida <tomoyapenguin@gmail.com>
|
|
(https://github.com/ruby/irb/pull/988)
https://github.com/ruby/irb/commit/db0a923d62
|
|
This option is similar to the `bundle install --quiet` option
https://github.com/rubygems/rubygems/commit/3bd773d827
|
|
https://github.com/ruby/ipaddr/commit/73f59e111f
|
|
Updated to use cidr method when return address with prefix in #as_json
https://github.com/ruby/ipaddr/commit/cf8181d53e
|
|
Bundler always exits with a status code.
https://github.com/rubygems/rubygems/commit/3a38bd0b12
|
|
https://github.com/ruby/syntax_suggest/commit/0b9e4081c0
|
|
https://github.com/ruby/syntax_suggest/commit/e1d9c83736
|
|
`--embed-mixins`
(https://github.com/ruby/rdoc/pull/842)
* Embed mixed-in methods and constants with `--embed-mixins`
When `--embed-mixins` option is set:
- methods from an `extend`ed module are documented as singleton methods
- attrs from an `extend`ed module are documented as class attributes
- methods from an `include`ed module are documented as instance methods
- attrs from an `include`ed module are documented as instance attributes
- constants from an `include`ed module are documented
Sections are created when needed, and Darkfish's template annotates
each of these mixed-in CodeObjects. We also respect the mixin methods'
visibility.
This feature is inspired by Yard's option of the same name.
* Add comment to document why we set object visibility
Co-authored-by: Stan Lo <stan001212@gmail.com>
* Add the mixin_from attribute to CodeObject's initializer
* Add test coverage for private mixed-in attributes.
---------
https://github.com/ruby/rdoc/commit/481c2ce660
Co-authored-by: Stan Lo <stan001212@gmail.com>
|
|
If we assume that most of the time the `opts` hash is small
it's faster to go over the provided keys with a `case` than
to test all possible keys one by one.
Before:
```
== Encoding small nested array (121 bytes)
ruby 3.4.0preview2 (2024-10-07 master 32c733f57b) +YJIT +PRISM [arm64-darwin23]
Warming up --------------------------------------
json 156.832k i/100ms
oj 209.769k i/100ms
rapidjson 162.922k i/100ms
Calculating -------------------------------------
json 1.599M (± 2.5%) i/s (625.34 ns/i) - 7.998M in 5.005110s
oj 2.137M (± 1.5%) i/s (467.99 ns/i) - 10.698M in 5.007806s
rapidjson 1.677M (± 3.5%) i/s (596.31 ns/i) - 8.472M in 5.059515s
Comparison:
json: 1599141.2 i/s
oj: 2136785.3 i/s - 1.34x faster
rapidjson: 1676977.2 i/s - same-ish: difference falls within error
== Encoding small hash (65 bytes)
ruby 3.4.0preview2 (2024-10-07 master 32c733f57b) +YJIT +PRISM [arm64-darwin23]
Warming up --------------------------------------
json 216.464k i/100ms
oj 661.328k i/100ms
rapidjson 324.434k i/100ms
Calculating -------------------------------------
json 2.301M (± 1.7%) i/s (434.57 ns/i) - 11.689M in 5.081278s
oj 7.244M (± 1.2%) i/s (138.05 ns/i) - 36.373M in 5.021985s
rapidjson 3.323M (± 2.9%) i/s (300.96 ns/i) - 16.871M in 5.081696s
Comparison:
json: 2301142.2 i/s
oj: 7243770.3 i/s - 3.15x faster
rapidjson: 3322673.0 i/s - 1.44x faster
```
After:
```
== Encoding small nested array (121 bytes)
ruby 3.4.0preview2 (2024-10-07 master 32c733f57b) +YJIT +PRISM [arm64-darwin23]
Warming up --------------------------------------
json 168.087k i/100ms
oj 208.872k i/100ms
rapidjson 149.909k i/100ms
Calculating -------------------------------------
json 1.761M (± 1.1%) i/s (567.90 ns/i) - 8.909M in 5.059794s
oj 2.144M (± 0.9%) i/s (466.37 ns/i) - 10.861M in 5.065903s
rapidjson 1.692M (± 1.7%) i/s (591.04 ns/i) - 8.545M in 5.051808s
Comparison:
json: 1760868.2 i/s
oj: 2144205.9 i/s - 1.22x faster
rapidjson: 1691941.1 i/s - 1.04x slower
== Encoding small hash (65 bytes)
ruby 3.4.0preview2 (2024-10-07 master 32c733f57b) +YJIT +PRISM [arm64-darwin23]
Warming up --------------------------------------
json 242.957k i/100ms
oj 675.217k i/100ms
rapidjson 355.040k i/100ms
Calculating -------------------------------------
json 2.569M (± 1.5%) i/s (389.22 ns/i) - 12.877M in 5.013095s
oj 7.128M (± 2.3%) i/s (140.30 ns/i) - 35.787M in 5.023594s
rapidjson 3.656M (± 3.1%) i/s (273.50 ns/i) - 18.462M in 5.054558s
Comparison:
json: 2569217.5 i/s
oj: 7127705.6 i/s - 2.77x faster
rapidjson: 3656285.0 i/s - 1.42x faster
```
|
|
This helps very marginally with allocation speed.
https://github.com/ruby/json/commit/25db79dfaa
|
|
(https://github.com/ruby/rdoc/pull/1190)
This will make the anchor target easier to read.
https://github.com/ruby/rdoc/commit/e2fe4882f4
|
|
(https://github.com/ruby/rdoc/pull/1174)
https://github.com/ruby/rdoc/commit/7398e5b0ad
Co-authored-by: Stan Lo <stan001212@gmail.com>
|
|
compatible requirements
https://github.com/rubygems/rubygems/commit/a8d14c1fc2
|
|
wrong source
https://github.com/rubygems/rubygems/commit/1e5780db0a
Co-authored-by: Taylor Thurlow <thurlow@hey.com>
|
|
https://github.com/rubygems/rubygems/commit/d5dce93167
|
|
https://github.com/rubygems/rubygems/commit/432fe083a6
|
|
https://github.com/rubygems/rubygems/commit/55eb6630a8
|
|
https://github.com/rubygems/rubygems/commit/fe9999f2cf
|
|
https://github.com/ruby/prism/commit/5ea6042408
|
|
https://github.com/ruby/yaml/commit/5b39653c52
|
|
https://github.com/ruby/yaml/commit/09691d005f
|
|
https://github.com/ruby/yaml/commit/f7c44d3fd7
|
|
https://github.com/ruby/yaml/commit/f47d6123eb
|
|
https://github.com/ruby/yaml/commit/c3d0f64224
|
|
https://github.com/ruby/yaml/commit/952fd361b1
|
|
(https://github.com/ruby/rdoc/pull/1091)
https://github.com/ruby/rdoc/commit/716bc16a7d
|
|
We fixed some issues recently where Bundler would try to activate a
pysch spec with missing extensions and crash. However, as a side effect,
we started printing warnings about missing extensions in situations
where we did not warn before.
It may be interesting to warn on these new situations too, but in order
to minimize changes for now, I'm reverting to printing warnings in the
same situations as before.
https://github.com/rubygems/rubygems/commit/51ebff6982
|
|
A default gem does not always live in the same place. For example,
Bundler may be installed to `site_dir` when RubyGems have been upgraded.
A more reliable way seems to actually activate the default gem, so that
we can know for sure where it lives.
https://github.com/rubygems/rubygems/commit/c69f6dfb18
|
|
activated
https://github.com/rubygems/rubygems/commit/b44bf2ac74
|
|
(https://github.com/ruby/irb/pull/1018)
IRB need to accept bignum history size, but we don't want explicit bignum checks because threshold of bignum and fixnum depends on platform.
https://github.com/ruby/irb/commit/5151467e6a
|
|
(https://github.com/ruby/reline/pull/761)
Continuous tab completion is possible in GNU Readline.
If dig_perfect_match_proc is set, continuous tab completion will be disabled.
https://github.com/ruby/reline/commit/469a52846b
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/11884
Merged-By: nobu <nobu@ruby-lang.org>
|
|
Introduce StringQuery to provide methods to access some metadata
about the Ruby lexer.
https://github.com/ruby/prism/commit/d3f55b67b9
|
|
(https://github.com/ruby/irb/pull/1012)
As introduced in 824473e8
https://github.com/ruby/irb/commit/15e3f50c3f
|
|
* Extract logic save_history in separate helper
* Extract logic history_file in helper
* Allow for readonly history
https://github.com/ruby/irb/commit/52307f9026
|
|
https://github.com/ruby/time/commit/933eccf8d9
|