summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* [ruby/irb] Activate yamatanooroti tests on CIStan Lo2022-11-271-2/+2
| | | | | | | | | | (https://github.com/ruby/irb/pull/459) * Activate yamatanooroti tests on CI * Fix delete test https://github.com/ruby/irb/commit/750cf4c480
* [ruby/net-http] [DOC] Enhanced RDoc for Net::HTTPHeaderBurdette Lamar2022-11-271-17/+58
| | | | https://github.com/ruby/net-http/commit/77c6878970
* MJIT: Remove a duplicated rescueTakashi Kokubun2022-11-261-5/+2
| | | | | `#compile` has a catch-call rescue, so compile_insn_entry shouldn't do that. It was a temporary code needed during the migration.
* MJIT: Merge mjit_compiler.rb into mjit.rbTakashi Kokubun2022-11-265-20/+13
| | | | There are too many mjit_compiler.* files. It was hard to find files.
* [ruby/net-http] Fix test for Ruby headPeter Zhu2022-11-261-1/+5
| | | | | | | The error raised for broken coderanges was changed in ruby/ruby@571d21f and the test was fixed in that commit but not ported to this repo. ruby/net-http@e6185dda26ea6db7a3515d4f47ab231f5f4ac902
* Update bundled gems list at 3853385377525258881d35850a4247 [ci skip]git2022-11-261-1/+1
|
* Update bundled_gems (#6813)Soutaro Matsumoto2022-11-261-1/+1
| | | * Update bundled_gems
* Update default gems list at 534bac04e71efcbb9f4dc877f490b9 [ci skip]git2022-11-261-1/+1
|
* [ruby/erb] Version 4.0.0Takashi Kokubun2022-11-261-1/+1
| | | | https://github.com/ruby/erb/commit/2809a54d88
* Do not use the same variable for multiple thingsTakashi Kokubun2022-11-251-5/+5
| | | | | | | `conv` proc is used before and after the `url` variable is updated. So this script didn't seem to behave correctly for the "Close #xxx" syntax. Reusing the same variable name for different things seems prone to errors.
* Support other GitHub PR/issue syntaxesTakashi Kokubun2022-11-251-1/+1
| | | | https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue
* Allow an arbitrary number of newlinesTakashi Kokubun2022-11-251-1/+1
|
* Revert "Update default gems list at 574896a0ce99ab00676aa5ff2fabd3 [ci skip]"Takashi Kokubun2022-11-251-27/+0
| | | | This reverts commit eb3a6ae524b029e96738f21931d95dfad1caed2f.
* Update default gems list at 574896a0ce99ab00676aa5ff2fabd3 [ci skip]git2022-11-261-0/+27
|
* [ruby/erb] Define ERB::Escape moduleTakashi Kokubun2022-11-262-10/+18
| | | | | (https://github.com/ruby/erb/pull/38) Close #32
* Revert "Update default gems list at d0bb24c497ceae01cc7b7698365982 [ci skip]"Nobuyoshi Nakada2022-11-261-27/+0
| | | | | This reverts commit ba26dd7ba557f1a8d58251bb8437d579e0d5d23a, which duplicates the list.
* Update default gems list at d0bb24c497ceae01cc7b7698365982 [ci skip]git2022-11-261-0/+27
|
* [DOC] Fix loose and tight listsNobuyoshi Nakada2022-11-261-5/+34
| | | | | The MarkDown parser of RDoc does not allow mixing loose and tight lists, and the results may be very unexpected otherwise.
* [DOC] Fix indents of nested bullet listsNobuyoshi Nakada2022-11-261-16/+16
|
* Follow the NEWS.md change up [ci skip]Nobuyoshi Nakada2022-11-261-4/+4
|
* MJIT: Change default --mjit-max-cache back to 100Takashi Kokubun2022-11-252-1/+2
| | | | | | | | | | | | | | | | | These days we benchmark MJIT using yjit-bench. The warmup duration in yjit-bench is very short, so compiling many methods comes at a cost even while it's actually optimal for MJIT to compile everything / tens of thousands of methods once it reaches the peak performance. yjit-bench doesn't necessarily represent the peak performance on production. It measures the performance of Ruby 30~60s after boot. If your JIT takes more than 1 minute to warm up, there's no way for the JIT to make the numbers good on yjit-bench. Until we make MJIT's compilation much faster, we don't afford compiling 10,000 methods on yjit-bench. This change alone makes MJIT's benchmark number on railsbench 2x better :p
* MJIT: Refactor source_shape_id extractionTakashi Kokubun2022-11-251-13/+14
| | | | I'm not comfortable indenting code that deeply.
* MJIT: Remove obsoleted variableTakashi Kokubun2022-11-251-2/+0
| | | | no longer used after 4ea9d7d7c223ff92365c4a013fc1bd073d67a3a5
* MJIT: Remove the code to optimize shape transitionTakashi Kokubun2022-11-252-12/+2
| | | | | because this code crashes on railsbench. I'll try adding a repro for it later, but I don't know shapes enough to craft it right away.
* YJIT: Run test-all tests without requiring RUN_OPTSAlan Wu2022-11-253-18/+19
| | | | | | | | Most tests in test_yjit.rb use a sub process, so we can run them even when the parent process is not running with YJIT. Run them so simply running `make check` tests YJIT a bit. [Misc #19149]
* Fix autoload status of statically linked extensionsAlan Wu2022-11-254-13/+72
| | | | | | | | | | | | | | | | | | Previously, for statically-linked extensions, we used `vm->loading_table` to delay calling the init function until the extensions are required. This caused the extensions to look like they are in the middle of being loaded even before they're required. (`rb_feature_p()` returned true with a loading path output.) Combined with autoload, queries like `defined?(CONST)` and `Module#autoload?` were confused by this and returned nil incorrectly. RubyGems uses `defined?` to detect if OpenSSL is available and failed when OpenSSL was available in builds using `--with-static-linked-ext`. Use a dedicated table for the init functions instead of adding them to the loading table. This lets us remove some logic from non-EXTSTATIC builds. [Bug #19115]
* [StepSecurity] ci: Harden GitHub ActionsStepSecurity Bot2022-11-2516-54/+54
| | | Signed-off-by: StepSecurity Bot <bot@stepsecurity.io>
* NEWS: "Find pattern" is not related to find.rb [ci skip]Nobuyoshi Nakada2022-11-251-1/+1
|
* [Feature #18925] [DOC] Add `FileUtils.ln_sr` to NEWSNobuyoshi Nakada2022-11-251-0/+5
|
* [DOC] Fix AST documentsNobuyoshi Nakada2022-11-251-10/+11
| | | | | | - Fix indents of `tokens`, to make the contents of Token a list - Move the example of `tokens` to separate from the above list - Markup keyword argument and method name
* [DOC] Remove extraneous backticksNobuyoshi Nakada2022-11-251-19/+19
| | | | So cross-references to defined classes/modules/methods work.
* Fix indents in NEWS [ci skip]Nobuyoshi Nakada2022-11-251-84/+84
| | | | | The MarkDown parser in RDoc requires 4 columns indentation for paragraphs following list items.
* [ruby/erb] Keep ERB::Util#html_escape privateTakashi Kokubun2022-11-252-3/+3
| | | | | | | ERB::Util.html_escape has been public, but ERB::Util#html_escape had been private. https://github.com/ruby/erb/commit/e62210bf56
* [rubygems/rubygems] Stop installing everything under "lib" at the top in all ↵Nobuyoshi Nakada2022-11-251-8/+1
| | | | | | tests https://github.com/rubygems/rubygems/commit/f9772d62e1
* `remain` no longer starts with 0Nobuyoshi Nakada2022-11-251-7/+2
|
* [Bug #18971] Add precheck to enumeratorNobuyoshi Nakada2022-11-252-13/+56
|
* [Bug #19145] `volatile` on an argument may not be effectiveNobuyoshi Nakada2022-11-251-1/+2
|
* The mode flags may be clobbered by tag jumpsNobuyoshi Nakada2022-11-251-1/+1
|
* Add examples to error_tolerant option in NEWS [ci skip]yui-knk2022-11-251-0/+41
|
* add debug context APIs for debuggers (frame depth)Koichi Sasada2022-11-252-13/+61
| | | | | | | | | | | | | The following new debug context APIs are for implementing debugger's `next` (step over) and similar functionality. * `rb_debug_inspector_frame_depth(dc, index)` returns `index`-th frame's depth. * `rb_debug_inspector_current_depth()` returns current frame depth. The frame depth is not related to the frame index because debug context API skips some special frames but proposed `_depth()` APIs returns the count of all frames (raw depth).
* Make String#rstrip{,!} raise Encoding::CompatibilityError for broken coderangeJeremy Evans2022-11-244-8/+30
| | | | | | | | | | | | | | | | 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]
* [ruby/fileutils] [Feature #18925] Add `ln_sr` method and `relative:` option ↵Nobuyoshi Nakada2022-11-252-4/+138
| | | | | | to `ln_s` https://github.com/ruby/fileutils/commit/5116088d5c
* Use `rb_sprintf` instead of deprecated `sprintf`Nobuyoshi Nakada2022-11-253-24/+26
|
* [ruby/erb] Allow requiring erb/escape.so aloneTakashi Kokubun2022-11-241-4/+7
| | | | | | (https://github.com/ruby/erb/pull/37) Prior to this commit, requiring erb/escape first and then requiring erb did not work as expected.
* [ruby/erb] Split erb.rb into files for each module under ERBTakashi Kokubun2022-11-245-580/+570
| | | | | | (https://github.com/ruby/erb/pull/36) https://github.com/ruby/erb/commit/f74833cc07
* [ruby/erb] Rename erb.so to erb/escape.soTakashi Kokubun2022-11-245-5/+5
| | | | | | (https://github.com/ruby/erb/pull/35) https://github.com/ruby/erb/commit/1280046952
* Raise TypeError for endless non-numeric range include?Jeremy Evans2022-11-242-17/+43
| | | | | | | | | | | | | | | | Beginless ranges previously raised TypeError for this case, except for string ranges, which had unexpected behavior: ('a'..'z').include?('ww') # false (..'z').include?('ww') # previously true, now TypeError Use of include? with endless ranges could previously result in an infinite loop. This splits off a range_string_cover_internal function from range_include_internal. Fixes [Bug #18580]
* Add a NEWS entry about erb -S removal [ci skip]Takashi Kokubun2022-11-241-1/+3
|
* [ruby/erb] Drop deprecated -S option from erb commandTakashi Kokubun2022-11-242-24/+1
| | | | | | | | We attempted to remove things like this and reverted all of them, but I think nobody relies on this unlike the positional arguments of `ERB#initialize`. https://github.com/ruby/erb/commit/92fde7e403
* [ruby/erb] Suppress warnings to fix ruby-head CITakashi Kokubun2022-11-241-3/+3
| | | | | | | | | | | | | | | | | | (https://github.com/ruby/erb/pull/34) There seems to be no way to fix this. It doesn't happen in an installed directory, so it's likely a false positive and/or a bug in rubygems. | <internal:/home/runner/.rubies/ruby-head/lib/ruby/3.2.0+3/rubygems/core_ext/kernel_require.rb>:85: warning: <internal:/home/runner/.rubies/ruby-head/lib/ruby/3.2.0+3/rubygems/core_ext/kernel_require.rb>:85: warning: loading in progress, circular require considered harmful - /home/runner/.rubies/ruby-head/lib/ruby/3.2.0+3/bundler/setup.rb | from /home/runner/work/erb/erb/libexec/erb:0:in `require' | from /home/runner/.rubies/ruby-head/lib/ruby/3.2.0+3/bundler/setup.rb:3:in `<top (required)>' | from /home/runner/.rubies/ruby-head/lib/ruby/3.2.0+3/bundler/setup.rb:3:in `require_relative' | from /home/runner/.rubies/ruby-head/lib/ruby/3.2.0+3/bundler/shared_helpers.rb:8:in `<top (required)>' | from /home/runner/.rubies/ruby-head/lib/ruby/3.2.0+3/bundler/shared_helpers.rb:8:in `require_relative' | from /home/runner/.rubies/ruby-head/lib/ruby/3.2.0+3/bundler/rubygems_integration.rb:3:in `<top (required)>' | from /home/runner/.rubies/ruby-head/lib/ruby/3.2.0+3/bundler/rubygems_integration.rb:3:in `require' | from /home/runner/.rubies/ruby-head/lib/ruby/3.2.0+3/rubygems.rb:1352:in `<top (required)>' | from <internal:/home/runner/.rubies/ruby-head/lib/ruby/3.2.0+3/rubygems/core_ext/kernel_require.rb>:85:in `require' | from <internal:/home/runner/.rubies/ruby-head/lib/ruby/3.2.0+3/rubygems/core_ext/kernel_require.rb>:85:in `require'
View Lorry Controller Status