| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
PowerShell does not expand by `%varname%` syntax.
|
|
|
|
|
| |
Github workflow stopped using cmd.exe suddenly, and `||` and `&&`
seem not working in PowerShell.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Get rid of these redundant and useless warnings.
```
$ ruby -e 'def bar(a) a; end; def foo(...) bar(...) end; foo({})'
-e:1: warning: The last argument is used as the keyword parameter
-e:1: warning: for `foo' defined here
-e:1: warning: The keyword argument is passed as the last hash parameter
-e:1: warning: for `bar' defined here
```
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Fixes Ruby Bug 9876.
|
|
|
|
|
| |
So that the result structure can be accessed as `$number`
variables, not a mere `VALUE`.
|
|
|
|
| |
This reverts commit 5ebb0d50f6560b35bc03deb79341a115c5f782ee.
|
|
|
|
| |
This reverts commit 4d844cbaed518743776594fa5ae33b86fe176ad1.
|
|
|
|
| |
This reverts commit ce6caade7c57a505f73086ccd7b33c14f7715f22.
|
|
|
|
|
|
|
| |
Only untaint result on Ruby <2.7, as taint support is deprecated
in Ruby 2.7+ and no longer has an effect.
https://github.com/ruby/webrick/commit/4c430f9410
|
|
|
|
| |
https://github.com/ruby/webrick/commit/6b6990ec81
|
|
|
|
|
|
|
|
|
|
| |
While the stripping of header values is required by RFC 2616 4.2 and
RFC 7230 3.2.4, the squishing is not and can break things, such as
when one header contains an HMAC of another header.
Fixes Ruby Bug 7021.
https://github.com/ruby/webrick/commit/8b96088a86
|
|
|
|
| |
https://github.com/ruby/webrick/commit/00c281caa7
|
|
|
|
|
|
|
| |
It is currently broken, and even if it worked, it can cause problems
when debugging. See Ruby Bug 10715.
https://github.com/ruby/webrick/commit/575dea8656
|
|
|
|
| |
https://github.com/ruby/webrick/commit/3b51f6b4d2
|
|
|
|
|
|
|
| |
Ruby 2.7 deprecates taint and it no longer has an effect.
The lack of taint support should not cause a problem in
previous Ruby versions.
https://github.com/ruby/fiddle/commit/18d6fb6915
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Use ffi_closure_free unconditionally.
The current conditionals reflect historic heritage of FFI. Usage of
ffi_closure_free should be better default nowadays, because libffi 3.0.5
fixing issues of ffi_closure_free should be widely available.
* RUBY_LIBFFI_MODVERSION is not used anymore.
Because `ffi_closure_free()` is not used unconditionally, there is no
other use for RUBY_LIBFFI_MODVERSION define, so drop its usage.
* Use more meaningful variable name.
`ver` variable used to be used to pupulate RUBY_LIBFFI_MODVERSION
define. Since the define was removed, the `libffi_dir` variable name
should better describe the remaining usage of the variable.
https://github.com/ruby/fiddle/commit/c49cc79eb8
|
|
|
|
| |
https://github.com/ruby/fiddle/commit/ea06b28db8
|
|
|
|
| |
https://github.com/ruby/fiddle/commit/a01a962342
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Fix a failing test
This commit fixes the following failure:
```
1) Failure:
Fiddle::TestImport#test_no_message_with_debug [/Users/mrkn/src/github.com/ruby/fiddle/test/fiddle/test_import.rb:152]:
1. [2/2] Assertion for "stderr"
| <[]> expected but was
| <["Exception `NameError' at /Users/mrkn/.rbenv/versions/2.5.1/lib/ruby/2.5.0/fiddle/import.rb:157 - uninitialized constant Fiddle::Function::STDCALL"]>.
```
* Stop using Bundler.with_clean_env
* Clear existing Ruby environment variables on test_no_message_with_debug
https://github.com/ruby/fiddle/commit/13133ddec8
|
|
|
|
|
|
|
|
|
|
|
|
| |
If the first parameter to Fiddle::Function is a closure object (rather
than an interger), `rb_Integer` will cast it to an integer but not
maintain a reference to the closure. Then if the closure gets GC'd, we
have a segv. This commit keeps a reference to the original parameter to
initialize so that the object will not be GC'd.
Fixes: https://bugs.ruby-lang.org/issues/13286
https://github.com/ruby/fiddle/commit/0fc697bbc5
|
| |
|
|
|
|
|
|
| |
Gem::Specification#add_development_dependency.
https://github.com/ruby/date/commit/13c94362c2
|
|
|
|
| |
https://github.com/ruby/date/commit/8c02586a98
|
|
|
|
| |
https://github.com/ruby/date/commit/af01edd7d8
|
|
|
|
|
|
|
|
| |
Ruby 2.7 deprecates taint and it no longer has an effect.
The lack of taint support should not cause a problem in
previous versions.
https://github.com/ruby/date/commit/519470dc3b
|
|
|
|
|
|
| |
Fixes Ruby Bug 12961
https://github.com/ruby/date/commit/7f533c2552
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, the type of these arguments were not checked, leading to
NoMethodErrors in some cases, and TypeErrors in other cases, but not
showing what field was having the problems. This change makes it so
the field with the problem is included in the error message.
For the valid_*? methods, this changes them to return false if one
of the arguments that should be numeric is not.
Fixes Ruby Bug 11935
Fixes Ruby Misc 15298
https://github.com/ruby/date/commit/a2f4b665f8
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, julian dates would not round trip through to_time.to_date,
because Time is always considered gregorian. This converts the Date
instance from julian to gregorian before converting to Time, ensuring
that an equal date object will be returned if converting that Time
back to Date.
This does result in julian Date objects showing different day values
if converting to Time.
Fixes Ruby Bug 8428.
https://github.com/ruby/date/commit/d8df64555e
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
To perform a regular method call, the VM needs two structs,
`rb_call_info` and `rb_call_cache`. At the moment, we allocate these two
structures in separate buffers. In the worst case, the CPU needs to read
4 cache lines to complete a method call. Putting the two structures
together reduces the maximum number of cache line reads to 2.
Combining the structures also saves 8 bytes per call site as the current
layout uses separate two pointers for the call info and the call cache.
This saves about 2 MiB on Discourse.
This change improves the Optcarrot benchmark at least 3%. For more
details, see attached bugs.ruby-lang.org ticket.
Complications:
- A new instruction attribute `comptime_sp_inc` is introduced to
calculate SP increase at compile time without using call caches. At
compile time, a `TS_CALLDATA` operand points to a call info struct, but
at runtime, the same operand points to a call data struct. Instruction
that explicitly define `sp_inc` also need to define `comptime_sp_inc`.
- MJIT code for copying call cache becomes slightly more complicated.
- This changes the bytecode format, which might break existing tools.
[Misc #16258]
|
|
|
|
|
|
|
| |
If a fiber is invoked with transfer method (such as "f.transfer"),
then the invoked fiber ("f") is labeled as "transferred" and this
fiber can not be invoked with Fiber#resume. This patch adds
transferred attribute for "Fiber#to_s" (and inspect).
|
|
|
|
|
|
| |
This reverts commit fa8ac91e957a076f6df1adaecad7896817138009.
Previous behavior is intentional.
|
|
|
|
| |
This reverts commit ff953a003e03f5f070112ececefab4c07ff4cb0e.
|
| |
|
| |
|
|
|
|
| |
Coverity Scan complains it.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It made rdoc fail.
https://rubyci.org/logs/rubyci.s3.amazonaws.com/ubuntu1804/ruby-master/log/20191023T183005Z.fail.html.gz
```
RDoc is not a full Ruby parser and will fail when fed invalid ruby programs.
The internal error was:
(ArgumentError) invalid byte sequence in US-ASCII
uh-oh! RDoc had a problem:
invalid byte sequence in US-ASCII
```
|
| |
|
|
|
|
|
|
| |
On German keyboard, right alt key acts as like shift key.
Ex. right-alt-8 is just "[". This input doesn't have meta-key statement.
|
|
|
|
| |
Refreshes bundled gems to the latest version, and extracts them.
|
| |
|
| |
|
| |
|
| |
|