summaryrefslogtreecommitdiff
path: root/lib
AgeCommit message (Collapse)Author
23 hours[ruby/error_highlight] Keep it work if paren exists after receiverMasataka Pocke Kuwabara
https://github.com/ruby/error_highlight/commit/b79d679bbd
3 days[ruby/reline] Support Terminfo on Cygwin and macOSaycabta
https://github.com/ruby/reline/commit/b0b75fcd27
3 days[ruby/reline] Don't check the existence of Terminfo on Windowsaycabta
https://github.com/ruby/reline/commit/320f09055c
3 days[ruby/reline] Check TYPE_VARIADICaycabta
https://github.com/ruby/reline/commit/8e62e46e33
3 days[ruby/reline] Define StringWithTiparm instead of singular methodaycabta
https://github.com/ruby/reline/commit/de234dc875
3 days[ruby/reline] Fixed Ctrl+Enter key in Windows.SilverPhoenix99
https://github.com/ruby/reline/commit/0c38e39023
3 days[ruby/reline] Check empty .inputrcaycabta
https://github.com/ruby/reline/commit/b60b3b76cd
3 days[ruby/reline] Add original C function declarations comment for each functionaycabta
https://github.com/ruby/reline/commit/9a25ee9f12
3 days[ruby/reline] Fix reline on OpenBSDJeremy Evans
OpenBSD doesn't support tiparm, only tparm. I'm not sure if the two are compatible, but this at least this allows me to run irb on OpenBSD. https://github.com/ruby/reline/commit/0ce2b34e2b
3 days[ruby/reline] Added support for Numpad divide key on Windows.SilverPhoenix99
https://github.com/ruby/reline/commit/84577da0c4
3 days[ruby/reline] Support Enter key of numpad on Windowsaycabta
The yamatanooroti gem can't emulate numpad key pressing... https://github.com/ruby/reline/commit/8e9da1aeaf
3 days[ruby/reline] Windows cmd: Don't type anything when pressing ALT keys aloneLars Kanis
Fixes #298 https://github.com/ruby/reline/commit/72acfcd27a
3 days[ruby/reline] Add TODO comment to implement tigetflag() and tigetnum()aycabta
https://github.com/ruby/reline/commit/a0d946a398
3 days[ruby/reline] Add require 'reline/terminfo' to use Reline::Terminfo.enabled?aycabta
https://github.com/ruby/reline/commit/7ef9805b35
3 daysUpdate the latest version of readline.gemspecHiroshi SHIBATA
3 days[ruby/net-http] Enforce write timeout when body_stream is usedMiguel Teixeira
The existing implementation of `Net::HTTP#write_timeout` relies on `Net::BefferedIO` to trigger the `Net::WriteTimeout` error. This commit changes `send_request_with_body_stream` to remove the optimization that was making `Net::HTTP#write_timeout` not work when `body_stream` is used. Open issue: https://bugs.ruby-lang.org/issues/17933 https://github.com/ruby/net-http/commit/a0fab1ab52
3 days[ruby/set] Improve What's Here linksBurdetteLamar
https://github.com/ruby/set/commit/76b056c3b9
3 days[ruby/set] Improve What's Here linksBurdetteLamar
https://github.com/ruby/set/commit/dd787a3988
3 days[ruby/set] gemspec: This gem exposes 0 executablesOlle Jonsson
This change removes unused configuration. https://github.com/ruby/set/commit/6c2338d699
3 days[ruby/set] Update documentation for intersect?/disjoint?Jeremy Evans
https://github.com/ruby/set/commit/35b69e9d69
3 days[ruby/set] Allow the use of any enumerable in intersect?/disjoint?Jeremy Evans
https://github.com/ruby/set/commit/1a73ab9047
3 days[ruby/set] Allow Set#intersect? and #disjoint? to accept array argumentJeremy Evans
Implements [Feature #17838] https://github.com/ruby/set/commit/d9b389bafa
4 days[ruby/optparse] More on tutorial (https://github.com/ruby/optparse/pull/23)Burdette Lamar
- Removed a largish block of repeated text. - Added sections "Top List and Base List" and "Methods for Defining Options" (on, define, etc.). - Linked from class OptionParser doc to the tutorial. https://github.com/ruby/optparse/commit/7f3195b9db
4 days[ruby/optparse] nodoc private methodsNobuyoshi Nakada
https://github.com/ruby/optparse/commit/f23d750d14
4 daysUpdate to latest uriBenoit Daloze
* https://github.com/ruby/uri/commit/bc47bf71df2b2e9cea09d0b2684ceac7355e42a0 * To include the fix from https://github.com/ruby/uri/pull/27
4 days[ruby/readline] Improve the gem's descriptionMarcus Stollsteimer
Improve the language in the gem's summary and description; also remove U+00A0 (no-break space) characters from post-install box. https://github.com/ruby/readline/commit/5037cf7ffc
4 days[ruby/resolv-replace] gemspec: Drop executables directiveOlle Jonsson
This gem exposes no executables. https://github.com/ruby/resolv-replace/commit/fa405185f7
4 days[ruby/resolv] Bump version to 0.2.1Hiroshi SHIBATA
https://github.com/ruby/resolv/commit/095f1c003f
4 days[ruby/getoptlong] RDoc: escape to avoid links to the word SetOlle Jonsson
We would like to avoid linking to the Set class for these words. https://github.com/ruby/getoptlong/commit/33b56d6141
4 days[ruby/getoptlong] gemspec: Drop executables directivesOlle Jonsson
This gem exposes 0 executables. https://github.com/ruby/getoptlong/commit/4522163cbd
5 days[ruby/find] Add Errno::EINVAL to list of ignored errorsJeremy Evans
This error can occur on Windows for certain filenames on certain code pages. Fixes [Bug #14591] https://github.com/ruby/find/commit/0a474d1027
5 daysRemove probably unintented symlinksNobuyoshi Nakada
5 daysDeal with Unicode ranges in the file emoji-sequences.txtMartin Dürst
Detect Unicode ranges and loop over them. This fixes issue #18028.
5 daysFix test failure for parallel testingHiroshi SHIBATA
5 daysAdded missing require for URI::WS classHiroshi SHIBATA
5 days[ruby/uri] Add proper Ractor support to URIBenoit Daloze
* Using a module to map scheme name to scheme class, which also works with Ractor. * No constant redefinition, no ObjectSpace, still fast lookup for initial schemes. https://github.com/ruby/uri/commit/883567fd81
5 days[ruby/uri] Revert "Fix to support Ruby 3.0 Ractor"Benoit Daloze
* This reverts commit 1faa4fdc161d7aeebdb5de0c407b923beaecf898. * It has too many problems, see https://github.com/ruby/uri/pull/22 for discussion. https://github.com/ruby/uri/commit/b959da2dc9
5 days[ruby/uri] Fix to support Ruby 3.0 Ractorkvokka
https://github.com/ruby/uri/commit/1faa4fdc16
5 days[rubygems/rubygems] Remove the warning for not defining a gem server sourceDaniel Niknam
Bundler has deprecated gemfiles without a global source and this feature is now obsolete. `Bundler::Definition#has_rubygems_remotes?` is removed because it's not used anymore. https://github.com/rubygems/rubygems/commit/d29dd2cb7b
5 days[rubygems/rubygems] Refactor Bundler::Dsl#check_rubygems_source_safety to ↵Daniel Niknam
improve readability `check_rubygems_source_safety` is responsible for: 1. if there are multiple global sources - for bundle 3.x raise an error - for bundle 2.x print a warning 2. print a warning if there is no explicit global source The second responsibility was added recently and now the logic could be extracted to improve readability. Conditions are still live in the `check_rubygems_source_safety` method since we don't want to call both functions always and that would help us achieve that. https://github.com/rubygems/rubygems/commit/f3d7e946ee
5 days[rubygems/rubygems] Deprecate Gemfile without an explicit global sourceDaniel Niknam
Raise a warning when parsing a Gemfile and it doesn't have a global source. Gemfiles like this, specially now that rubygems sources are are no longer merged into a single source for security, are very confusing because they generate a different lockfile depending on the gems you have locally installed. This is because bundler always use an implicit global source that defaults to locally installed gems. https://github.com/rubygems/rubygems/commit/b7523ad21c
5 days[rubygems/rubygems] Implement Bundler::SourceList#implicit_global_source?Daniel Niknam
This method is created to tell whether any global source exist in the object or not and it will be used by `Bundler:Dsl` to print a warning if no global source has been defined in the Gemfile. https://github.com/rubygems/rubygems/commit/422fec4438
5 days[rubygems/rubygems] Implement Bundler::Source::Rubygems#no_remotes?Daniel Niknam
This method is created to tell whether any remote exist in the object or not and it will be used by `Bundler:SourceList` to tell if a global source has been defined implicitly or not. https://github.com/rubygems/rubygems/commit/47e3ff0e47
5 days[rubygems/rubygems] Lazily load shellwordsDavid Rodríguez
https://github.com/rubygems/rubygems/commit/ef6388656a
5 days[rubygems/rubygems] Rubygems doesn't need to load the `base64` libraryDavid Rodríguez
https://github.com/rubygems/rubygems/commit/fe723c0f7f
5 days[rubygems/rubygems] Rubygems doesn't need to load the `resolv` libraryDavid Rodríguez
https://github.com/rubygems/rubygems/commit/8bf41f53cc
5 days[rubygems/rubygems] Lazily load `shellwords` libraryDavid Rodríguez
https://github.com/rubygems/rubygems/commit/e5532ef886
5 days[rubygems/rubygems] The `--quiet` should still display warningsDavid Rodríguez
The is the previous intentional behaviour until https://github.com/rubygems/bundler/commit/ca0676cb1c638e0b9747ea8c18f28adf82cc01de. In my opinion, that previous behaviour was better and should be restored, because we want our users to always see warnings and fix them. And the original issue that motivated the change is fixable by other means, namely through `BUNDLE_SILENCE_ROOT_WARNING`, or through `BUNDLE_SILENCE_DEPRECATIONS` in general. Finally, the --quiet option is still documented as "only print errors and warnings". So this PR essentially reverts https://github.com/rubygems/bundler/commit/ca0676cb1c638e0b9747ea8c18f28adf82cc01de for the above reasons. https://github.com/rubygems/rubygems/commit/35f2254dfc
5 days[rubygems/rubygems] Check requirements classesNobuyoshi Nakada
Mitigate the security risk: https://devcraft.io/2021/01/07/universal-deserialisation-gadget-for-ruby-2-x-3-x.html https://github.com/rubygems/rubygems/commit/141c2f4388
5 days[rubygems/rubygems] Remove all `syck` traces from `rubygems`David Rodríguez
After reading [this blog post](https://blog.rubygems.org/2011/08/31/shaving-the-yaml-yak.html), published almost 10 years ago already, my understanding is that this problem could come up in two ways: * Rubygems.org serving corrupted gemspecs". As far as I understand this was fixed in rubygems.org a lot time ago, since https://github.com/rubygems/rubygems.org/pull/331. * Clients having a ten years old gemspec cache with some of these bad gemspecs. In this case, there's no easy solution but I think ten years is enough and rebuilding the cache should do the trick. So, I think it's time we remove this. https://github.com/rubygems/rubygems/commit/afcb15d556