Activity
From 12/25/2023 to 12/31/2023
12/31/2023
-
03:55 PM Revision a19544d1 (git): [DOC] Fix markup
-
-
-
- https://github.com/ruby/rdoc/commit/914a6af137
-
- https://github.com/ruby/win32ole/commit/76acc979bf
-
- https://github.com/ruby/win32ole/commit/afceb6814f
-
05:06 AM Misc #17815 (Closed): Snapcraft Ruby plugin
-
01:20 AM Misc #17815: Snapcraft Ruby plugin
- This can be closed. I've implemented a Ruby build plugin on v1 and v2.
-
03:13 AM Revision 0d2ca334 (git): [DOC] Fix link to untrace_var from trace_var
-
- https://github.com/ruby/win32ole/commit/eba2934177
12/30/2023
-
05:57 PM Bug #20104: Regexp#match returns nil but allocates T_MATCH objects
- So I looked into this and it's this commit that introduces that behavior: 7193b404a1a56e50f8046d0382914907020c1559
Edit: create PR here https://github.com/ruby/ruby/pull/9398. I should probably add test for this, I'm just seeing if CI p... -
- Between Ruby 3.2 and 3.3, behavior changed so that Regexp#match will allocate a T_MATCH object even when there is no match. Example code:
```ruby
h = {}
GC.start
GC.disable
ObjectSpace.count_objects(h)
matches = h[:T_MATCH] || 0... -
- This should help in debugging the intermittent test failures on CI:
TestProcess#test_warmup_frees_pages [test/ruby/test_process.rb:2779]:
<201> expected but was
<202>.
12/29/2023
-
- I was able to reproduce the segfault in ruby 3.3.0 (2023-12-25 revision 5124f9ac75) [x86_64-linux] on the same file and line. I didn't try earlier rubies, just this one. However, when I downloaded all the ubuntu packages that were outlin...
-
- I created a PR that updates the Ractor docs: https://github.com/ruby/ruby/pull/9395. It doesn't go into much detail about the situation but clarifies it a bit.
Adding a `movable?` method would have have to be a separate ticket @fortho... -
- The documentation was indented one level too deep, which causes RDoc to
generate it all as a code block. -
-
- This has been fixed by @ko1 in 7718e9588b4d7d83c8f9a89dce10b06b9f97bddb, it can be closed now. It could possibly use a backport, but I'll leave that up to you guys. Thank you!
-
- https://github.com/ruby/securerandom/commit/647e5f0af8
-
04:08 PM Revision 2571d537 (git): Reduce `if` for decreasing counter on OP_REPEAT_INC (#9393)
- This commit also reduces the warning `'stkp' may be used
uninitialized in this function`. -
-
-
-
-
09:32 AM Revision 1ade170a (git): Introduce NODE_LINE
- `__LINE__` was managed by `NODE_LIT` with `Integer` object.
This commit introduces `NODE_LINE` so that
1. `__LINE__` is detectable from AST Node
2. Reduce dependency ruby object -
08:23 AM Revision 6f33e3c5 (git): [ruby/reline] Revert kill_ring.rb file permission
- (https://github.com/ruby/reline/pull/623)
https://github.com/ruby/reline/commit/38e9cb2899 -
05:50 AM Feature #20093: Syntax or keyword to reopen existing classs/modules, never to define new classs/modules
- > The only downside I see is that doesn't make it easy to define and access constants defined under that class/module.
> ...
I actually found this quite surprising:
```
irb(main):008> String.class_eval { Module.nesting }
=> []
irb... -
05:28 AM Feature #20093: Syntax or keyword to reopen existing classs/modules, never to define new classs/modules
- I commented that "class_eval / module_eval can do the same things functionally.". However, as @Eregon pointed out, there is a different rule about constants around `class_eval` / `module_eval`.
The method definition in `class_eval`/`mod... -
01:11 AM Feature #20093: Syntax or keyword to reopen existing classs/modules, never to define new classs/modules
- Why a new keyword? If it behaves like a `class_eval`, could it be an alias?
```rb
String.reopen do
def stuff = here
end
``` - 04:05 AM Revision bc3b9356 (git): [ruby/reline] Replace `object_id` comparison with `equal?`
- (https://github.com/ruby/reline/pull/617)
https://github.com/ruby/reline/commit/63deef4ae5 - 02:43 AM Revision e86b4c29 (git): [ruby/securerandom] Increase speed of UUID generation
- https://github.com/ruby/securerandom/commit/b587b8c7cb
12/28/2023
-
- Fixed by commit:bc002971b6ad483dbf69b8a275c44412bb6ab954
-
-
- Fixed by commit:c452fe17ac679b4171c7de4f4004d61790828ba8
-
-
03:24 PM Bug #20085: Fiber.new{ }.resume causes Segmentation fault for Ruby 3.3.0 on aarch64-linux
- @naruse For the record, the fix is already merged into the master by https://github.com/ruby/ruby/pull/9371
-
02:47 PM Bug #20085: Fiber.new{ }.resume causes Segmentation fault for Ruby 3.3.0 on aarch64-linux
- @katei Since Backport field is correctly specified, I'll merge it for 3.3.1 after the fix is merged into master.
-
- Opened a backport PR https://github.com/ruby/ruby/pull/9385
@naruse Can we backport the patch to 3.3 branch?
- Short description: `Fiber` on aarch64 with PAC support on Linux was broken in 3.3.0. The patch fixes the issue by adjus... -
09:20 PM Feature #13821: Allow fibers to be resumed across threads
- > This proposal breaks Fiber semantics so fundamentally
I don't disagree with you, and I don't have a strong opinion one way or another, but there is nothing about coroutine semantics which prevents them from being passed between thre... -
01:05 PM Feature #13821: Allow fibers to be resumed across threads
- bascule (Tony Arcieri) wrote in #note-10:
> There's a simple solution to this: track if a given fiber is holding mutexes (e.g. keep a count of them) and if it is, make Fiber#resume raise an exception if it is resumed in a different thre... -
- One issue was the use of the copy-coroutine. As we've removed this and replaced it with a pthread fallback, we can now potentially allow fibers to be resumed across threads. I'll put together a PR so we can experiment.
-
- Not same. https://bugs.ruby-lang.org/issues/20083 is fixed in master branch. This issue is found in a branch that fixes 20083.
-
02:56 PM Bug #20098: Wrong regexp match in ruby 3.2 and 3.3
- Same as https://bugs.ruby-lang.org/issues/20083?
-
- Not same. https://bugs.ruby-lang.org/issues/20083 is related to regexp optimization from ruby 3.2.
This issue is not because it's same result in older ruby version 3.0 and 3.1
-
- Same as https://bugs.ruby-lang.org/issues/20083?
- 04:58 PM Revision 2b967376 (git): Fix use of the rb_profile_frames start parameter
- Previously, it was decrementing the start argument until it reached
zero without actually changing the control frame pointer.
[Bug #14607] -
03:57 PM Bug #20089: Fiber#kill transfers to root fiber
- That definitely makes sense for a Fiber killing _itself_, but would you say that killing a _different_ Fiber should cause a fiber to transfer away? In my first script above, calling `worker.kill` causes the `manager` fiber to transfer.
... -
-
02:09 PM Feature #15667: Introduce malloc_trim(0) in full gc cycles
- It looks like this ticket can be closed. I see that Ruby 3.3 makes use of malloc_trim.
-
03:46 PM Bug #20103 (Open): rb_internal_thread_remove_event_hook() hangs when called from within a Thread hook
- ## Problem
The Ruby process hangs when `rb_internal_thread_remove_event_hook()` is called from within a Thread hook registered by `rb_internal_thread_add_event_hook()`.
The thread is waiting for the thread event execution lock (`pthr... -
- Same as https://bugs.ruby-lang.org/issues/20083?
-
- * Remove debugging code
* Fix path to github-pr-info.txt, which is used when labeled before
build completes
* Add a check to skip the build if the build is completed but the PR is
not labeled with Playground -
02:33 PM Revision 0990270c (git): [DOC] Add What's Here for Complex (#9366)
-
-
-
- * [Feature #20102] Introduce `Fiber#resuming?`
* Can we introduce?
* [Feature #19057] Hide implementation of `rb_io_t`.
* Eric has agreed to release updated gems. Can we continue to move forward?
* [Bug #19857] Eval coverage is reset... -
-
- This is implemented for `Fiber#storage` in Ruby 3.3.
I'll consider expanding it to Thread and Fiber locals as it was agreed on but has a bigger blast radius. -
- There is a PR here that mostly just works: https://github.com/ruby/ruby/pull/4879
However, additional work would be required to:
1. Tidy up the implementation and
2. Mark some core classes as Immutable as outlined in https://gist.... -
- There are some tricky edge cases when using `Fibre#raise` and `Fiber#kill`, e.g.
```ruby
fiber = nil
killer = Fiber.new do
fiber.raise("Stop")
end
fiber = Fiber.new do
killer.resume
end
fiber.resume
# 4:in `raise': ... -
-
- Fixed by merging https://github.com/ruby/ruby/pull/9381. I'll mark this to be backported to 3.2 as well.
-
- > I agree about REG_MULTI_SZ - from checking the documentation of https://learn.microsoft.com/en-us/windows/win32/api/winreg/nf-winreg-regsetvalueexw:
> ...
OK, great, thank you.
> Sorry, I am not set up for git pull requests in my ... -
05:57 AM Bug #20096: Ruby 3.2.2 win32/registry: Junk appended to Windows Registry String Value
- I agree about REG_MULTI_SZ - from checking the documentation of https://learn.microsoft.com/en-us/windows/win32/api/winreg/nf-winreg-regsetvalueexw:
With the REG_MULTI_SZ data type, the string must be terminated with two null character... -
- Thank you for your report. Your diagnosis looks right, this probably is a memory overread. Your patch looks reasonable - are you able to open this as a Github pull request?
Also, are you familiar with `REG_MULTI_SZ`? To my quick glanc... - 07:03 AM Revision 051a8743 (git): Fix memory overread in registry.rb
- The terminator is not actually getting filled in; we're simply passing
(two) bytes of empty memory as the NUL terminator. This can lead to
garbage characters getting written to registry values.
Fix this by explicitly putting a WCHAR_NUL... -
-
-
- I opened a PR for this: https://github.com/ruby/ruby/pull/9380
-
- When opening a file with `File.open`, as long as `'b'` is not set in the mode, Ruby will perform CRLF -> LF conversion on Windows when reading text files - i.e. CRLF line endings on disk get converted to Ruby strings with only "\n" in th...
-
-
- We need to use the same options for both C compiler and assembler
when `-mbranch-protection` is guessed by configure. Otherwise,
`coroutine/arm64/Context.{h,S}` will use incompatible PAC strategies. -
02:05 AM Bug #19442: Remove USE_RINCGC flag
- These kind of flags are provided to measure the impact with on/off the features.
We can simulate them with parameters, but we can not avoid overhead of write barriers completely, for example.
Anyway it was gone. -
- 12:07 AM Revision 1f1edeef (git): [ruby/pathname] require fileutils in both methods using it
- rmtree is already requiring fileutils, but mkpath apparently relies on
autoload of FileUtils. Switch to require for both methods
https://github.com/ruby/pathname/commit/07ad1fb41a -
12/27/2023
-
- In think clarifying the documentation is a good idea.
> And .transfer does return to the caller, as long as the caller is the main Fiber, for example, this prints out a sequence of messages:
I think that's just intuitively correct ... -
- Thanks for taking a look! I was going from the example in the docs (https://docs.ruby-lang.org/en/master/Fiber.html#method-i-transfer), where the return value of `.transfer` is used by the caller.
And `.transfer` _does_ return to the... -
- My initial feeling is that this is not a bug.
Transferring to a fiber is a uni-directional operation and no information is expected to be kept about the caller. If that is what you desire, use resume.
There is nothing that prevents... -
- Transfer is uni-directional and keeps no state about the caller. It's up to the caller to implement its own control flow if preferred. It's a low level operation which must be used more carefully.
```ruby
manager = Fiber.new do
wo... -
- I strongly advise this is backported urgently.
-
08:15 AM Bug #20085: Fiber.new{ }.resume causes Segmentation fault for Ruby 3.3.0 on aarch64-linux
- This issue is fixed by https://github.com/ruby/ruby/pull/9371 in my environment. Thank you @katei san!
-
- I think https://github.com/ruby/ruby/pull/9371 will fix this issue
-
07:30 PM Feature #20100: [Feature] Better / easier support for (optional) colours, on the commandline, in case a parsing error happened? - This is a reasonable feature request. Syntax highlighting helps in easily scanning and parsing code, so having that in the terminal output will help to identify errors and locations faster.
Making this opt-in rather than opt-out seem... -
06:53 PM Feature #20100 (Open): [Feature] Better / easier support for (optional) colours, on the commandline, in case a parsing error happened?
- This suggestion is primarily in regard to (optional) colour support, on the commandline,
in case a parsing error happened. I'll explain what I mean with this in a moment.
Let me first show a partial screenshot (image), to indicate th... -
04:27 PM Bug #20099 (Feedback): Ruby 3.3.0 segfaults on s390x musl libc (Alpine Linux) when built with -O3 (default optflags)
- It does not segfault when I override `optflags` to `-O2` (default is `-O3`).
```
Configuration summary for ruby version 3.3.0
* Installation prefix: /usr
* exec prefix: ${prefix}
* arch: s390x-lin... -
- Makes the call-seq and code more consistent in format.
-
- tagomoris (Satoshi Tagomori) wrote in #note-4:
> I never want to recommend someone to use `class_eval` for monkey patching.
Why not?
For clarity, I mean `class_eval` with a block so there are no syntax highlighting hurdles and no ex... -
02:51 PM Feature #20093: Syntax or keyword to reopen existing classs/modules, never to define new classs/modules
- Just a side note: we actually have a term for "reopen existing class," and it is "refine."
So a bit of "turning the head around," this proposal might be rephrased as "default refinements" (ones that are always activated when some file... - 12:59 PM Feature #20093: Syntax or keyword to reopen existing classs/modules, never to define new classs/modules
- If this feature has the purpose of making class/module extension explicit (meaning you can clearly see that a class/module is being open again to be extended), then I agree with it.
By the way, I think the keyword `open` is more suita... -
- Thank you for your feedback. Yes, `class_eval` / `module_eval` can do the same things functionally. `class extension String` could be a syntax sugar of `String.class_eval do ... end`.
I think it's reasonable to have such a syntax sugar ... -
- Dan0042 wrote:
> I think what you're looking for is class_eval / module_eval
I am not entirely certain tagomoris meant to use **.class_eval** here.
See his alternative suggestion of "reopen".
Of course I may be wrong, but if ... -
03:44 AM Feature #20093: Syntax or keyword to reopen existing classs/modules, never to define new classs/modules
- I think what you're looking for is class_eval / module_eval
```ruby
String.class_eval do
def exclude?(string)
!include?(string)
end
end
``` -
- Would `class extension` just be syntax sugar for this:
```
String.class_eval do
def exclude?(string) = !include?(string)
end
```
or would it behave differently in some way? -
- `class A` and `module B` will reopen existing class A or module B to add/re-define methods if A/B exists. Otherwise, these will define the new class/module A/B.
But, in my opinion, the code of `class A` for patching existing classes doe... -
- These regexp all matches in ruby 3.1.4, but not in ruby 3.3.0.
~~~ruby
p /a((.|.)|bc){,4}z/.match? 'abcbcbcbcz'
p /a(b+?c*){4,5}z/.match? 'abbbccbbbccbcbcz' # matches in ruby 3.2.2
p /a(b+?(.|.)){2,3}z/.match? 'abbbcbbbcbbbcz'
p /a(... -
- hsbt (Hiroshi SHIBATA) wrote in #note-2:
> It's intentional changes. see https://bugs.ruby-lang.org/issues/18797
Thanks.
nobu (Nobuyoshi Nakada) wrote in #note-3:
> ...
Yeah that would be nice. -
- It sometimes matches and sometimes does not, depend on repeat quantifier number.
~~~ruby
# empty capture group repeat
p /(a(){1,4}){2}/.match?('aa') #=> true
p /(a(){1,5}){2}/.match?('aa') #=> false
# repeat of capture group that ... -
-
- https://github.com/ruby/etc/commit/97a4f798d4
-
- The behavior in 3.4.0 is correct.
It was a bug #20090. -
01:26 AM Bug #20092 (Closed): Warnings for anonymous parameters do not display in Ruby 3.4dev
- I encountered no expected warnings in Ruby 3.4dev.
## Reproduction code
```ruby
def anonymous(*, **, &)
rest_block do
foo(*)
end
kwrest_block do
bar(**)
end
block_block do
baz(&)
end
end
```
... -
- https://github.com/ruby/ruby/pull/9373
-
04:51 AM Bug #20094 (Closed): Inline while loop behavior changed unexpectedly in 3.3.0
- The behavior of the inline while loop has changed in 3.3.0. This unexpectedly broke my code and I couldn't find anything in the changelog about it so reporting it as a bug.
In ruby <= 3.2:
``` ruby
(p 1) while false # nothing... -
-
-
-
-
- Ruby Version:
ruby 3.2.2 (2023-03-30 revision e51014f9c0) [x64-mswin64_140]
Compiler: MSVC 2019 - Microsoft (R) C/C++ Optimizing Compiler Version 19.29.30147 for x64.
Issue: win32/registry adds junk to Windows Registry String Value
... -
- https://github.com/ruby/etc/commit/fae932ff61
-
- Multiple regex lookaheads seem to behave strangely in 3.3.0:
```ruby
p "xxx" =~ /(?=.*x)x(?=banana)/ # 2
```
Clearly, the string `xxx` does not contain `banana`, so this regex should never match, but it does. -
-
- 03:11 AM Revision 3d24254b (git): Make sync script work correctly with Windows-style newlines
- I'm almost certain nobody is actually running this script on Windows,
but the tests for it do run during `nmake check`, and they fail at least
on my git configuration.
The $ anchor doesn't match \r\n with git's -E regex matching, so we ... - 01:54 AM Revision dc532b7c (git): Fix WEBrick::TestFileHandler#test_short_filename test not working
- The test is currently skipped and can't possibly work on windows at the
moment. It fails because $LOAD_PATH is not set up properly in the forked
CGI process, so `require 'uri'` fails.
This works properly in the test_cgi.rb tests, becaus... -
01:30 AM Revision 99f8bb13 (git): Fetch tags with test-bundled-gems
- make test-bundled-gems failed when default branch didn't have tag ref at target repository.
```
updating rbs ...
From ssh://github.com/ruby/rbs
- [deleted] (none) -> origin/dependabot/bundl... -
01:26 AM Feature #19982 (Closed): Bump required Visual Studio version to 2015 after 3.3
-
- merged PR 9360.
and also committed 5703cc296a98834a389a6c5d60690c5e4d423f90 -
- I created a PR for this bug (See https://github.com/ruby/ruby/pull/9367).
Thank you for your reporting!
The bug reason is a combination of a regex optimization and a bug for atomic groups.
First, since `\s` and the following `A` (in... - 01:15 AM Revision 5703cc29 (git): Update supported Windows and Visual C++ versions
-
-
- Fixed by commit:596db9c1f486d6609a4e97d82c8c71b54609fb6f
-
12:20 AM Feature #20034: [mkmf] Support creating a compilation database for C language tooling
- I'm the current rake-compiler maintainer.
rake-compiler just runs `extconf.rb` and uses generated `Makefile`. If we do this by rake-compiler, rake-compiler needs to parse `Makefile` or something to generate `compile_commands.json`. It...
12/26/2023
-
11:56 PM Bug #20091 (Closed): Anonymous block method parameters no longer usable within blocks with ruby 3.3
- This used to work on 3.1 and 3.2, but now fails with "anonymous block parameter is also used within block (SyntaxError)":
```
def g = yield
def f(&)
g { g(&) }
end
p f { 123 }
```
And something like this also fails:
... -
-
09:43 PM Revision fac25367 (git): Test_SyncDefaultGems: Fail when editor run (#9365)
- When something went wrong and git launches editor, and a editor chosen
was terminal-based, a test run unnoticeably hangs.
As we intend editors not to be ran with --no-edit, GIT_EDITOR should be
defaulted to `false` so let Git command fa... -
05:57 PM Bug #20090 (Closed): Anonymous arguments are now syntax errors in unambiguous cases
- It looks like the changes that were made in #19370 may have gone further than intended. It's also possible I'm misunderstanding what decision was made. But it was my understanding that the goal was to make ambiguous cases a syntax error....
-
- I was hoping to use `Fiber#kill` to clean up formerly `.transfer`-d Fibers and work around https://bugs.ruby-lang.org/issues/20081, but I found that `Fiber#kill` has a similar control flow jump behavior. Is this on purpose, or a bug?
... -
-
-
- +==+ does not format properly, so we should use <tt>==</tt> instead.
-
03:33 PM Bug #20088 (Closed): Ruby 3.3.0 does not cross-complie on arm64-darwin
- To reproduce:
```shell
docker run -it ghcr.io/rake-compiler/rake-compiler-dock-image:1.4.0.rc2-mri-arm64-darwin bash
cd /tmp
export CPPFLAGS=''
export CFLAGS='-O1 -fno-omit-frame-pointer -fno-fast-math -fstack-protector-strong '
... -
03:12 PM Bug #20087 (Closed): Uninitialized instance variable warning - obsolete documentation
- This warning got removed from Ruby 3.0: https://bugs.ruby-lang.org/issues/17055
But the documentation (ruby/doc/syntax/assignment.rdoc@master) still says:
> An uninitialized instance variable has a value of +nil+. If you run Ruby ... -
- This is currently working as intended but we could consider changing the behaviour. I understand the use case.
-
- I tested Ruby 3.3.0 and it no longer crashes.
```
irb(main):001> ObjectSpace.each_object.to_a
An error occurred when inspecting the object: #<TypeError: uninitialized MatchData>
Result of Kernel#inspect: #<Array:0x0000000106048980>... -
- [Feature #19982]
-
11:42 AM Feature #19908: Update to Unicode 15.1
- @nobu:
We have `Grapheme_Cluster_Break=...`、so I think '=' may be appropriate. But `Grapheme_Cluster_Break=...` uses a long, explicit name. So shouldn't it be `Indic_Cluster_Break=...`, not just `InCB=...`? -
- There is a more serious issue than just whether using an '_' or an '=' in the property: Unicode 15.1 makes some serious changes to grapheme clusters.
Our implementation (function 'node_extended_grapheme_cluster' in regparse.c) is based ... -
- I think we should backport this fix urgently.
-
11:29 AM Bug #20085: Fiber.new{ }.resume causes Segmentation fault for Ruby 3.3.0 on aarch64-linux
- @tomog105, thank you a lot!
I want to confirm that the segfault happens inside Docker Desktop's VM.
On my machine (MacBook Pro M1 Max, Mac OS 14.2.1, Docker Desktop 4.26.1), it happens both for "Use Virtualization framework" option tu... -
- Okay, I could reproduce the issue on my end. Thank you for your detailed info!
The root issue is that `CFLAGS` uses `-mbranch-protection=pac-ret` guessed by `configure` but `ASFLAGS` doesn't.
So here is a workaround to address the ... -
- Additionally, my another machine (Apple M2 Pro MacBook) could reproduce the segfault on both machine type of QEMU and VZ in Rancher Desktop.
Therefore, a difference of the cpu feature may not be trigger for the segfault.
And, I put t... -
- In my environment (Apple M1 MacBook on macOS 13.6.3), I could reproduce if I used the Apple Virtualization framework (VZ) machine type in a container execution environment (Rancher Desktop), but I couldn't reproduce if I used the QEMU em...
-
- I'm sure https://github.com/ruby/ruby/pull/9306 is the culprit but not sure when the segfault happens.
Could you share your `/proc/cpuinfo` to see if your machine supports Pointer Authentication or Branch Target Identification? -
02:45 AM Bug #20085: Fiber.new{ }.resume causes Segmentation fault for Ruby 3.3.0 on aarch64-linux
- Thanks. I tried the Dockerfile you provided, but I couldn't reproduce the segfault on aarch64.
Can you reproduce the issue with gdb and provide the backtrace?
Add the following lines to Dockerfile
* `RUN apt-get install gdb`
* `CMD gd... -
- We confirmed a bug in memory mapped files on Windows.
See https://github.com/ruby/ruby/pull/9358 for the fix.
We don't need to backport the logging. - 11:36 AM Revision e5a4f757 (git): Fix Window private file mapping unlink EACCES issue. (#9358)
- * Don't return early.
* Add missing `mapping` assignment.
* Make debug logs conditional. -
- > Raises FiberError if called on a fiber belonging to another thread.
I agree the error is a little confusing, but the reality is it's probably okay.
"in `kill': attempt to resume a resumed fiber (double resume) (FiberError)"
Yo... -
08:11 AM Revision b1f67cf0 (git): CI matrix for 3.3
- 06:58 AM Revision 24a2534f (git): Update bundled gems list as of 2023-12-26
-
- https://github.com/ruby/ruby/pull/9360
-
- This is still happend with latest version of Xcode.
```
linking ruby
ld: warning: ignoring duplicate libraries: '-ldl', '-lobjc', '-lpthread'
ruby: replacing existing signature
``` -
-
-
- https://github.com/ruby/syntax_suggest/commit/66e1cf0b3e
12/25/2023
-
-
- This commit adds a new workflow `pr-playground.yml` that posts a
Wasm-based PR playground link to the PR when it's labeled with
`playground`. -
- ```
ruby -e "Fiber.new{}.resume"
0.170 -e:1: [BUG] Segmentation fault at 0x0036ffffb4f110f0
0.170 ruby 3.3.0 (2023-12-25 revision 5124f9ac75) [aarch64-linux]
0.170
0.170 -- Control frame information ------------------------------... -
- st_replace and st_init_existing_table_with_size are functions used
internally in Ruby and should not be publicly visible. -
-
-
- I think we needed to add it to Compatibility issues in NEWS.md.
-
- It's intentional changes. see https://bugs.ruby-lang.org/issues/18797
-
- Regexp.new used to take up to 3 arguments, but now only 1..2 are allowed:
```
[1] pry(main)> Regexp.new 'abc', 'i', 'n'
ArgumentError: wrong number of arguments (given 3, expected 1..2)
from (pry):1:in `initialize'
```
On 3.2... -
-
-
- Continue on error because it is known that this fails right now.
Once fixed, we'll turn it off. - 12:13 PM Revision 8cd9bdd7 (git): Update default gems list at 1966a61a1e93560b9bf217662541c5 [ci skip]
-
-
- Fixes https://github.com/ruby/optparse/pull/51
https://github.com/ruby/optparse/commit/667ab35f59 -
12:12 PM Revision df941aa9 (git): [ruby/resolv] Fix typo
- https://github.com/ruby/resolv/commit/5dfdcfb7c7
-
- https://github.com/ruby/irb/commit/2d5a1afdf5
-
12:12 PM Revision 86fa418d (git): [ruby/ipaddr] Consider IPv4-mapped IPv6 addresses link local/loopback if IPV4 address is private
- Same as #57
https://github.com/ruby/ipaddr/commit/d56acecb80 - 12:12 PM Revision da77c79d (git): [ruby/ipaddr] Fix regressions in exception messages
- Changes introduced by 09edfd4 have broken some exception
messages, and added the address as an unnecessary
suffix in others.
https://github.com/ruby/ipaddr/commit/74a043109c -
12:12 PM Revision eb531313 (git): [ruby/ipaddr] ntop: Measure address size in bytes
- `IPAddr.ntop` takes the binary representation of an IP address, whose
length should be 4 or 16 *bytes* (not characters/codepoints).
The current implementation accepts strings in any encoding, but for
some values in non-BINARY encoding, ... -
12:12 PM Revision ea5776e7 (git): [flori/json] Use rb_sym2str instead of SYM2ID
- This avoids pinning an id to the symbol used if a dynamic symbol is
passed in as a hash key.
rb_sym2str is available in Ruby 2.2+ and json depends on >= 2.3.
https://github.com/flori/json/commit/5cbafb8dbe - 12:12 PM Revision 65ec74a8 (git): [ruby/io-console] Provide a 'Changelog' link on rubygems.org/gems/io-console
- By providing a 'changelog_uri' in the metadata of the gemspec
a 'Changelog' link will be shown on https://rubygems.org/gems/io-console
which makes it quick and easy for someone to check on the changes
introduced with a new version.
Deta... -
- https://github.com/ruby/io-console/commit/08e41a3e4d
-
- https://github.com/ruby/io-console/commit/44dce34569
-
- https://github.com/ruby/io-console/commit/63dbeeecf4
-
- https://github.com/ruby/securerandom/commit/e8be08901a
-
- https://github.com/ruby/tempfile/commit/6932d6bc6f
-
- https://github.com/ruby/psych/commit/fc9ca15999
- 12:12 PM Revision bb162585 (git): [ruby/psych] Remove now-unreachable rescue block
- https://github.com/ruby/psych/commit/6905a2123c
- 12:12 PM Revision 95e7af0c (git): [ruby/psych] Remove unused array
- https://github.com/ruby/psych/commit/b9e7b4a4a4
- 12:12 PM Revision b4cb7ead (git): [ruby/fiddle] Bump version
- https://github.com/ruby/fiddle/commit/fd4bb4ea8a
- 12:12 PM Revision 60e46926 (git): [ruby/csv] Bump version
- https://github.com/ruby/csv/commit/0cba3e766d
- 12:12 PM Revision cb6a5569 (git): [ruby/date] Provide a 'Changelog' link on rubygems.org/gems/date
- By providing a 'changelog_uri' in the metadata of the gemspec
a 'Changelog' link will be shown on https://rubygems.org/gems/date
which makes it quick and easy for someone to check on the changes
introduced with a new version.
Details of... -
- https://github.com/ruby/etc/commit/44425427ab
-
- https://github.com/ruby/etc/commit/0353d7c8ee
-
- https://github.com/ruby/etc/commit/a39e982129
- 12:12 PM Revision 1e1da750 (git): [ruby/timeout] Provide a 'Changelog' link on rubygems.org/gems/timeout
- By providing a 'changelog_uri' in the metadata of the gemspec
a 'Changelog' link will be shown on https://rubygems.org/gems/timeout
which makes it quick and easy for someone to check on the changes
introduced with a new version.
Details... -
- https://github.com/ruby/timeout/commit/301ad4cfdc
- 12:12 PM Revision 24e0f6fc (git): [ruby/net-protocol] Provide a 'Changelog' link on rubygems.org/gems/net-protocol
- By providing a 'changelog_uri' in the metadata of the gemspec
a 'Changelog' link will be shown on https://rubygems.org/gems/net-protocol
which makes it quick and easy for someone to check on the changes
introduced with a new version.
De... - 12:12 PM Revision da06c097 (git): [ruby/base64] Provide a 'Changelog' link on rubygems.org/gems/base64
- By providing a 'changelog_uri' in the metadata of the gemspec
a 'Changelog' link will be shown on https://rubygems.org/gems/base64
which makes it quick and easy for someone to check on the changes
introduced with a new version.
Details ... - 12:12 PM Revision 12ff13c6 (git): [rubygems/rubygems] Bump rb-sys
- Bumps [rb-sys](https://github.com/oxidize-rb/rb-sys) from 0.9.83 to 0.9.84.
- [Release notes](https://github.com/oxidize-rb/rb-sys/releases)
- [Commits](https://github.com/oxidize-rb/rb-sys/compare/v0.9.83...v0.9.84)
---
updated-depende... -
12:12 PM Revision df11b3da (git): [rubygems/rubygems] Let the guards have some space to breathe
- https://github.com/rubygems/rubygems/commit/73f1609715
-
- Not wrapping to_lock since access to it is single threaded and
read-only at the time of writing the lockfile.
https://github.com/rubygems/rubygems/commit/3b53aa1b12 -
- https://github.com/ruby/rdoc/commit/6231b03476
-
- Constant definitions using these functions have been supported, but
since RDoc::Parser::C#gen_const_table did not consider other than
`rb_define_const` the documents for them have not been found, without
`Document-const` direvtive.
Fixe... -
- https://github.com/ruby/optparse/commit/324ff21f04
-
- Fixes https://github.com/ruby/optparse/pull/51
https://github.com/ruby/optparse/commit/1c895efc39 -
- This reverts commit 6a79e53823e328281b9e9eee53cd141af28f8548.
-
- This reverts commit d242e8416e99eaee4465e2681210ae8b7ecd6d34.
-
12:12 PM Bug #20083 (Closed): String#match? behaving inconsistently with Ruby 3.3.0
- From irb, when calling String#match?
```
pattern = /([\s]*ABC)$/i # or /(\s*ABC)/i
p "1ABC".match?(pattern) # => true
p "12ABC".match?(pattern) # => true
p "123ABC".match?(pattern) # => true
p "1231ABC".match?(pattern) # => t... -
-
- 10:30 AM Revision cd844592 (git): Update default gems list at e7d0ec361941a9d67616c3df1dd82d [ci skip]
-
-
09:47 AM Revision 0d175ec4 (git): Copy 3.3.0 NEWS.md to doc/NEWS [ci skip]
- Basically 7d264e8e7bc21800c79b81e73a38082ff88c220b but for 3.3.0.
- 09:46 AM Revision c224179b (git): Update default gems list at e1c0e8cac4af53b64e7827fabaa5ae [ci skip]
-
-
- Basically bb2c3601381d8ecb033e48825f3d0c2a387dddf2 but for 3.4.0.
-
- Revert "Remove deprecated code to fix RUBY_DEBUG build failures"
This reverts commit 9614bea2cd59902a051a7387e354e23a52fe5396.
And changed 3.4 to 3.5. To be fixed properly later. -
-
-
-
- Applied in changeset commit:git|44592c4e20a17946b27c50081aee96802db981e6.
----------
Implement `it` (#9199)
[[Feature #18980]](https://bugs.ruby-lang.org/issues/18980)
Co-authored-by: Yusuke Endoh <mame@ruby-lang.org> -
- [[Feature #18980]](https://bugs.ruby-lang.org/issues/18980)
Co-authored-by: Yusuke Endoh <mame@ruby-lang.org> -
09:13 AM Revision 98eeadc9 (git): Development of 3.4.0 started.
-
-
- Applied in changeset commit:git|a9f096183170810ac6ce32b20d7810d11a51b5f5.
----------
[Feature #19370] Prohibit nesting anonymous parameter forwarding -
-
-
- In the extension libraries in spec/ruby/optional/capi, do not care
about deprecated declarations. -
-
- Run this test separately because something seems remained unreleased
on Windows. -
- RUBY_FL_PROMOTED is used by the garbage collector to track when an
object becomes promoted to the old generation. rb_obj_setup must not
copy that flag over because then it may become out-of-sync with the age
of the object.
This fixes a ... -
-
-
- The test fails when RGENGC_CHECK_MODE is turned on:
1) Failure:
TestSymbol#test_inspect_under_gc_compact_stress [test/ruby/test_symbol.rb:123]:
<":testing"> expected but was
<":\x00\x00\x00\x00\x00\x00\x00">. -
- These are intentional words
-
-
- The for loops for marking and reference updating declaratively marked
TypedData objects did not mark/reference update the very last element.
When RGENGC_CHECK_MODE is turned on, this caused the test in Enumerator
to fail with:
tool... - 01:20 AM Revision 260bf60e (git): Correctly release the underlying file mapping. (#9340)
- * Avoiding using `Tempfile` which was retaining the file preventing it from unlinking.