| Age | Commit message (Collapse) | Author |
|
https://github.com/ruby/erb/commit/51c0922170
|
|
(https://github.com/ruby/erb/pull/85)
https://github.com/ruby/erb/commit/692597b9a2
|
|
- The remaining code was not ported over as I felt it wasn't useful
to output the Ruby related version in the context of
running `bundle doctor`.
|
|
https://github.com/rubygems/rubygems/commit/e4f70a3e4f
|
|
https://github.com/rubygems/rubygems/commit/40cf54d256
|
|
https://github.com/rubygems/rubygems/commit/38a0bdc123
|
|
https://github.com/rubygems/rubygems/commit/bf63859e1e
|
|
https://github.com/rubygems/rubygems/commit/0aae094c89
|
|
https://github.com/rubygems/rubygems/commit/e6aa8aabcd
|
|
- The command can either be run using:
1. `bundle doctor --ssl`
2. `bundle doctor ssl`
The later is most useful when you need to specify
custom ssl options (such as the verify mode or the
TLS version when running the diagnostic).
The implementation will follow in the next commits.
https://github.com/rubygems/rubygems/commit/993d12874c
|
|
- Copy/pasted from https://github.com/rubygems/ruby-ssl-check.
The next commits will break it down for easier reviewing.
https://github.com/rubygems/rubygems/commit/aa643a11b1
|
|
|
|
Otherwise it makes incorrect assumption about RubyGems layout.
https://github.com/ruby/syntax_suggest/commit/04585d820d
|
|
load with require_relative.
https://github.com/ruby/syntax_suggest/commit/b782897560
|
|
https://github.com/rubygems/rubygems/commit/bb66253f2c
|
|
https://github.com/rubygems/rubygems/commit/93619c97ff
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/7877
|
|
Normally, we use `require_relative` when requiring internal code.
However, Bundler may also load external code (for example, bundler
plugins), and when that external code loads Bundler itself, using
`require_relative` without setting up the `$LOAD_PATH` may lead into
double load errors.
For example, when testing a Gemfile using plugins using our source code
tree, I get the following:
```
➜ plugins-dup ~/Code/rubygems/rubygems/bundler/exe/bundle
Fetching gem metadata from https://rubygems.org/.
Resolving dependencies...
Using bundler 2.5.0.dev
Installing extended_bundler-errors 0.3.3
/Users/deivid/.asdf/installs/ruby/3.2.2/lib/ruby/site_ruby/3.2.0/bundler/version.rb:4: warning: already initialized constant Bundler::VERSION
/Users/deivid/Code/rubygems/rubygems/bundler/lib/bundler/version.rb:4: warning: previous definition of VERSION was here
/Users/deivid/.asdf/installs/ruby/3.2.2/lib/ruby/site_ruby/3.2.0/bundler/worker.rb:5: warning: already initialized constant Bundler::Worker::POISON
/Users/deivid/Code/rubygems/rubygems/bundler/lib/bundler/worker.rb:5: warning: previous definition of POISON was here
/Users/deivid/.asdf/installs/ruby/3.2.2/lib/ruby/site_ruby/3.2.0/bundler/vendor/fileutils/lib/fileutils.rb:183: warning: already initialized constant Bundler::FileUtils::VERSION
/Users/deivid/Code/rubygems/rubygems/bundler/lib/bundler/vendor/fileutils/lib/fileutils.rb:183: warning: previous definition of VERSION was here
/Users/deivid/.asdf/installs/ruby/3.2.2/lib/ruby/site_ruby/3.2.0/bundler/vendor/fileutils/lib/fileutils.rb:2165: warning: already initialized constant Bundler::FileUtils::Entry_::S_IF_DOOR
/Users/deivid/Code/rubygems/rubygems/bundler/lib/bundler/vendor/fileutils/lib/fileutils.rb:2165: warning: previous definition of S_IF_DOOR was here
/Users/deivid/.asdf/installs/ruby/3.2.2/lib/ruby/site_ruby/3.2.0/bundler/vendor/fileutils/lib/fileutils.rb:2461: warning: already initialized constant Bundler::FileUtils::Entry_::DIRECTORY_TERM
/Users/deivid/Code/rubygems/rubygems/bundler/lib/bundler/vendor/fileutils/lib/fileutils.rb:2461: warning: previous definition of DIRECTORY_TERM was here
/Users/deivid/.asdf/installs/ruby/3.2.2/lib/ruby/site_ruby/3.2.0/bundler/vendor/fileutils/lib/fileutils.rb:2569: warning: already initialized constant Bundler::FileUtils::OPT_TABLE
/Users/deivid/Code/rubygems/rubygems/bundler/lib/bundler/vendor/fileutils/lib/fileutils.rb:2569: warning: previous definition of OPT_TABLE was here
/Users/deivid/.asdf/installs/ruby/3.2.2/lib/ruby/site_ruby/3.2.0/bundler/vendor/fileutils/lib/fileutils.rb:2627: warning: already initialized constant Bundler::FileUtils::LOW_METHODS
/Users/deivid/Code/rubygems/rubygems/bundler/lib/bundler/vendor/fileutils/lib/fileutils.rb:2627: warning: previous definition of LOW_METHODS was here
/Users/deivid/.asdf/installs/ruby/3.2.2/lib/ruby/site_ruby/3.2.0/bundler/vendor/fileutils/lib/fileutils.rb:2634: warning: already initialized constant Bundler::FileUtils::METHODS
/Users/deivid/Code/rubygems/rubygems/bundler/lib/bundler/vendor/fileutils/lib/fileutils.rb:2634: warning: previous definition of METHODS was here
Failed to install plugin `extended_bundler-errors`, due to Bundler::Plugin::MalformattedPlugin (ArgumentError: Trying to register Bundler::GemfileError for status code 4 but
Bundler::GemfileError is already registered)
```
Changing this to always use `$LOAD_PATH` fixes the problem.
https://github.com/rubygems/rubygems/commit/121a861c39
|
|
https://github.com/ruby/irb/commit/07fae94862
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/7020
|
|
from https://github.com/rubygems/rubygems/commit/bfb0ae69776069155d2092702bfbb5a12617d85a
Notes:
Merged: https://github.com/ruby/ruby/pull/6906
|
|
We attempted to remove things like this and reverted all of them, but I
think nobody relies on this unlike the positional arguments of
`ERB#initialize`.
https://github.com/ruby/erb/commit/92fde7e403
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/6287
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/5669
|
|
https://github.com/rubygems/rubygems/commit/a3b9f19080
|
|
(https://github.com/ruby/rdoc/pull/821)
This patch makes sure we only load relative code. Hence when coding or
testing rdoc, we'll be sure to always be using the correct code.
Discussion started at https://github.com/ruby/rdoc/pull/817.
Signed-off-by: Ulysse Buonomo <buonomo.ulysse@gmail.com>
https://github.com/ruby/rdoc/commit/aa41bd48eb
Co-authored-by: Nobuyoshi Nakada <nobu@ruby-lang.org>
|
|
The `exe` folder and `lib` folder of default gems don't locate under the
same place. While `exe/irb` will be under the gem folder, `irb.rb` will be
under `lib/ruby/VERSION/`.
So `require_relative` will make `irb` unuseable when shipped with Ruby.
Related discussion in the comments: https://github.com/ruby/irb/pull/335
https://github.com/ruby/irb/commit/99d3aa979d
|
|
1. `require` can mislead Ruby to load system irb's files and cause
constant redefined warnings as other code loads the same module/class
from lib folder.
2. Most files already use `require_relative`.
https://github.com/ruby/irb/commit/848d339f2e
|
|
rubygems + ruby combinations
https://github.com/rubygems/rubygems/commit/d6df0b7de0
Co-authored-by: André Arko <andre@arko.net>
|
|
https://github.com/rubygems/rubygems/commit/d647ab5607
|
|
https://github.com/ruby/irb/commit/e736a77076
|
|
https://github.com/ruby/irb/commit/b12f0cb8e2
|
|
|
|
|
|
|
|
|
|
|
|
Run ERb processing unconditionally since __FILE__ and $0 doesn't match
in a gem context.
Notes:
Merged: https://github.com/ruby/ruby/pull/3449
|
|
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/3114
|
|
|
|
[ruby-core:93516][Feature #15982]
https://github.com/ruby/racc/pull/123
|
|
Fixed misspellings reported at [Bug #16437], for default gems.
|
|
https://github.com/bundler/bundler/commit/e4cbb91b7d
|
|
This reverts commit d9d2bf6d522dd36d1ef2732e87cef8b7cba729fd.
https://github.com/bundler/bundler/commit/eeb2ff1561
|
|
https://github.com/bundler/bundler/commit/d9d2bf6d52
|
|
|
|
https://github.com/bundler/bundler/commit/a53709556b95a914e874b22ed2116a46b0528852
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67539 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
|
|
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66710 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
|
|
We have the platform issue on heroku:
* https://gist.github.com/schneems/26452540f6e2bbbcf2ea144f45f6b305
* https://github.com/heroku/heroku-buildpack-ruby/issues/833
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66323 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
|