Activity
From 05/12/2024 to 05/18/2024
05/18/2024
-
03:29 PM Revision dbbaf871 (git): [DOC] Fix `$<` comment
-
-
02:59 PM Bug #20154: aarch64: configure overrides `-mbranch-protection` if it was set in CFLAGS via environment
- I don't think I quite understand what exactly the right course of action here is.
> Would it make sense to check if such flags exist and not overwrite them if they do?
Why is this not a serious proposal? "We should respect user giv... -
- You're welcome, thank you for posting such a detailed and actionable report. You're exactly right; your patch deals with this issue in IO methods using `rb_io_getline_fast` but this is probably causing crashes in other places as well; _h...
-
10:28 AM Bug #20493: Segfault on rb_io_getline_fast
- Thanks for this extremely detailed explanation!
Just for my own understanding [I'm not as proficient in low level C, took me a while reading through all details], can I assert that: the fix I suggested would've only "fixed" the segfau... -
- After applying that fix to the RPM spec file in https://build.opensuse.org/package/show/devel:languages:ruby/ruby3.3, I can't get the reproduction to crash any more.
-
- I opened https://github.com/ruby/ruby/pull/10795 as a proposed fix for this. Let's see what other people (and CI) think :)
-
- OK, I believe I've worked out what's wrong here.
The BLOCKING_REGION macro is used to release the GVL, run some code, and re-acquire the GVL. It looks like this:
```
#define BLOCKING_REGION(th, exec, ubf, ubfarg, fail_if_interrupt... -
- Thank you for your bug report and excellent reproduction! I've had a look at this today - I haven't reached a conclusion yet, but I want to write down where I got so far.
The crash is happening because:
* One thread is calling `rb_... -
11:10 AM Bug #19753: IO::Buffer#get_string can't handle negative offset
- Backported by https://github.com/ruby/ruby/pull/10778
- 11:09 AM Revision 0e664ebc (git): Fix `io_buffer_get_string` default length computation. (#8427)
- * Fix `io_buffer_get_string` default length computation.
When an offset bigger than the size is given, the resulting length will be
computed incorrectly. Raise an argument error in this case.
* Validate all arguments. - 11:09 AM Revision 67d499a7 (git): Improvements to `IO::Buffer` `read`/`write`/`pread`/`pwrite`. (#7826)
- - Fix IO::Buffer `read`/`write` to use a minimum length.
- 11:09 AM Revision 359e40e3 (git): Rename `data` -> `buffer` for better readability. (#7836)
-
-
- * Add types to `tLAMBDA` and `tSTRING_DBEG` to store corresponding
information when returning these tokens.
* Add `enum lex_state_e state` to `%union` for `tSTRING_DBEG`. -
- Since you say you're OK with solutions requiring modifying the program though, have you tried doing something like this?
```
Tempfile::Remover.class_eval { def call(...) = nil }
```
I realise if this is a common use-case it would... -
06:44 AM Revision ac85eef1 (git): Fix links
-
02:26 AM Revision 55c62e67 (git): No need to specify tags anymore
- In the past, these codes were used by both parser and ripper.
On ripper, the type of LHS is `<val>` then type cast was needed.
However currently these are only used by parser then no need to
cast.
05/17/2024
-
10:05 PM Feature #20448: Make coverage event hooking C API public
- Thanks for the research. So, `TracePoint.new(:branch)` seems good enough for the use case of fuzzer, right?
But with just this API, there is no way to get the list of all edges, including ones that are not fired. This is needed for br... -
06:37 PM Feature #20448: Make coverage event hooking C API public
- **TL;DR: I've been further researching how fuzzers gather coverage information, and what types of coverage are most useful for fuzzing. I think the best course of action regarding this request would be to implement a fairly general cover...
-
08:42 PM Revision cce7c25a (git): [PRISM] Enable TestRequire
-
- We've spotted a consistent segfault when running bundle install with `--jobs 4`
When running: `bundle install -j 4` we'd get a Segfault at:
```
/usr/lib64/ruby/3.3.0/rubygems/ext/builder.rb:93: [BUG] Segmentation fault at 0x000000... -
03:37 PM Bug #20218: aset/masgn/op_asgn with keyword arguments
- In this issue there's no consideration of compatibility or utility. This is a breaking change. The ability to pass kwargs to index methods has been in ruby for a long time, probably from the inception of kwargs and I have code that uses ...
-
-
-
- https://github.com/ruby/prism/commit/31ef81fd06
-
02:45 PM Revision aed93ba1 (git): [ruby/prism] Replace and Use PM_LOCATION_NULL_VALUE macro
- https://github.com/ruby/prism/commit/50e188b168
-
-
01:04 PM Revision 2d825ca7 (git): REXML 3.2.8 is not working with rss and test-bundled-gems yet.
- https://github.com/ruby/ruby/actions/runs/9125437794/job/25091614796#step:11:272
- 08:40 AM Revision 8acec5b6 (git): Update bundled gems list at 10d02e71d1f57b68f530c0e669e444 [ci skip]
- 08:26 AM Revision cbc84b80 (git): * 2024-05-17 [ci skip]
-
- 08:25 AM Revision 5db59cd5 (git): [ruby/openssl] test_asn1.rb: Remove the assertions of the time string format without second.
- This commit fixes the following errors in the tests.
Because the OpenSSL project changed the code to make the time string format
without second invalid. So, we drop the assertions.
```
1) Error: test_generalizedtime(OpenSSL::TestASN1): ... -
08:25 AM Revision 89574f02 (git): [ruby/openssl] test/openssl/test_asn1.rb: skip failing tests on LibreSSL 3.6.0
- LibreSSL 3.6.0 expects the seconds part in UTCTime and GeneralizedTime
to be always present. LibreSSL 3.6.0 release note [1] says:
> - The ASN.1 time parser has been refactored and rewritten using CBS.
> ...
[1] https://ftp.openbsd.org/... - 08:25 AM Revision 10f4e4d9 (git): [ruby/net-http] Skip test_session_reuse_but_expire with OpenSSL 3.3
- OpenSSL 3.3.0 9 Apr 2024 is also broken.
Signed-off-by: Xi Ruoyao <xry111@xry111.site>
https://github.com/ruby/net-http/commit/ab525c956d -
- 02:50 AM Revision 534f1c37 (git): Bump actions/checkout in /.github/actions/setup/directories
- Bumps [actions/checkout](https://github.com/actions/checkout) from 4.1.5 to 4.1.6.
- [Release notes](https://github.com/actions/checkout/releases)
- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)
- [Commits](http... - 02:50 AM Revision 0f8f0386 (git): Bump actions/checkout from 4.1.5 to 4.1.6
- Bumps [actions/checkout](https://github.com/actions/checkout) from 4.1.5 to 4.1.6.
- [Release notes](https://github.com/actions/checkout/releases)
- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)
- [Commits](http... -
- (https://github.com/ruby/irb/pull/956)
When a syntax error includes multiple error messages, we want to
check for unrecoverable messages first so that we do not
accidentally match a recoverable error later in the message.
https://githu... -
-
02:05 AM Revision b90ea8ae (git): [ruby/find] find.gemspec: Drop executables dir config
- This gem contains no executables.
https://github.com/ruby/find/commit/7bd452155e -
01:18 AM Misc #20407: Question about applying encoding modifier to an interpolated Regexp
- I checked the related source code especially about rb_reg_preprocess_dregexp. It wrongly calls rb_reg_preprocess with overwriting fixed_enc instead of inheriting it.
It seems to raise error if the resulted encoding of the regexp is ot... -
12:55 AM Feature #20470: Extract Ruby's Garbage Collector
- +1 for extracting GC implementation of `gc.c` into a separate `gc_impl.c` file.
My motivation: Some of the use cases of Ruby on Wasm (e.g. edge computing platform) do not actually need to collect garbage objects during execution because...
05/16/2024
-
-
- https://github.com/ruby/prism/commit/72518f5716
-
- https://github.com/ruby/prism/commit/ab43b3ab66
-
-
-
05:43 PM Feature #20492 (Open): Debug option for tempfile
- Hi,
the ruby lib tempfile is quite useful, but since it always deletes files once the object is garbage collected or the program terminates (or the program explicitely asks to remove the file) it is difficult to debug programs and to... -
- https://github.com/ruby/prism/commit/2a43b4f55c
-
04:43 PM Feature #20484: A new pragma for eager resolution of classes referenced in rescue clauses.
- zverok (Victor Shepelev) wrote in #note-3:
> Honestly, it is no different than any name used in a branch that wasn’t tested. E.g. if you have this:
> ...
I would agree that any such opt-in feature should probably catch other cases. I'... -
-
-
-
-
-
03:15 PM Bug #19753: IO::Buffer#get_string can't handle negative offset
- Thanks so much, I will review it.
-
- I have cherry-picked some additional refactoring commits and open pull request https://github.com/ruby/ruby/pull/10778.
-
- https://github.com/nagachika/ruby/commit/7d325d1b2ea7b6ef7debd6a29ad97c93311ed9b5 Here is the changeset to backport into ruby_3_2 branch, including style change and refactoring (data -> buffer).
I have resolved some conflict by hand.
@... -
- https://github.com/ruby/prism/commit/0ef5658dcc
-
- https://github.com/ruby/prism/commit/8d4c5c2bca
-
- https://github.com/ruby/prism/commit/178d4f66fd
-
- https://github.com/ruby/prism/commit/863197629c
-
- https://github.com/ruby/prism/commit/57d5c9be2c
-
- https://github.com/ruby/prism/commit/33d12afa60
-
01:34 PM Revision c55c11d7 (git): [rubygems/rubygems] Fix binstubs sometimes not getting regenerated when `--destdir` is given
- This was only working for gems also installed in the default gem home.
https://github.com/rubygems/rubygems/commit/47df02dbd9 -
- So that it can also be delegated to `Gem::SpecificationRecord`.
https://github.com/rubygems/rubygems/commit/1407807a99 -
-
- https://github.com/rubygems/rubygems/commit/7f0706a897
-
- Tests have two copies of b-2 installed, one in default home and another
in user home. But only the one in default home was visible because of
not reloading paths. The user install test was working by chance.
https://github.com/rubygems/... -
- https://github.com/rubygems/rubygems/commit/5fbe5e43d6
-
- If `cache_all_platforms` setting is enabled, the secondary source was
no longer considering cached gems.
That means that if the remote secondary source has removed its gems,
then this was now resulting in an error while before the previ... -
- https://github.com/rubygems/rubygems/commit/6166e4bce1
-
- https://github.com/rubygems/rubygems/commit/5d03a346ab
-
- https://github.com/rubygems/rubygems/commit/535c83d5be
-
- Applied in changeset commit:git|2dd46bb82ffc4dff01d7ea70922f0e407acafb4e.
----------
[Bug #20468] Fix safe navigation in `for` variable -
- I talked with k0kubun and disscussed about multiple options as below.
I understand the background and agree to go ahead.
Upgrading BASERUBY
* more work for each upgrade
* there is less motivation to upgrade BASERUBY other than mk_b... -
- I think it's obviously a bug, but I'm concerned that changing the behavior might cause FrozenError in applications. Therefore, I have decided not to backport the changesets related to this issue.
Please feel free to raise any objections... -
-
- > leaving the files after gem rebuild was intentional, for local
> ...
https://github.com/rubygems/rubygems/pull/4913#issuecomment-2081710691
https://github.com/rubygems/rubygems/commit/185a2091fb -
-
- Thank you for your report. I will look the PRs.
I will set the status of this ticket because of this is a backport ticket.
And currently 3.1 branch is under the security maintenance phase, so I fill the Backport field for 3.1 with "WON... -
- Thank you. I'll do my best.
-
04:28 AM Misc #20491: Proposal for new branch maintainers
- I think this is a good idea. Approved.
Matz -
- Note: I confirmed this proposal with @k0kubun and @usa
-
- Since this was a long standing bug, I won't backport it to stable branch in general. If you know any real applications suffered from this behavior, please let me know.
Thanks. -
- ruby_3_2 2d686e1019414f6bbb7ccbfa897b7b665250743d merged revision(s) ae8990aef098410ecc2b5f48fea9d7d171a3c5f6.
-
- Alias init functions
The extension library has each initialization function named "Init_" +
basename. If multiple extensions have the same base name (such as
cgi/escape and erb/escape), the same function will be ... -
12:06 AM Feature #16461: Proc#using
- Sorry for the delay.
Eregon (Benoit Daloze) wrote in #note-10:
> Reading #12086 again, I feel #12281 is a much simpler alternative (`using(refinement) { literal block }`).
> ...
It looks too redundant to me because `using` is needed...
05/15/2024
-
11:41 PM Feature #19840 (Feedback): [Proposal] Expand Find pattern to Multiple Find
- Sorry for late response.
I disagree with this suggestion.
I implemented this feature in the [pattern-match](https://github.com/k-tsj/pattern-match) gem, a PoC library for pattern matching.
```ruby
match({ results: [{ id: 1, nam... -
- I've updated the message to say:
```
'when' clause on line 4 duplicates 'when' clause on line 2 and is ignored
```
I hope this is okay, I believe it is much more clear. The PR is here: https://github.com/ruby/ruby/pull/10776. @no... -
-
-
-
-
-
- https://github.com/ruby/prism/commit/89d0d9851a
-
- https://github.com/ruby/prism/commit/dd532ded95
-
- It is saved in `setup` and restored in `teardown`.
https://github.com/rubygems/rubygems/commit/880c5de667 -
- In RubyKaigi 2024, I, naruse and nagachika discussed about maintaining stable branches. We propose the following members for the new branch maintainer of current stable branches.
* `ruby_3_3`: @k0kubun
* `ruby_3_2`: @nagachika
* `... -
04:21 AM Bug #20490: Process.waitpid2(-1, Process::WNOHANG) misbehaves on Ruby 3.1 & 3.2 with detached process
- I've opened fixes here:
* 3.2: https://github.com/ruby/ruby/pull/10771
* 3.1: https://github.com/ruby/ruby/pull/10772 -
- I think this patch in the `ruby_3_2` branch fixes the problem:
```diff
diff --git a/process.c b/process.c
index 354e16fd26..52d49948a5 100644
--- a/process.c
+++ b/process.c
@@ -1290,7 +1290,7 @@ waitpid_wait(struct waitpid_state *w)
... -
- This is a follow-up issue for a bug that I thought was fixed in https://bugs.ruby-lang.org/issues/19837 and duplicated in https://bugs.ruby-lang.org/issues/20181.
The following script doesn't terminate quickly in Ruby 3.1.5 and 3.2.4,... -
05/14/2024
-
09:51 PM Bug #20424: ZLib::GZipReader always double allocates strings when passed outbuf, significantly increasing memory usage
- [zlib #61 was merged](https://github.com/ruby/zlib/pull/61#event-12808578072). It seems like we can consider this ticket complete.
-
09:44 PM Revision e3e1e530 (git): [ruby/zlib] Avoid double copying into provided outbuf
- https://github.com/ruby/zlib/commit/07f44b7546
-
- This accounts for a significant number of string allocations when reading rubygems, but we can avoid that in many places by only copying into the outbuf when present
https://github.com/ruby/zlib/commit/d25ef406c1 - 09:43 PM Revision cb1a574e (git): Bump github/codeql-action from 3.25.4 to 3.25.5
- Bumps [github/codeql-action](https://github.com/github/codeql-action) from 3.25.4 to 3.25.5.
- [Release notes](https://github.com/github/codeql-action/releases)
- [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md... -
08:37 PM Bug #20489: Ractor behavior strange in ruby master
- Thank you. I'll investigate it.
-
09:00 AM Bug #20489 (Closed): Ractor behavior strange in ruby master
- This is a tarai program
Run`./ruby tarai_ractor.rb 2 8` is to use 2 thread to run 8 times tarai function total, that means 4 times tarai for each ractor(thread).
```
GC.disable
def split_len(len, split)
ret = []
mod = l... -
07:41 PM Feature #6648: Provide a standard API for retrieving all command-line flags passed to Ruby
- nobu (Nobuyoshi Nakada) wrote in #note-15:
> `RbConfig` is for build time informations, and does not look a right place for runtime informations.
Isn't it ok to relax the semantics a little bit? RbConfig seems to me the most logical ... -
07:49 AM Feature #6648: Provide a standard API for retrieving all command-line flags passed to Ruby
- Note that for this to be most effective it would be the arguments unprocessed as they appear on the command line, but that may not be possible to do if the shell removes quoting.
I don't think that should be a reason not to implement ... -
- `RbConfig` is for build time informations, and does not look a right place for runtime informations.
-
- If `RbConfig` is a convenient place for you, it is OK to add `ruby_args`.
Matz.
-
07:23 AM Feature #6648: Provide a standard API for retrieving all command-line flags passed to Ruby
- @matz Do you agree with `RbConfig.ruby_args`, is it OK to add it?
-
- When `gem uninstall <gem> --install-dir <dir>` is run, if the version
removed had a plugin, and that same version happened to also be
installed globally, then the plugin stub would fail to be removed.
https://github.com/rubygems/rubygem... -
- This class handles all logic to handle the list of specifications, given
a set of GEM_PATH directories. Makes `Gem::Specification` has less
responsibilities and will help with fixing some bugs next.
https://github.com/rubygems/rubygems/... -
- https://github.com/rubygems/rubygems/commit/8c9807092c
-
- Other analog methods are documented, so document this one too.
https://github.com/rubygems/rubygems/commit/76da34d44d -
- I don't think this method is any worse than others, let's only document
what it does.
https://github.com/rubygems/rubygems/commit/dec722187f -
- https://github.com/rubygems/rubygems/commit/b545daa95d
-
- If we move test directory removal to the very end, I think we should not
leak anything.
https://github.com/rubygems/rubygems/commit/fb3d8944b5 -
- https://github.com/rubygems/rubygems/commit/7b71965a70
-
09:56 AM Feature #15554: warn/error passing a block to a method which never use a block - `--warn-unused-block`/`:warn_unused_block`?
-
- We are discussing how to make opt-in.
Because relaxed mode can miss cases (e.g. for methods with a common name), and some newer codebases/some Rubyists might want to use the stricter check (e.g. it enhances readability, ignored blocks b... -
09:00 AM Feature #20437: Could the licensing conditions be made less ambiguous?
- > The Ruby License is a dual license with 2-clause BSDL and the "conditions below". Your proposal is the proposal to change the Ruby license and it won't be accepted.
If these two are inseparable, forming together the "Ruby" license, th... -
- > lib/net/protocol.rb
The description is obsoleted.
The license of the code is the same as Ruby
> ...
Racc's license is the same as Ruby
see also https://github.com/ruby/racc
> Rubygems
It looks MIT License and the Ruby lic... - 08:22 AM Revision 41e6fd06 (git): [DOC] Fix typo in example code for `String#encode` method
- The example code in the documentation for the `String#encode` method has
a typo in the `fallback` option. The example code uses `h` as the
fallback option, but it should use `hash` instead to match the variable
name in the example code. - 08:19 AM Revision 44f50f41 (git): Update default gems list at 4a1e4436a99c5794b022f03e8c0589 [ci skip]
-
08:18 AM Revision 4a1e4436 (git): [ruby/reline] Bump version to 0.5.7
- (https://github.com/ruby/reline/pull/704)
https://github.com/ruby/reline/commit/b9b3d392ff -
- Thank you for the PR. I agree that the patch is good to backport. PR merged at 449899b38314d0ecbe61e42d34398bdf2561b8e9.
-
07:29 AM Revision 449899b3 (git): Fix `String#index` to clear MatchData when a regexp is passed
- [Bug #20421]
The bug was fixed in Ruby 3.3 via 9dcdffb8bf8a3654fd78bf1a58b30c8e13888a7a -
- As long as the pluggable GC issue is clearly stated somewhere, I have no objection.
Matz.
-
07:01 AM Feature #20470: Extract Ruby's Garbage Collector
- I think the risk is fairly low, since the user has to compile Ruby with `--with-shared-gc` to enable this feature. Since they have to manually enable this feature at compile time, they should be aware of the possible security issues that...
-
- My concern is that a part of this feature, adding a new environment variable that loads a shared object implicitly, can cause security issues.
`LD_PRELOAD`, `DYLD_INSERT_LIBRARIES` and so on have the same risk, so dynamic linkers remove... -
06:43 AM Revision b60f0944 (git): Fix TestPatternMatching#test_deconstruct_keys test
- Before the change `C.keys` returned keys captured in some previous test case that by chance captured `nil` value what made this test passed successfully. Now it returns keys captured in this test case.
-
- (https://github.com/ruby/reline/pull/701)
* Refactor send
* Implement the undo command
* Fix @past_lines initialization
* Improve assertion
* Hide to save buffer in insert_pasted_text
* Replace @using_delete_command with @undoing
...
05/13/2024
-
- No worries. This aspect of Ruby GC often confuses people.
-
09:35 AM Bug #20485: Simple use of Fiber makes GC leak objects with singleton method
- I tried looping with `100.times` in a more complex case that I created in the middle of the entire investigation of a test suite whose memory usage keeps growing until getting killed due to OOM, and as you said, the "leaked" object remai...
-
- Alright, looking at your dump:
```json
{"address":"0x7f2b570455b8", "type":"CLASS", "shape_id":2, "slot_size":160, "class":"0x7f2b57045518", "variation_count":0, "superclass":"0x7f2b5707fd30", "name":"Work", "references":["0x7f2b5707... -
- I asked my co-workers to try this script and some of them gave me their results. The following table includes my results.
|Environment|# of people|Reproducibility|
|--|--|--|
|ruby 3.3.1 (2024-04-23 revision c56cd86388) [x86_64-linu... -
- @skhrshin if you can reproduce consistently, what could be helpful would be to provide a heap dump like this (use some service list GitHub gist because the output might be big:
```ruby
require 'objspace'
class Work
def add_meth... -
- To be honest I also tried 3.2.2 and 3.1.4, each with `[1].each`, `1.times` and `Mutex.new.synchronize`, and neither reproduced.
So I'm starting to wonder if it isn't simply that for some reason one object consistently end up on the st... -
-
- I closed because I tried your repro script with `ruby 3.3.1 (2024-04-23 revision c56cd86388) [arm64-darwin23]` both with `1.times` and `Mutex.new.synchronize` and it doesn't fail.
Also your description really fit [Bug #19436], hence ... -
- Do you mean this is fixed in trunk? Or are you saying this shouldn't happen on Ruby 3.3.1? If latter, that is not correct as I wrote `[1].each` and `Mutex.new.synchronize` versions reproduce the problem on Ruby 3.3.1.
I would like you t... -
- I was hoping we might be able to decide on an official maximum size for a source file in terms of bytes/lines/columns/etc.
Ruby uses fixed integer sizes to represent line numbers, column numbers, offsets, etc. These can overflow with ... -
- I'm not sure why but this particular change seems to have introduced
some flaky test failures. So I'll revert it.
https://github.com/rubygems/rubygems/commit/668488014b -
- https://github.com/rubygems/rubygems/commit/de4650f629
-
- https://github.com/rubygems/rubygems/commit/8c8aaecc48
-
- I asked Matz and here is a reordered agenda: https://hackmd.io/CoLraFp_QrqyHBcv3g8bVg?both
Many topics so we can't discuss all of them. The purpose of this meeting is knowing each other. Please discuss detailed topics with the people ... -
05:48 AM Misc #20436: DevMeeting at RubyKaigi 2024
- * [Bug #20424] ZLib::GZipReader always double allocates strings when passed outbuf, significantly increasing memory usage
* Lots of discussion on the GitHub PR [here](https://github.com/ruby/zlib/pull/61)
* What do we need to do to... -
- I figured that was already happening for the "unused" warning.
-
- https://github.com/ruby/prism/commit/d4eb13e703
-
04:29 PM Revision 5931f857 (git): [ruby/prism] Add error handling for missing `parser` gem in `Prism::Translation`
- Resolves https://github.com/ruby/prism/pull/2803.
This PR adds error handling for missing `parser` gem in `Prism::Translation`.
The `parser` gem is a required runtime dependency when using `Prism::Translation::Parser`.
But it is not re... -
- Having the @newline instance variable in every node adds up, and
since it is so rarely used, we only want to add it when necessary.
Moving this into an autoloaded file and moving the instance variable
out of the default initializers red... -
- https://github.com/rubygems/rubygems/commit/716666f65f
-
12:24 PM Bug #20487 (Rejected): 1..nil is giving range from 1 to inifinity in ruby greater than 2.6
- This is expected behavior. `nil` is the implicit end of an endless range:
```ruby
(1..) == (1..nil)
# => true
(1..nil)
# => 1..
(1..).end
# => nil
``` -
12:18 PM Bug #20487 (Rejected): 1..nil is giving range from 1 to inifinity in ruby greater than 2.6
- we consider nil as undefined value, value that is not present, we consider nil as falsey value as well, when we do nil.to_i it gives us zero..then with this rational 1..nil shouldn't give the range 1 to infinity, either we should make it...
- 10:35 AM Revision 58801034 (git): [rubygems/rubygems] Use spec.base_dir to remove plugins
- The plugin loader from `@gem_home` was removed during uninstallation.
However, this could leave behind the plugins for `--user-install`
installed gems.
Use `Gem::Specifictaions#base_dir` instead. This ensures that the plugin
loader for ... -
- Instead of unit testing the `remove_plugins` method, test the whole
removal process.
https://github.com/rubygems/rubygems/commit/bfdc60af98 -
- If one upgrades the default copy of Bundler through `gem update
--system`, and then reinstalls Ruby without removing the previous copy.
Then the new installation will have a correct default bundler gemspec,
but a higher copy installed in... -
- We should make sure Bundler does not trigger RubyGems require logic for
gem activation until it had the chance to register its own monkeypatches
to RubyGems.
https://github.com/rubygems/rubygems/commit/fbd2ff86b9 -
- https://github.com/rubygems/rubygems/commit/07022e3f2f
-
- "internal compiler error" means a bug of gcc.
We can do nothing for it. -
- Follow CRuby build guide in `https://github.com/ruby/ruby`
Some file like `numerc.c` whill produce a `internal compiler error` when enble option `-fno-omit-frame-pointer`
gcc version is
```
$ gcc --version
gcc.exe (Rev2, Built by... -
- Eager resolution of referenced constants at parse time would be very painful in many case as it would add some extra constraints on load order, likely causing circular dependency issues, even before considering things such as `autoload`....
05/12/2024
-
- Fixed warning about discarding modifiers.
```
../src/ruby_parser.c:677:48: warning: passing 'rb_encoding *' (aka 'const struct OnigEncodingTypeST *') to parameter of type 'void *' discards qualifiers [-Wincompatible-pointer-types-discar... -
- Looks like a duplicate of https://bugs.ruby-lang.org/issues/19436, fixed in Ruby 3.3 but can't really be backported.
-
- I confirmed that all of `1.times`, `[1].each` and `Mutex.new.synchronize` versions reproduce the problem on Ruby 3.2.4.
-
- Changing `1.times` to `[1].each` could reproduce the problem on Ruby 3.3.1 too.
-
- Update: To reproduce this issue with Ruby 3.3.1, Mutex is necessary.
-
- Update: Using Mutex was not necessary.
-
- I found a possible memory leak which occurs only when several conditions are met.
The code to reproduce the problem is below:
```
class Work
def add_method
singleton_class.define_method(:f) {}
end
end
1.times { Fibe... -
07:57 AM Feature #20484: A new pragma for eager resolution of classes referenced in rescue clauses.
- Honestly, it is no different than any name used in a branch that wasn’t tested. E.g. if you have this:
```ruby
if foo
OneClass.new
else
OtherClass.new
end
```
...and the `else` branch wasn’t covered by tests, and the `OtherCl... -
- duerst (Martin Dürst) wrote in #note-1:
> Can you give an example with actual code to show where you get problems?
The problem I ran into is that the exception class was properly named `SomeModule::SomeClass`, but my rescue block had... -
02:13 AM Feature #20484 (Feedback): A new pragma for eager resolution of classes referenced in rescue clauses.
- Can you give an example with actual code to show where you get problems?
-
- What’s the expected semantics of this range?
There can be several options. Note that the behavior should be consistent/explainable in the context of other ranges (sometimes it makes sense to define the specialized behavior, but a very ... -
- Applied in changeset commit:git|b911d2222f907d3fad397938e8f513ecfb4635b8.
----------
[Bug #20482] [DOC] Clarify about pattern maching guard clause
Guard clauses can only be used in `case` pattern matching statements,
not in `=>`/`in` o... -
- Soilent (Konstantin x) wrote in #note-2:
> Thank you, nobu! That explains it.
> ...
Yes, you can confirm the AST by `ruby --dump=parsetree -e '1 in a if a'` (the code is simplified).
> And since this is a modifier `if`, the parser c... -
06:08 AM Bug #20482: nil variables in a guard clause of a standalone => or in expression
- Thank you, nobu! That explains it.
Just to clarify, is this how the expression is parsed?
```ruby
( [1, 2] in a, b ) if b == 2*a
```
And since this is a modifier `if`, the parser creates variables a and b first, which is why t... -
- One-line pattern matching can not have a guard clause, so the `if` in the first example is a modifier `if` and is evaluated before the pattern matching.
In short, it should be intentional, I think. -
- Guard clauses can only be used in `case` pattern matching statements,
not in `=>`/`in` operators. -
- I think that same concern applies to some existing `GC` methods (e.g. `GC.compact`, `GC.verify_compaction_reference`) etc. So it would make sense that plugable GC would offer a way for the GCs to register behavior for these methods, and ...
-
-
-
- Applied in changeset commit:git|8b9b150512b7b9514143a6b971992c9a539ead2f.
----------
[Bug #20481] Check for unmarshaling ivar
Prohibit setting instance variables of existing classes and modules
via link. -
- Prohibit setting instance variables of existing classes and modules
via link. -
-
- https://github.com/ruby/irb/commit/7d60349499
-
- Even this should be a syntax error?
```ruby
def foo(bar = ->(baz = bar) {}) end
```
That means it needs to manage the list of yet-unusable variables, not only tracking single variable.