summaryrefslogtreecommitdiff
path: root/lib
AgeCommit message (Collapse)Author
2019-08-27Remove test_mode in `lib/reline`.manga_osyo
2019-08-27Refactoring Reline accessor.manga_osyo
2019-08-27Handle binding.irb for frozen objects and BasicObjects using a delegateJeremy Evans
Fixes Ruby Bug 13264
2019-08-27Move private call without arguments inside methodJeremy Evans
This code did not have the desired effect. I'm not sure if irb_binding is supposed to be private or not. If not, the private call can just be removed.
2019-08-25lib/webrick.rb: use require_relative for webrick/utils.rbYusuke Endoh
`require "webrick/utils.rb"` should load `lib/webrick/utils.rb`, but on some CI machines, it wrongly loads `test/webrick/utils.rb`, which caused circular require warning: https://rubyci.org/logs/rubyci.s3.amazonaws.com/ubuntu/ruby-master/log/20190825T093007Z.log.html.gz ``` /data/chkbuild/tmp/build/20190825T093007Z/ruby/lib/rubygems/core_ext/kernel_require.rb:61: warning: /data/chkbuild/tmp/build/20190825T093007Z/ruby/lib/rubygems/core_ext/kernel_require.rb:61: warning: loading in progress, circular require considered harmful - /data/chkbuild/tmp/build/20190825T093007Z/ruby/lib/webrick.rb ```
2019-08-22Always check multiline terminationaycabta
2019-08-21Add abs to Matrix (#2199)Fernando Wolf Bona
2019-08-22IRB's multiline history is enable only when Reidline modeaycabta
2019-08-21The investigation is going on...Nobuyoshi Nakada
2019-08-21[bundler/bundler] Remove old rubies stuff no longer neededDavid Rodríguez
https://github.com/bundler/bundler/commit/36fb3287f4
2019-08-20Avoid creating Hash objects per each mon_synchronize call (#2393)Akira Matsuda
Notes: Merged-By: amatsuda <ronnie@dio.jp>
2019-08-20[rubygems/rubygems] Use `RbConfig::CONFIG['rubylibprefix']`Nobuyoshi Nakada
It is defined since ruby 1.9.2. https://github.com/rubygems/rubygems/commit/84981ca908
2019-08-20Fix some bundler specs (#2380)David Rodríguez
* These seem to consistenly pass already * Show actual command when running `make test-bundler` Current the setup command that installs the necessary gems for testing bundler was printed, but not the actual command that runs the tests. That was a bit confusing. * Borrow trick from setproctitle specs * A title that long doesn't get set sometimes No idea why, but the test doesn't need that the title is that long. * Fix most gem helper spec ruby-core failures * Fix the rest of the gem helper failures * Fix version spec by improving the assertion * Remove unnecessary `BUNDLE_RUBY` environment var We can use `RUBY` when necessary, and `BUNDLE_RUBY` is not a good name because bundler considers `BUNDLE_*` variables as settings. * Rename `BUNDLE_GEM` to `GEM_COMMAND` This is more descriptive I think, and also friendlier for bundler because `BUNDLE_` env variables are interpreted by bundler as settings, and this is not a bundler setting. This fixes one bundler spec failure in config specs against ruby-core. * Fix quality spec when run in core Use the proper path helper. * Fix dummy lib builder to never load default gems If a dummy library is named as a default gem, when requiring the library from its executable, the default gem would be loaded when running from core, because in core all default gems share path with bundler, and thus they are always in the $LOAD_PATH. We fix the issue by loading lib relatively inside dummy lib executables. * More exact assertions Sometimes I have the problem that I do some "print debugging" inside specs, and suddently the spec passes. This happens when the assertion is too relaxed, and the things I print make it match, specially when they are simple strings like "1.0" than can be easily be part of gem paths that I print for debugging. I fix this by making a more exact assertion. * Detect the correct shebang when ENV["RUBY"] is set * Relax assertion So that the spec passes even if another paths containing "ext" are in the load path. This works to fix a ruby-core issue, but it's a better assertion in general. We just want to know that the extension path was added. * Use folder structure independent path helper It should fix this spec for ruby-core. * Fix the last failing spec on ruby-core * Skip `bundle open <default_gem>` spec when no default gems
2019-08-20Treat two types "do" correctlyaycabta
A "do" what has followed a token what has EXPR_CMDARG is for a block, and in other cases "do" is for "while", "until" or "for".
2019-08-19Update the canonical repository urlHiroshi SHIBATA
2019-08-19Prefer Regexp#=~ to Regexp#match when the RHS may be nilNobuyoshi Nakada
2019-08-19lib/rdoc/markup/parser.rb: remove a unused variable initializationYusuke Endoh
2019-08-18[bundler/bundler] No need to activate the `fileutils` default gemDavid Rodríguez
The version we're vendoring actually relaxed this restriction back to 2.3.0+, so we can always use the vendored version. https://github.com/bundler/bundler/commit/d366cbfe5d
2019-08-18[bundler/bundler] Last relative requiresDavid Rodríguez
https://github.com/bundler/bundler/commit/fb587b9ebb
2019-08-18[bundler/bundler] Move local variable to only branch where it's usedDavid Rodríguez
https://github.com/bundler/bundler/commit/3995b3345d
2019-08-18[bundler/bundler] Fix open default gem errorZehan Zhao
https://github.com/bundler/bundler/commit/792d724752
2019-08-18[bundler/bundler] Fix `bundle doctor` commandDavid Rodríguez
Previously `bundle doctor` would fail on any bundle that does not include git gems or plugins. This is because the previously used `Bundler.home` does not exist unless the bundle includes git gems or plugins. For example, with `bundle config set path .bundle`, it points to which does not exist unless this kind of gems exist in the Gemfile. The name `Bundler.home` is really unfortunate, it should probably be have more descriptive name, and be private. But for now I just want to make `bundle doctor` usable. https://github.com/bundler/bundler/commit/5531a18c1e
2019-08-18[bundler/bundler] Bundler displays a duplicate gem entries warning even if ↵David Stosik
gems only appear once per group https://github.com/bundler/bundler/commit/d18a83109e
2019-08-18The "exe" dir doesn't exist in this repostiroyaycabta
2019-08-18Don't crash when deleting at the end of the lineAlan Wu
To reproduce this bug, type one character into irb, then press the delete key on your keyboard.
2019-08-18$LOAD_PATH elements should be real pathsNobuyoshi Nakada
Installed path may contain symbolic links.
2019-08-17Remove CI files from listaycabta
2019-08-17Removed formatter_test_case and text_formatter_test_case from ↵Hiroshi SHIBATA
Gem::Specification#files.
2019-08-17Removed autoload from Markup.Hiroshi SHIBATA
2019-08-17Removed test_case files from lib directory.Hiroshi SHIBATA
2019-08-17[bundler/bundler] Fix bundle bin location in core repoDavid Rodríguez
https://github.com/bundler/bundler/commit/9437568ab4
2019-08-17Support the current stable version of Ruby like 2.5 and 2.6.Hiroshi SHIBATA
2019-08-17Revert "`Gem.load_path_insert_index always returns non-nil index after Ruby 1.9"Hiroshi SHIBATA
This reverts commit 260ef51a73c067599826c8ab110c53994c1b6226. This broke the stable versions of Ruby like 2.4 and 2.5
2019-08-17Added comments for extended require by RubyGemsHiroshi SHIBATA
2019-08-17`Gem.load_path_insert_index always returns non-nil index after Ruby 1.9Hiroshi SHIBATA
2019-08-17Try to continue on LoadError with gem_original_requireHiroshi SHIBATA
2019-08-17Keep the existance behavior with symlink pathHiroshi SHIBATA
2019-08-17Revert "Revert "[rubygems/rubygems] [Require] Ensure -I beats a default gem""Hiroshi SHIBATA
This reverts commit 75d29db8f965893bb6ab38b9008abc80cdda246e.
2019-08-17Fix typosKazuhiro NISHIYAMA
2019-08-17Revert "[rubygems/rubygems] [Require] Ensure -I beats a default gem"Hiroshi SHIBATA
This reverts commit 00cd5d74cecb6aa4a184e57e2b8246ef6e45d458.
2019-08-17Fixed Insecure Operation in requireHiroshi SHIBATA
Caused by 00cd5d74ce
2019-08-17[rubygems/rubygems] Fixup #2844Hiroshi SHIBATA
https://github.com/rubygems/rubygems/commit/5924286ae2
2019-08-17[rubygems/rubygems] installer.rb - fix #windows_stub_scriptMSP-Greg
use ruby_exe in heredocs instead of ruby.exe https://github.com/rubygems/rubygems/commit/9f1b7d6590
2019-08-17[rubygems/rubygems] Do not mutate uri.query during s3 signature creationAlexander Pakulov
https://github.com/rubygems/rubygems/commit/c0275ee537
2019-08-17[rubygems/rubygems] Make deprecate Gem::RubyGemsVersion and Gem::ConfigMap.Hiroshi SHIBATA
https://github.com/rubygems/rubygems/commit/1133c2f700
2019-08-17[rubygems/rubygems] Return `nil` to clarify return value is ignoredDavid Rodríguez
https://github.com/rubygems/rubygems/commit/8702f59d32
2019-08-17[rubygems/rubygems] Autoswitch to exact bundler version if presentDavid Rodríguez
https://github.com/rubygems/rubygems/commit/bb02953a97
2019-08-17[rubygems/rubygems] Don't unregister default specificationsDavid Rodríguez
I think this should be more efficient? https://github.com/rubygems/rubygems/commit/a1de78104f
2019-08-17[rubygems/rubygems] Fix removing unresolved default spec files from mapDavid Rodríguez
https://github.com/rubygems/rubygems/commit/7964917bbc
2019-08-17[rubygems/rubygems] Little refactorDavid Rodríguez
There's already a method called `suffix_pattern`, that's different from this local variable. So, move the local variable to a `suffix_regexp` that clearly differenciates from `suffix_pattern`. https://github.com/rubygems/rubygems/commit/4ec69c48b9
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-20 17:18:52 +0000