| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
Fixes [Bug #10314]
|
|
|
|
|
| |
File.extname now returns a dot string at a name ending with a dot.
[Bug #15267]
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* {String|Symbol}#match{?} with nil returns falsy
To improve consistency with Regexp#match{?}
* String#match(nil) returns `nil` instead of TypeError
* String#match?(nil) returns `false` instead of TypeError
* Symbol#match(nil) returns `nil` instead of TypeError
* Symbol#match?(nil) returns `false` instead of TypeError
* Prefer exception
* Follow empty ENV
* Drop outdated specs
* Write ruby/spec for above
https://github.com/ruby/ruby/pull/1506/files#r183242981
* Fix merge miss
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
This reverts commit a56d742e69aa8a3a1fe92fc515d93f6e51cf5fbc.
I was checking the CI result of the wrong revision. It actually worked
fine https://ci.appveyor.com/project/ruby/ruby/builds/27866303. Never
mind...
|
|
|
|
|
| |
For some reason the guard_not seems not working as expected
https://ci.appveyor.com/project/ruby/ruby/builds/27866153/job/v6wa6q6p7b7n7r37
|
|
|
|
|
| |
for mswin. This spec is not valid for mswin platform.
https://ci.appveyor.com/project/ruby/ruby/builds/27748774/job/85khngfpc806m5lj
|
|
|
|
|
|
| |
return directly in class/module is an error, so return in
proc in class/module should also be an error. I believe the
previous behavior was an unintentional oversight during the
addition of top-level return in 2.4.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Some warnings are because the @o.rb_scan_args call doesn't
include keyword arguments, but the first argument is passed to
rb_scan_args may have a last hash treated as keywords. Those
should be handled using rb_scan_args_kw on Ruby 2.7.
Other warnings are for the deprecated rb_scan_args behavior to
split option hashes or treat a nil argument as an option hash.
Those warnings should just be suppressed.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
a frozen String
* Always the same frozen String for each of these values.
* Avoids extra allocations whenever calling these 3 methods.
* See [Feature #16150]
|
|
|
|
|
|
| |
* Always the same frozen String for a given Module or Class.
* Avoids extra allocations whenever calling Module#name.
* See [Feature #16150]
|
|
|
|
|
|
| |
* Always the same frozen String for a given Symbol.
* Avoids extra allocations whenever calling Symbol#to_s.
* See [Feature #16150]
|
|
|
|
|
|
|
|
| |
Also have spec check that it returns ENV.
Mostly from burdettelamar@yahoo.com (Burdette Lamar).
Fixes [Bug #16164]
|
| |
|
| |
|
|
|
|
| |
[Feature #11297] [Feature #16123]
|
|
|
|
| |
[Feature #11297] [Feature #16123]
|
|
|
|
|
|
|
|
|
|
| |
This makes it consistent with calling private attribute assignment
methods, which currently is allowed (e.g. `self.value =`).
Calling a private method in this way can be useful when trying to
assign the return value to a local variable with the same name.
[Feature #11297] [Feature #16123]
|
| |
|
| |
|
|
|
|
|
|
| |
And skip them all for bundler 3.
https://github.com/bundler/bundler/commit/b88936cdc2
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
7340: Fix bundle clean issue r=deivid-rodriguez a=deivid-rodriguez
### What was the end-user problem that led to this PR?
The problem was that `bundle clean` is crashing under some conditions.
### What was your diagnosis of the problem?
My diagnosis was that sometimes (when the bundle includes git sourced gems with extensions), it assumes that some paths exist, but they don't.
### What is your fix for the problem, implemented in this PR?
My fix is to ignore those paths.
### Why did you choose this fix out of the possible options?
I chose this fix because it fixes the issue.
Fixes #7338.
Co-authored-by: David Rodríguez <deivid.rodriguez@riseup.net>
(cherry picked from commit b007fde67c77c1f15f13b97eda186644c2a2be04)
https://github.com/bundler/bundler/commit/3766053507
|
|
|
|
|
|
| |
It was suggested a deprecated command as a fix.
https://github.com/bundler/bundler/commit/e330a9a34f
|
|
|
|
| |
https://github.com/bundler/bundler/commit/65351c58b8
|
|
|
|
|
|
| |
This reverts commit 3dc509e645abb497e4dc92a7c42be471ff87db0b.
https://github.com/bundler/bundler/commit/b5766564fb
|
|
|
|
|
|
| |
This reverts commit 00b095b98fe4bd44950beaf3bc9f1d91eac7b69e.
https://github.com/bundler/bundler/commit/e93bce3b20
|
|
|
|
| |
https://github.com/bundler/bundler/commit/a86b49f1b9
|
|
|
|
| |
https://github.com/bundler/bundler/commit/b7fc6f4187
|
|
|
|
| |
https://github.com/bundler/bundler/commit/0a0e7cf5ec
|
| |
|
|
|
|
|
|
| |
Calling some syscall functions such as Dir.chroot causes SIGSYS instead
of EPERM on Android.
This change skips all tests that stops the test-suite run.
|
| |
|
| |
|
|
|
|
| |
[Bug #16007]
|
|
|
|
|
| |
In order to check whether a path is absolute or not in a portable way.
[Feature #15868]
|
|
|
|
|
| |
This spec should not be checking where methods are defined, only
that the method works as expected (returns a Lazy instance).
|
| |
|
| |
|