| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
https://github.com/ruby/net-protocol/commit/06d1420936
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This optimization is unsafe because `dest` is allowed to be a custom
object responding to `<<` (e.g. a block wrapped in `ReadAdapter`).
So the receiver can hold onto the passed buffer for as long as it wants.
If it was guaranteed that `ReadAdapter` was the only possible receiver
we could dup the buffer there for mutation safety, but I'm not certain
it's the case so I'd rather err on the safe side.
Ref: https://github.com/shrinerb/shrine/issues/610
https://github.com/ruby/net-protocol/commit/7efa16d55d
|
|
|
|
|
|
| |
Gem::Resolver::InstallerSet
https://github.com/rubygems/rubygems/commit/05cb5410cb
|
|
|
|
|
|
| |
using Kernel#sprintf over String#%
(https://github.com/ruby/logger/pull/75)
* Prefer Kernel#sprintf over String#% for formatting Strings
|
|
|
|
|
|
| |
(https://github.com/ruby/logger/pull/81)
https://github.com/ruby/logger/commit/b41d7c699c
|
|
|
|
|
|
| |
(https://github.com/ruby/logger/pull/82)
https://github.com/ruby/logger/commit/8915627234
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(https://github.com/ruby/irb/pull/472)
* Lazily load the multi-irb extension
We now have plan to implement a command that prints all commands'
information, which will need to load all command files without actually
running them.
But because the `multi-irb` extension patches IRB's top-level methods,
loading it would cause unintentional side-effects.
So this commit moves related requires into command execution to avoid the problem.
* Make extend_irb_context private
Co-authored-by: Takashi Kokubun <takashikkbn@gmail.com>
|
|
|
|
| |
https://github.com/rubygems/rubygems/commit/7b84fc1f19
|
| |
|
|
|
|
|
|
|
| |
The lack of a newline between the call-seq and the documentation was
causing the documentation to be parsed as a call-seq.
https://github.com/ruby/net-http/commit/1a212e2065
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
`IRB_USE_AUTOCOMPLETE=false`
(https://github.com/ruby/irb/pull/469)
* Allow using IRB_USE_AUTOCOMPLETE=false to disable autocompletion
Currently, the only 2 ways to disable autocompletion are:
1. Create `.irbrc` and set `IRB.conf[:USE_AUTOCOMPLETE] = false`
2. Add the `--noautocomplete` flag when using the `irb` executable
Both of them are less convenient than setting a env var and are
lesser known to devs.
And given the number of problems the autocompletion has (see #445), I
think we should allow disabling it with a simple `IRB_USE_AUTOCOMPLETE=false`.
* Mention some env var configs in the README
|
|
|
|
|
|
|
|
|
| |
(https://github.com/ruby/did_you_mean/pull/180)
* Do not suggest #name= for #name and vice versa
* Avoid allocating unnecessary MatchData
Co-authored-by: Jean byroot Boussier <jean.boussier+github@shopify.com>
Co-authored-by: Jean byroot Boussier <jean.boussier+github@shopify.com>
|
|
|
|
| |
https://github.com/ruby/did_you_mean/commit/f5b15128e2
|
|
|
|
| |
https://github.com/ruby/uri/commit/72f22716f8
|
|
|
|
| |
https://github.com/ruby/un/commit/8f1c78e27c
|
|
|
|
| |
https://github.com/ruby/tsort/commit/dd71002c65
|
|
|
|
| |
https://github.com/ruby/tmpdir/commit/ee99c758fd
|
|
|
|
| |
https://github.com/ruby/timeout/commit/4941e8c871
|
| |
|
|
|
|
| |
https://github.com/ruby/securerandom/commit/5bfe7d6c16
|
|
|
|
| |
https://github.com/ruby/resolv/commit/261f049058
|
|
|
|
| |
https://github.com/ruby/pstore/commit/2d95c19c43
|
|
|
|
| |
https://github.com/ruby/pp/commit/8870aa02df
|
|
|
|
| |
https://github.com/ruby/optparse/commit/c80dfb1ebd
|
|
|
|
| |
https://github.com/ruby/open-uri/commit/783892ebb0
|
|
|
|
| |
https://github.com/ruby/net-protocol/commit/3097bb4cc3
|
|
|
|
| |
https://github.com/ruby/net-http/commit/09a9ea163a
|
|
|
|
| |
https://github.com/ruby/mutex_m/commit/57f23978cd
|
|
|
|
| |
https://github.com/ruby/logger/commit/9c4ae3b81d
|
|
|
|
| |
https://github.com/ruby/ipaddr/commit/d92acb3982
|
|
|
|
| |
https://github.com/ruby/getoptlong/commit/71fbf2123f
|
|
|
|
| |
https://github.com/ruby/forwardable/commit/301687dbfa
|
|
|
|
| |
https://github.com/ruby/fileutils/commit/213e6a3d1f
|
|
|
|
| |
https://github.com/ruby/drb/commit/7c2d56e9f3
|
|
|
|
| |
https://github.com/ruby/delegate/commit/420637be45
|
|
|
|
| |
https://github.com/ruby/benchmark/commit/303ac8f28b
|
|
|
|
| |
https://github.com/ruby/rdoc/commit/c5e7ee03ac
|
|
|
|
| |
https://github.com/ruby/racc/commit/1768ed252f
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
These APIs/configs are not approved by the Ruby core, so they can't be
released to the public. This means having them in the codebase will
block other fixes/features from being released as well.
So this commit removes those exposed interfaces to unblock the release.
Hopefully when https://bugs.ruby-lang.org/issues/18996 is approved we
can re-implement better APIs.
https://github.com/ruby/reline/commit/f7a961c550
|
|
|
|
|
|
| |
(https://github.com/ruby/net-http/pull/84)
https://github.com/ruby/net-http/commit/660046386f
|
|
|
|
|
|
| |
Add test for not leaving empty files if ENOSPC is raised during 'gem install'
https://github.com/rubygems/rubygems/commit/8e0e20f079
|
|
|
|
|
|
|
|
|
|
| |
- Obviously, `tim` is a typo for `time`
- This didn't cause an exception because IO#raw is implemented in C and it doesn't check the keyword of the parameters
- Though this typo doesn't produce any problems for now, I think it should be fixed just in case for the future
- I've used this fixed version of Reline with IRB for several days and didn't find any new problems due to the fix
- But I myself am not sure how to make sure this fix is completely robust
https://github.com/ruby/reline/commit/e66a9696a1
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
... to prevent "circular require" when `--disable-gems` is used.
This is a simplified case of https://github.com/ruby/ruby/commit/e5a0abc5dedfd011986b16e8f8cf5cda476984c9
```
$ bundle exec ruby -we 'system("ruby", "-w", "--disable-gems", "-e", "")'
<internal:/home/mame/work/ruby/local/lib/ruby/3.2.0+3/rubygems/core_ext/kernel_require.rb>:85: warning: <internal:/home/mame/work/ruby/local/lib/ruby/3.2.0+3/rubygems/core_ext/kernel_require.rb>:85: warning: loading in progress, circular require considered harmful - /home/mame/work/ruby/local/lib/ruby/3.2.0+3/bundler/setup.rb
```
When bundler/setup is require'ed under --disable-gems mode, it loads
rubygems by `require "rubygems" unless defined?(Gem)` in
https://github.com/rubygems/rubygems/blob/0b1f682a6d65e57b86ba4853cba23cac361c769d/bundler/lib/bundler/rubygems_integration.rb#L3
In this case, require'ing bundler/setup from rubygems.rb is circular.
This change makes rubygems.rb to require "bundler/setup" only when
`Bundler` is not defined.
https://github.com/rubygems/rubygems/commit/b4608dee5e
|
|
|
|
|
|
| |
This SyntaxError#path feature only exists in Ruby HEAD. Until it is released in a preview I want to continue to support existing releases of 3.2.0 (and also so CI will continue to work, as it still uses a preview version to execute tests).
https://github.com/ruby/syntax_suggest/commit/9862032465
|
|
|
|
|
|
|
|
| |
https://bugs.ruby-lang.org/issues/19138
Co-authored-by: Nobuyoshi Nakada <nobu@ruby-lang.org>
https://github.com/ruby/syntax_suggest/commit/8e1e7b3298
|
|
|
|
|
|
| |
(https://github.com/ruby/net-http/pull/83)
https://github.com/ruby/net-http/commit/1ea5004098
|
|
|
|
| |
https://github.com/ruby/delegate/commit/2a91436284
|
|
|
|
| |
https://github.com/ruby/rdoc/commit/e1679fa7e4
|
|
|
|
| |
https://github.com/ruby/rdoc/commit/fe0159de2f
|