[pull] master from ruby:master #380
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![pull[bot]](https://github.com/avatars/in/12910?s=60&v=4){kind=small}
Do not read STDIN as a String instance.
`.bundle/specification/foo-x.y.z.gemspec` may be changed our toolchain
The current build system uses runtime dependencies from only `.bundle` directory. We shouldn't install runtime dependencies from rubygems.org when `make test-bundled-gems` is invoked.
to it (ruby/irb#856) * Test IRB's behaviour with empty input * Handle empty input and pass it to debugger Since `rdbg` accepts empty input to repeat the previous command, IRB should take empty input in `irb:rdbg` sessions and pass them to the debugger. Currently, IRB simply ignores empty input and does nothing. This commit creates `EmptyInput` to represent empty input so it can fit into the current IRB's input processing flow in `Irb#eval_input`. ruby/irb@0e9db419be
(ruby/irb#873) * Replace ExtendCommand with Command and standardize command related names 1. Rename lib/irb/extend-command.rb to lib/irb/command.rb 2. Rename lib/irb/cmd/*.rb to lib/irb/command/*.rb 3. Rename test/irb/test_cmd.rb to test/irb/test_command.rb 4. Rename ExtendCommand to Command * Alias ExtendCommand to Command and deprecate it * Rename Command::Nop to Command::Base * Not deprecate old constants just yet * Add lib/irb/cmd/nop.rb back ruby/irb@462c1284af
rubyspec seems very slow or getting stuck on s390-linux. https://app.travis-ci.com/github/ruby/ruby/jobs/617916019 No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself.
Fix the error with the working directory in the result job in some GitHub Actions YAML files. I hit this error on my forked repository below. https://github.com/junaruga/ruby/actions/runs/7921897724/job/21628462038?pr=2#step:2:11 ``` Error: An error occurred trying to start process '/bin/bash' with working directory '/Users/runner/work/ruby/ruby/build'. No such file or directory ```
Using RSTRING_PTR can cause the string object to not exist on the stack, which could cause it to be GC'd or be moved by GC compaction. This can cause RSTRING_PTR to point to the incorrect location if the string is embedded and moved by GC compaction. Fixes ruby/prism#2442.
This adds YJIT support for VM_CALL_KW_SPLAT with nil, specifically for when we already know from the context that it's done with a nil. This is enough to support forwarding with `...` when there no keyword arguments are present. Amend the kw_rest support to propagate the type of the parameter to help with this. Test interactions with splat, since the splat array sits lower on the stack when a kw_splat argument is present.
Also remove RBS for currently ignored files. Will follow-up when those check fully in later PRs. ruby/prism@2cae58f86d
When running_iseq happens to be 0, it's better to fail on the assertion rather than referencing the null pointer.
(ruby/reline#637) I think this has a few benefits: 1. Most terminal themes generally don't change or pick similar colors for their black and white colors, so it's more likely to be consistent across terminals/themes. 2. They don't have the potential color-blind issues that other color options may have. 3. We won't need additional changes for no color mode. ruby/reline@6579a0a737
- Redirect `git ls-files` without shelling out. - When building by `gem`, `__FILE__` is the path name given in the command line, or the gemspec file name in the current directory. In that case, comparison it and expanded path never equal. Compare listed file names with the base name of `__FILE__` instead. ruby/tmpdir@f505e3f7cb
It is only for old commits, useless without full repository logs.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot]
Can you help keep this open source service alive? 💖 Please sponsor : )