summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2023-12-13[ruby/prism] fix typo in docsAlex Koval
https://github.com/ruby/prism/commit/d7fbc09345
2023-12-13[ruby/irb] Warn and do nothing if block is passed to measure commandtomoya ishida
(https://github.com/ruby/irb/pull/813) https://github.com/ruby/irb/commit/e79a90a1e6
2023-12-13We need only one line for detecting caller gem nameHiroshi SHIBATA
2023-12-13Avoid warning --jit when only YJIT is enabledTakashi Kokubun
2023-12-12Fix a typo for `RJIT_TARGET_OK` (#8222)Nobuyoshi Nakada
2023-12-12Skip a GC test for RJITTakashi Kokubun
It randomly fails like this: https://github.com/ruby/ruby/actions/runs/7191443542/job/19586164973
2023-12-13Update default gems list at 5f5f8dbbb6a7861e9c591ad0914994 [ci skip]git
2023-12-13[ruby/resolv] Bump up 0.3.0Hiroshi SHIBATA
https://github.com/ruby/resolv/commit/22153c2a45
2023-12-13Update default gems list at 39023792dbded9250040224accda18 [ci skip]git
2023-12-13[ruby/io-console] Bump up 0.7.0Hiroshi SHIBATA
https://github.com/ruby/io-console/commit/3e5586e632
2023-12-13Update default gems list at 06edde22f462f736c16ae9038b015f [ci skip]git
2023-12-13[ruby/io-nonblock] Bump up 0.3.0Hiroshi SHIBATA
https://github.com/ruby/io-nonblock/commit/501e2ffea3
2023-12-13Update default gems list at 5cabe1e9cc6829d1918c65bf29c4ba [ci skip]git
2023-12-13[ruby/io-wait] Bump up 0.3.1Hiroshi SHIBATA
https://github.com/ruby/io-wait/commit/5ec3db36c8
2023-12-13Update default gems list at 12c775c94249b57dadfda0c2de9568 [ci skip]git
2023-12-13[ruby/etc] Bump up 1.4.3Hiroshi SHIBATA
https://github.com/ruby/etc/commit/743c26086d
2023-12-13[rubygems/rubygems] Improve default gem handlingDavid Rodríguez
If a gem is specified in the Gemfile (or resolved as a transitive dependency), it's always resolved from remote/installed sources. Default gems are only used as a fallback for gems not included in the bundle. I believe this leads to more consistent behavior and more portable apps, since all gems will be installed to the configured bundle path, regardless of whether they are default gems or not. https://github.com/rubygems/rubygems/commit/091b4fcf2b
2023-12-13[rubygems/rubygems] Refactor `bundle info`David Rodríguez
https://github.com/rubygems/rubygems/commit/0e919eaa87
2023-12-13[rubygems/rubygems] Remove dead codeDavid Rodríguez
https://github.com/rubygems/rubygems/commit/fad186df39
2023-12-13Normalize bundler bindirDavid Rodríguez
This makes bundler consistent with all other gems, and makes the default installation of Bundler in the release package look like any other bundler installation. Before (on preview3, for example), Bundler executable is installed at: lib/ruby/gems/3.3.0+0/gems/bundler-2.5.0.dev/libexec/bundle Now it's installed in the standard location: lib/ruby/gems/3.3.0+0/gems/bundler-2.5.0.dev/exe/bundle
2023-12-13RubyGems 3.5+ will use vendored net-httpHiroshi SHIBATA
2023-12-13Removed duplicated LICENSE fileHiroshi SHIBATA
2023-12-13[rubygems/rubygems] Explain the 3 states `options[:user_install]` can have.Vít Ondruch
This was issue previously, so hopefully this comment tries to state this explicitly for future readers. https://github.com/rubygems/rubygems/commit/8ccd830f85
2023-12-13[rubygems/rubygems] Test if the user dir is used for auto user installationVít Ondruch
This is mainly to align this test case with the `test_process_options_does_not_fallback_to_user_install_when_gem_home_ not_writable_and_no_user_install`, where the `install_dir` is checked already. https://github.com/rubygems/rubygems/commit/02b1884b61
2023-12-13[rubygems/rubygems] Make sure `--no-user-install` is respected for auto user ↵Vít Ondruch
installation The `options[:user_install]` might have three states: * `true`: `--user-install` * `false`: `--no-user-install` and * `nil`: option was not specified However, this had not been respected previously and the `false` and `nil` were treated the same. This could lead to auto user installation despite `--no-user-install` being specified on the command line. Fixes https://github.com/rubygems/rubygems/pull/7237 https://github.com/rubygems/rubygems/commit/9281545474
2023-12-13[rubygems/rubygems] Add a spec to cover what vendoring timeout fixesDavid Rodríguez
https://github.com/rubygems/rubygems/commit/2662e45d75
2023-12-13[rubygems/rubygems] Remove no longer needed gem install during testDavid Rodríguez
https://github.com/rubygems/rubygems/commit/bdb78d8289
2023-12-13[rubygems/rubygems] Resolv needs vendoring tooDavid Rodríguez
https://github.com/rubygems/rubygems/commit/cdfc6923e4
2023-12-13[rubygems/rubygems] Use vendored timeout from RubyGemsDavid Rodríguez
https://github.com/rubygems/rubygems/commit/cfc5018c54
2023-12-13[rubygems/rubygems] Vendor timeout in RubyGems tooDavid Rodríguez
https://github.com/rubygems/rubygems/commit/e2e7440ede
2023-12-13[rubygems/rubygems] Use vendored net-http in BundlerDavid Rodríguez
https://github.com/rubygems/rubygems/commit/0d758e8926
2023-12-13[rubygems/rubygems] Vendor net-http and net-protocol in RubyGemsDavid Rodríguez
https://github.com/rubygems/rubygems/commit/99d91c9ed2
2023-12-13[rubygems/rubygems] Avoid loading artifice when not necessaryDavid Rodríguez
https://github.com/rubygems/rubygems/commit/ef97ad37bd
2023-12-13[rubygems/rubygems] Load hax.rb before anything when ↵David Rodríguez
`BUNDLER_IGNORE_DEFAULT_GEM` set https://github.com/rubygems/rubygems/commit/111bd11c36
2023-12-13[rubygems/rubygems] Require `rubygems/request` where it's usedDavid Rodríguez
https://github.com/rubygems/rubygems/commit/73b9498658
2023-12-12[PRISM] Correctly parse non-base 10 integers in PrismJemma Issroff
This commit passes an `end` to rb_int_parse_cstr which allows us to correctly parse non-base 10 integers which are enclosed in parenthesis. Prior to this commit, we were getting a putobject nil when compiling `(0o0)` for example.
2023-12-13Add changelog entry for [Feature #20057]KJ Tsanaktsidis
2023-12-13Add a test case for preregistering with different dataKJ Tsanaktsidis
We want to make sure that if preregister is called with different data, that the postponed job table is updated.
2023-12-13Simplify implementation of tracepoint testsKJ Tsanaktsidis
With the latest version of the postponed job patchset merged, we don't actually need to go through the contortions of keeping the data in a global variable; we can just update `data` with multiple calls to rb_postponed_job_preregister.
2023-12-13Refactor local variable names in postponed_job methodsKJ Tsanaktsidis
Just removes the unneeded `prereg_` prefix from a few local var names.
2023-12-13Small doc improvements for rb_postponed_job APIKJ Tsanaktsidis
2023-12-13[ruby/prism] Fix hash deopt based on contentsUfuk Kayserilioglu
The previous implementation of hash deopt was based on clearing the static literal flag on a hash node if the element that was being added was an array, hash or range node, or if the element was not a static literal in the first place. However, this is not correct. First of all, the elements added to a hash node will primarily be assoc nodes, but never array, hash or range nodes. Secondly, the static literal flag is set on assoc nodes, only if the value in an assoc node is a static literal, so the key is never checked. As a result, the static literal flag on a hash node would never be cleared if the key wasn't a static literal. This commit fixes this by clearing the static literal flag if: 1. the element is not an assoc node, 2. the element is an assoc node, but the key is not a static literal, or 3. the element is an assoc node, the key is a static literal, but assoc node (and thus the value in assoc node) is not a static literal. https://github.com/ruby/prism/commit/7f67109b36
2023-12-12Use xfree for IO::BufferPeter Zhu
Since IO::Buffer is allocated using TypedData_Make_Struct, it must use xfree to free the buffer otherwise it will cause more major GC to run. Example: ``` 10.times do 1_000_000.times { IO::Buffer.new(0) } puts "oldmalloc_increase_bytes: #{GC.stat(:oldmalloc_increase_bytes)}, major_gc_count: #{GC.stat(:major_gc_count)}" end ``` Before: ``` oldmalloc_increase_bytes: 14904176, major_gc_count: 3 oldmalloc_increase_bytes: 2399424, major_gc_count: 5 oldmalloc_increase_bytes: 5204640, major_gc_count: 6 oldmalloc_increase_bytes: 2199936, major_gc_count: 7 oldmalloc_increase_bytes: 34199936, major_gc_count: 7 oldmalloc_increase_bytes: 24223360, major_gc_count: 8 oldmalloc_increase_bytes: 5967616, major_gc_count: 9 oldmalloc_increase_bytes: 37967616, major_gc_count: 9 oldmalloc_increase_bytes: 9689792, major_gc_count: 10 oldmalloc_increase_bytes: 41689792, major_gc_count: 10 ``` After: ``` oldmalloc_increase_bytes: 117392, major_gc_count: 2 oldmalloc_increase_bytes: 26128, major_gc_count: 2 oldmalloc_increase_bytes: 71600, major_gc_count: 2 oldmalloc_increase_bytes: 117072, major_gc_count: 2 oldmalloc_increase_bytes: 17296, major_gc_count: 2 oldmalloc_increase_bytes: 62768, major_gc_count: 2 oldmalloc_increase_bytes: 108240, major_gc_count: 2 oldmalloc_increase_bytes: 153712, major_gc_count: 2 oldmalloc_increase_bytes: 53936, major_gc_count: 2 oldmalloc_increase_bytes: 99408, major_gc_count: 2 ```
2023-12-12[DOC] RDoc for ComplexBurdetteLamar
2023-12-12Remove unused macrosAlan Wu
2023-12-12YJIT: Fix off-by-one in Kernel#send type handling (#9212)Alan Wu
Previously, if the method ID argument happens to be on one below the top of the stack, we didn't overwrite the type of the stack slot, which leaves an incorrect type for the stack slot. The included script tripped asserts both with and without --yjit-verify-ctx.
2023-12-12Move --repeat-count=2 job to macos-arm-oss (#9208)Takashi Kokubun
2023-12-12[PRISM] Fix segv with regex once flageileencodes
When you have an interpolated regex with a `once` flag and local variable is outside the block created by the `once` flag, Prism would see a segv. This is because it was not taking the depth into account. To fix this, we need to add 1 to the `local_depth_offset` on the `scope`. Fixes: ruby/prism#2047
2023-12-12Sync with upstream rubygems (#9206)David Rodríguez
2023-12-12Remove a duplicated jobTakashi Kokubun
This was first added in b481b673d75, but 197e91f357 added -DUNIVERSAL_PARSER to the Compilers workflow as well. Given the nature of this test and the fact that it also runs make test-all besides make test, I think it's better to keep only the Compilers one.
generated by cgit v1.2.3 (git 2.25.1) at 2026-05-14 16:30:08 +0000