aboutsummaryrefslogtreecommitdiffstats
path: root/spec
Commit message (Collapse)AuthorAgeFilesLines
* Merge RubyGems/Bundler masterHiroshi SHIBATA2022-12-203-20/+103
| | | | Pick from https://github.com/rubygems/rubygems/commit/ba3adad4d80038ffd7bea015da2f11d3e8a2ff82
* [rubygems/rubygems] fixMark Burns2022-12-201-0/+46
| | | | | | | | https://github.com/rubygems/rubygems/pull/6147 when --parseable and --groups used together https://github.com/rubygems/rubygems/commit/3b0b95c509
* [rubygems/rubygems] Turn `--ext` option into string. Deprecate usage without ↵Josef Šimánek2022-12-201-6/+25
| | | | | | | | explicit value. - this is preparation for onboarding Rust based extension gem generator https://github.com/rubygems/rubygems/commit/d32801bdbc
* [rubygems/rubygems] Use safe Marshal deserialization for dependency API ↵Josef Šimánek2022-12-202-1/+21
| | | | | | response. - adds Bundler#safe_load_marshal and Bundler::SAFE_MARSHAL_CLASSES listing safe classes to deserialize https://github.com/rubygems/rubygems/commit/e947c608cc
* [rubygems/rubygems] Fix crash when building resolution errors with OR ↵David Rodríguez2022-12-201-0/+39
| | | | | | requirements https://github.com/rubygems/rubygems/commit/8f287479bc
* [rubygems/rubygems] Add tests for bundle lockMichael Siegfried2022-12-201-1/+30
| | | | | | Ensure `bundle lock` handles pre flag just like bundle update does. https://github.com/rubygems/rubygems/commit/b9e85e3157
* [rubygems/rubygems] Test the public interfaceMichael Siegfried2022-12-201-55/+60
| | | | | | | | | With `GemVersionPromoter#sort_versions` being so simple, we no longer need to reach into the class's internals to make private methods public in order to effectively test. We can just allow both cases to go through the main method. https://github.com/rubygems/rubygems/commit/6cbe891003
* [rubygems/rubygems] Support for pre flag in `bundle update`Michael Siegfried2022-12-201-1/+30
| | | | | | | Passing this flag allows bumping to the current version, even if that version is prerelease. This works in concert with the current flags. https://github.com/rubygems/rubygems/commit/a6409e3509
* [rubygems/rubygems] Fix crash when lockfile is missing dependenciesDavid Rodríguez2022-12-202-34/+53
| | | | | | | | | | | | | We have a check for a corrupt lockfile right before installing. However, the check accounted for locked specs not satisfying locked dependencies, but not for locked specs missing for some locked dependencies. Instead of fixing this check, I decided to remove it in favor of automatically detecting the situation and re-resolve to automatically fix the lockfile rather than printing a warning but leave the problem there. https://github.com/rubygems/rubygems/commit/4a7a584252
* [rubygems/rubygems] Add bundle lock --update --bundlerAlyssa Ross2022-12-181-0/+20
| | | | | | | | | | | | bundle lock --update can do everything that bundle update can do, but it doesn't actually install gems. This is especially useful for generating a lockfile on a machine that doesn't have the libraries available to be able to build native extensions. But, there was no parallel for bundle update --bundler. So let's add one. https://github.com/rubygems/rubygems/commit/7fc00bd2a5
* Merge RubyGems/Bundler masterHiroshi SHIBATA2022-12-1553-464/+619
| | | | Pick from https://github.com/rubygems/rubygems/commit/084f7d1f21f6fc3e2bb685b7bda3653fb2891c6e
* Remove `require 'io/wait'` where it's no longer necessary. (#6932)Samuel Williams2022-12-152-2/+6
| | | | | | | * Remove `require 'io/wait'` as it's part of core now. * Update ruby specs using version gates. * Add note about why it's conditional.
* [rubygems/rubygems] Use better matcherDavid Rodríguez2022-12-131-1/+1
| | | | | | Hopefully it gives a better error. https://github.com/rubygems/rubygems/commit/5bc9ff64b6
* Merge RubyGems/Bundler masterHiroshi SHIBATA2022-12-1218-92/+83
| | | | from https://github.com/rubygems/rubygems/commit/bfb0ae69776069155d2092702bfbb5a12617d85a
* Add spec for fiber storage. (#6896)Samuel Williams2022-12-101-0/+111
|
* Clean up a temporary fileNobuyoshi Nakada2022-12-091-1/+4
|
* [Bug #19167] Remove useless conversion of classes for special constNobuyoshi Nakada2022-12-091-3/+5
|
* Added condition for ruby/ruby repositoryHiroshi SHIBATA2022-12-091-1/+5
|
* Merge syntax_suggest masterHiroshi SHIBATA2022-12-092-8/+34
| | | | Pick from https://github.com/ruby/syntax_suggest/commit/daee74dcb06296fa69fe8595fdff5d93d432b30d
* Merge RubyGems/Bundler masterHiroshi SHIBATA2022-12-0912-46/+176
| | | | Pick from https://github.com/rubygems/rubygems/commit/823c776d951f3c35094611473ec77f94e8bf6610
* Introduce `IO.new(..., path:)` and promote `File#path` to `IO#path`. (#6867)Samuel Williams2022-12-082-6/+19
|
* Update spec/bundler/bundler/fetcher/compact_index_spec.rbAaron Patterson2022-12-071-2/+0
| | | Co-authored-by: Takashi Kokubun <takashikkbn@gmail.com>
* Stop transitioning to UNDEF when undefining an instance variableAaron Patterson2022-12-071-0/+2
| | | | | | | | | | | | | | | | | | | | | | | Cases like this: ```ruby obj = Object.new loop do obj.instance_variable_set(:@foo, 1) obj.remove_instance_variable(:@foo) end ``` can cause us to use many more shapes than we want (and even run out). This commit changes the code such that when an instance variable is removed, we'll walk up the shape tree, find the shape, then rebuild any child nodes that happened to be below the "targetted for removal" IV. This also requires moving any instance variables so that indexes derived from the shape tree will work correctly. Co-Authored-By: Jemma Issroff <jemmaissroff@gmail.com> Co-authored-by: John Hawthorn <jhawthorn@github.com>
* update rbconfig spec to Unicode version 15.0.0Martin Dürst2022-12-062-4/+4
| | | | (this includes emoji version 15.0)
* Remove unguaranteed assertion [ci skip]Nobuyoshi Nakada2022-12-031-6/+0
| | | | | | It can be configured by `--with-os-version-style=TYPE` option, and just copies from theApple's installation as the default. We don't know why it is major only.
* UnboundMethod only refer defined_classKoichi Sasada2022-12-034-17/+58
| | | | | | | | | | | | | | | | | | | | | | | | | | | | UnboundMethod records caller's class, like `D` or `E` on the following case: ```ruby class C def foo = :foo end class D < C end class E < C end d = D.instance_method(:foo) e = E.instance_method(:foo) ``` But `d` and `e` only refers `C#foo` so that UnboundMethod doesn't record `D` or `E`. This behavior changes the following methods: * `UnboundMethod#inspect` (doesn't show caller's class) * `UnboundMethod#==` (`d == e` for example) fix https://bugs.ruby-lang.org/issues/18798
* Skip examples for SyntaxError extensions on Ruby 3.2Hiroshi SHIBATA2022-12-021-0/+4
|
* [Bug #19087] Merge to "trailing garbage" caseNobuyoshi Nakada2022-12-021-6/+3
|
* [Bug #19087] Fix an assertion of `String#to_c`Nobuyoshi Nakada2022-12-021-2/+4
|
* Update SyntaxSuggest to use angle brackets `>`schneems2022-11-306-50/+50
| | | | | | | | | ``` $ ruby tool/sync_default_gems.rb syntax_suggest Sync ruby/syntax_suggest ``` https://github.com/ruby/syntax_suggest/pull/161
* [ruby/syntax_suggest] Do not output "Syntax OK" when there's an errorschneems2022-11-282-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | Due to a problem with ripper we do not recognize `break` as invalid code. It's confusing that "Syntax OK" is output in that case. When there's no syntax error, the algorithm should not say anything. The exception is in the CLI and that's for compatibility with `ruby -wc` ``` $ cat /tmp/break.rb break ⛄️ 3.1.2 🚀 /Users/rschneeman/Documents/projects/syntax_suggest (schneems/no-syntax-not-okay-break) $ ruby -wc /tmp/break.rb Syntax OK ``` > Note that this is invalid, running this code will raise a Syntax error. ``` $ exe/syntax_suggest /tmp/break.rb Syntax OK ``` Close https://github.com/ruby/syntax_suggest/pull/157 https://github.com/ruby/syntax_suggest/commit/d7bd8f03a2
* [ruby/syntax_suggest] Failing test for #157schneems2022-11-281-0/+16
| | | | https://github.com/ruby/syntax_suggest/commit/14e8cdc916
* Make String#rstrip{,!} raise Encoding::CompatibilityError for broken coderangeJeremy Evans2022-11-241-7/+21
| | | | | | | | | | | | | | | | It's questionable whether we want to allow rstrip to work for strings where the broken coderange occurs before the trailing whitespace and not after, but this approach is probably simpler, and I don't think users should expect string operations like rstrip to work on broken strings. In some cases, this changes rstrip to raise Encoding::CompatibilityError instead of ArgumentError. However, as the problem is related to an encoding issue in the receiver, and due not due to an issue with an argument, I think Encoding::CompatibilityError is the more appropriate error. Fixes [Bug #18931]
* Use valid tokens as cookie namesNobuyoshi Nakada2022-11-222-11/+11
|
* Fixup spec/ruby/optional/capi/rbasic_spec.rb for mswinMSP-Greg2022-11-212-2/+2
|
* Update RSpec gemsDavid Rodríguez2022-11-151-6/+9
|
* Deal with different Ruby versionsTakashi Kokubun2022-11-121-2/+10
|
* Fix a CI failure in bigdecimalTakashi Kokubun2022-11-121-1/+1
|
* Migrate our resolver engine to PubGrubHiroshi SHIBATA2022-11-1215-239/+181
| | | | | | https://github.com/rubygems/rubygems/pull/5960 Co-authored-by: David Rodríguez <deivid.rodriguez@riseup.net>
* Merge RubyGems/Bundler master from ee2f8398324af4bc1b95f7565ce2fda98126e026v3_2_0_preview3Hiroshi SHIBATA2022-11-113-0/+63
|
* [rubygems/rubygems] Update bundler/spec/bundler/shared_helpers_spec.rbYusuke Endoh2022-11-101-1/+1
| | | | | https://github.com/rubygems/rubygems/commit/8b1481ba77 Co-authored-by: Nobuyoshi Nakada <nobu@ruby-lang.org>
* [rubygems/rubygems] Load "bundler/setup" in lib/rubygems.rbYusuke Endoh2022-11-101-0/+7
| | | | | | | | | | | | | | | Ruby interpreter loads some special gems at startup: did_you_mean, error_highlight, and syntax_suggest. These gems are loaded before `bundler/setup` is loaded by `RUBYOPT=-rbundler/setup`. So, the versions of the gems are not controllable by Gemfile. This change will `require "bundler/setup"` in rubygems.rb (i.e., before the special gems are loaded). Now `bundle exec` sets an environment variable `BUNDLER_SETUP`, and rubygems requires the variable if defined. See also: https://bugs.ruby-lang.org/issues/19089 https://github.com/rubygems/rubygems/commit/963cb65a2d
* [rubygems/rubygems] Add tests for universal Ruby with arch-specific prebuilt ↵Bo Anderson2022-11-083-0/+88
| | | | | | gems https://github.com/rubygems/rubygems/commit/11229b16c3
* Thread#native_thread_id is very platform specificNobuyoshi Nakada2022-11-081-1/+3
|
* Update to ruby/spec@740ccc8Benoit Daloze2022-11-07110-831/+1274
|
* Update to ruby/mspec@1e16420Benoit Daloze2022-11-071-4/+22
|
* Revert jobserver handling in specNobuyoshi Nakada2022-11-072-22/+6
|
* Let other test runners follow the change of GNU make 4.4 jobserverNobuyoshi Nakada2022-11-072-6/+22
|
* Skip `File.atime`/`File.mtime` tests randomly failing on TravisNobuyoshi Nakada2022-10-242-9/+11
| | | | | | Not only powerpc64le, also s390x and arm32 seem failing too. These failures are probably caused by filesystem settings on Travis, but unrelated to CPUs.
* [Bug #19004] `Complex.polar` handles complex singular `abs` argumentStephen Ierodiaconou2022-10-231-0/+16
| | | | | | | | | | | | | | | | `Complex.polar` accepts Complex values as arguments for the polar form as long as the value of the complex has no imaginary part (ie it is 'real'). In `f_complex_polar` this is handled by extracting the real part of the arguments. However in the case `polar` is called with only a single argument, the absolute value (abs), then the Complex is created without applying a check on the type of abs, meaning it is possible to create a Complex where the real part is itself an instance of a Complex. This change removes the short circuit for the single argument case meaning the real part extraction is performed correctly (by f_complex_polar). Also adds an example to `spec/ruby/core/complex/polar_spec.rb` to check that the real part of a complex argument is correctly extracted and used in the resulting Complex real and imaginary parts.
generated by cgit v1.2.3 (git 2.39.1) at 2024-10-01 01:40:53 +0000