aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Added condition for ruby/ruby repositoryHiroshi SHIBATA2022-12-091-1/+5
|
* Merge syntax_suggest masterHiroshi SHIBATA2022-12-093-52/+79
| | | | Pick from https://github.com/ruby/syntax_suggest/commit/daee74dcb06296fa69fe8595fdff5d93d432b30d
* Merge net-protocol-0.2.1Hiroshi SHIBATA2022-12-092-0/+9
|
* Merge RDoc-6.5.0Hiroshi SHIBATA2022-12-092-86/+132
|
* Merge RubyGems/Bundler masterHiroshi SHIBATA2022-12-0922-158/+420
| | | | Pick from https://github.com/rubygems/rubygems/commit/823c776d951f3c35094611473ec77f94e8bf6610
* Merge Psych-5.0.1Hiroshi SHIBATA2022-12-093-0/+21
|
* Merge yaml-0.2.1Hiroshi SHIBATA2022-12-091-1/+1
|
* Merge json-2.6.3Hiroshi SHIBATA2022-12-092-2/+2
|
* Merge stringio-3.0.4Hiroshi SHIBATA2022-12-091-21/+21
|
* Merge fiddle-1.1.1Hiroshi SHIBATA2022-12-093-1/+32
|
* Merge strscan-3.0.5Hiroshi SHIBATA2022-12-095-15/+117
|
* Reapply the following commits related to extend timeout value.Hiroshi SHIBATA2022-12-091-1/+8
| | | | | | | | 66d1900423e6fb9774c2fe72dba8c2968b54d7ab 0686e4181d04dd911316a227753ceaa96d8c6533 1a63468831524f68e73cbb068071652c6486cfc6 e1fee7f949cb6719122672fa1081c60984a5339f 232e43fd52e53f667c2c290cffb4afa524889f0f
* Merge csv-3.2.6Hiroshi SHIBATA2022-12-0920-415/+1749
|
* MJIT: Refactor JIT failure handlingTakashi Kokubun2022-12-081-4/+4
|
* MJIT: Add comments about custom hooks [ci skip]Takashi Kokubun2022-12-081-2/+2
|
* MJIT: Give a more appropriate name to the initial stateTakashi Kokubun2022-12-082-6/+6
|
* MJIT: Convert compact_p flag to an enumTakashi Kokubun2022-12-083-27/+45
| | | | I'm gonna add another type of unit shortly.
* MJIT: Drop an obsoleted explanation [ci skip]Takashi Kokubun2022-12-082-2/+2
| | | | There's no MJIT worker thread anymore
* Use a ruby-lang alias [ci skip]Takashi Kokubun2022-12-084-6/+8
|
* [ruby/rdoc] Fix `=end` delimiterNobuyoshi Nakada2022-12-091-1/+1
| | | | https://github.com/ruby/rdoc/commit/e1679fa7e4
* [ruby/rdoc] Non-RD part feature has not been imported to RDocNobuyoshi Nakada2022-12-091-0/+7
| | | | https://github.com/ruby/rdoc/commit/fe0159de2f
* [ruby/rdoc] Use TempfileNobuyoshi Nakada2022-12-091-8/+1
| | | | https://github.com/ruby/rdoc/commit/0b9dde5ab4
* [ruby/erb] Use a ruby-lang alias on spec.emailTakashi Kokubun2022-12-091-1/+1
| | | | https://github.com/ruby/erb/commit/39414f32a5
* Update default gems list at d7baa17b49a681a7436718f6219fcb [ci skip]git2022-12-091-1/+1
|
* [ruby/etc] Bump version to 1.4.2Hiroshi SHIBATA2022-12-091-1/+1
| | | | https://github.com/ruby/etc/commit/5cac138538
* MJIT: Remove obsoleted conditional variablesTakashi Kokubun2022-12-081-24/+0
|
* Update default gems list at 95b423f93a418abc010d7bc1baab48 [ci skip]git2022-12-091-1/+1
|
* [ruby/irb] Version 1.6.0Takashi Kokubun2022-12-091-1/+1
| | | | https://github.com/ruby/irb/commit/d799c5c9da
* Fix bad code example in documentationJanosch Müller2022-12-091-1/+1
|
* YJIT: Upgrade bindgen to stabilize and reduce outputAlan Wu2022-12-084-561/+159
| | | | | | | | | The new version has an option to merge everything into a big `extern "C"` block and it's nicer. More importantly, this upgrade fixes an issue where Ubuntu with Clang 12 and macOS with Clang 14 gave a one line diff for `rb_shape_t`. It was slightly annoying because we use macOS locally.
* YJIT: Drop Copy trait from Context (#6889)Takashi Kokubun2022-12-082-19/+19
|
* YJIT: implement opt_newarray_min YARV instruction (#6888)Maxime Chevalier-Boisvert2022-12-082-0/+43
|
* [ruby/irb] Add show_doc as an alias to the help commandStan Lo2022-12-082-9/+12
| | | | | | | | | | (https://github.com/ruby/irb/pull/475) In the long-term, we want to align with `Pry`, `byebug` and `debug` to use the `help` command to list all commands, which is what `show_cmds` currently does. And `show_doc` will be the command to look up Ruby APIs. By aliasing `show_doc` to the current `help` now, users will have time to get use to it.
* [ruby/irb] Gracefully handle missing command argumentStan Lo2022-12-084-14/+42
| | | | | | | | | | | | | | | | | (https://github.com/ruby/irb/pull/473) * Handle file loading commands' argument error gracefully Currently, if users don't provide an argument to `source`, `irb_load`, and `irb_require`, IRB raises `ArgumentError` with full stacktrace. This is confusing because it looks similar to when IRB has internal issues. The message also isn't helpful on helping users avoid the error. So in this commit, I add a new `CommandArgumentError` for commands to raise explicitly when users' input doesn't satisfy a command's argument requirement. * Gracefully handle `fg` command's argument requirement
* Update default gems list at 8bbf4e5d8dccba3adf07fb56a38c06 [ci skip]git2022-12-081-1/+1
|
* [ruby/stringio] bump up to 3.0.5Sutou Kouhei2022-12-081-1/+1
| | | | https://github.com/ruby/stringio/commit/e62b9d78d3
* Freeze singleton class, not its originAlan Wu2022-12-082-1/+14
| | | | | | | | | | | | | Previously, when we froze an object, we froze `RCLASS_ORIGIN(object.singleton_class)`, which didn't freeze `object.singleton_class` when it has some prepended modules. Origin iclass are internal objects and users can't interact with them through Kernel#freeze?, Kernel#freeze, or any mutation method that checks the frozen status. So we shouldn't touch the origin iclasses when the frozen status should be visible. [Bug #19169]
* YJIT: Fold check-yjit-bindings into yjit-bindgenAlan Wu2022-12-082-5/+2
| | | | | So it's shorter on CI and the hint about how the fix the failure shows up. It's going to print a diff locally too, but that should be fine.
* YJIT: Add a hint for fixing "check-yjit-bindings"Alan Wu2022-12-081-0/+1
| | | | | | This makes it clear what to do when the CI check fails and should remove a few minutes of confusion for people seeing this for the first time.
* [ruby/irb] Kill PTY process after test is finishedStan Lo2022-12-081-1/+33
| | | | | | | (https://github.com/ruby/irb/pull/471) The killing/waiting logic is borrowed from ruby/debug: https://github.com/ruby/debug/blob/ec5ae5aebd61a99dc84028d8dffa8e7e165c1ec6/test/support/test_case.rb#L107-L136
* [ruby/irb] Add "show_cmds" command to list all commands'Stan Lo2022-12-0825-17/+182
| | | | | | | descriptions (https://github.com/ruby/irb/pull/463) https://github.com/ruby/irb/commit/7e857655ac
* MJIT: Mark MJIT's objects from mjit_markTakashi Kokubun2022-12-081-2/+5
| | | | | It looks like the current way of marking objects was breaking eightbitraptor's upcoming VWA changes and this seems to fix it.
* ObjectSpace.dump_all: dump shapes as wellJean Boussier2022-12-087-40/+248
| | | | | | | | | | | | | | | | | | | | | | | | | I see several arguments in doing so. First they use a non trivial amount of memory, so for various memory profiling/mapping tools it is relevant to have visibility of the space occupied by shapes. Then, some pathological code can create a tons of shape, so it is valuable to have a way to have a way to observe shapes without having to compile Ruby with `SHAPE_DEBUG=1`. And additionally it's likely much faster to dump then this way than to use `RubyVM::Shape`. There are however a few open questions: - Shapes can't respect the `since:` argument. Not sure what to do when it is provided. Would probably make sense to not dump them. - Maybe it would make more sense to have a separate `ObjectSpace.dump_shapes`? - Maybe instead `dump_all` should take a `shapes: false` argument? Additionally, `ObjectSpace.dump_shapes` is added for the use case of debugging the evolution of the shape tree.
* Use the built bundled gems in test-all as well as test-bundled-gemsNobuyoshi Nakada2022-12-091-5/+7
|
* [DOC] Update `rb_gc_mark_locations` docJimmy Bourassa2022-12-091-1/+1
| | | | The documentation says that the `end` pointer will be marked but looking at the source, that is not the case.
* Ignore .o.tmp filesJean Boussier2022-12-081-0/+1
|
* [ruby/net-protocol] Failing test case for #19Jean Boussier2022-12-081-0/+29
| | | | | | | | | Unfortunately we have to use a mock, but this test demonstrate the mutation bug fixed in #19. It fails on 0.2.0 but passes on 0.1.3 or 0.2.1. https://github.com/ruby/net-protocol/commit/40a1ab687c
* Update default gems list at 6f44dc8edf5b444a45ea9f0a375a26 [ci skip]git2022-12-081-1/+1
|
* [ruby/net-protocol] Bump version to 0.2.1Hiroshi SHIBATA2022-12-081-1/+1
| | | | https://github.com/ruby/net-protocol/commit/06d1420936
* [ruby/net-protocol] Undo BufferedIO#rbuf_consume_all_shareable! optimizationJean Boussier2022-12-081-14/+4
| | | | | | | | | | | | | | | This optimization is unsafe because `dest` is allowed to be a custom object responding to `<<` (e.g. a block wrapped in `ReadAdapter`). So the receiver can hold onto the passed buffer for as long as it wants. If it was guaranteed that `ReadAdapter` was the only possible receiver we could dup the buffer there for mutation safety, but I'm not certain it's the case so I'd rather err on the safe side. Ref: https://github.com/shrinerb/shrine/issues/610 https://github.com/ruby/net-protocol/commit/7efa16d55d
generated by cgit v1.2.3 (git 2.39.1) at 2024-10-01 05:01:53 +0000