Activity
From 12/02/2024 to 12/08/2024
12/08/2024
-
11:14 PM Revision 895f2c21 (git): [ruby/rdoc] lint: Remove unreachable code
- (https://github.com/ruby/rdoc/pull/1137)
This is an attempt to utilize RuboCop further.
RuboCop was added in https://github.com/ruby/rdoc/commit/9262fdd43a3a
but only a few rules have been enabled.
I believe we can utilize RuboCop more ... - 10:43 AM Revision dd43af3b (git): [ruby/rdoc] Use distinct styles for note lists and label lists
- (https://github.com/ruby/rdoc/pull/1209)
* Use the original `label` description list style
As a default for all description lists, the original "label" style is
more readable.
This is slightly different from the original `label` dl th... -
09:03 AM Misc #20879: DevMeeting-2024-12-12
- - [Feature #20935] API for Globally Enabling/Disabling Happy Eyeballs Version 2 in the Socket Class
- I would like to discuss the appropriateness of the API for enabling/disabling HEv2 in the `Socket` class. -
- When introducing Happy Eyeballs Version 2 to `Socket.tcp` (https://bugs.ruby-lang.org/issues/20108), it was pointed out that there should be a way to disable this feature (https://bugs.ruby-lang.org/issues/20108#note-7).
To address th... -
06:55 AM Misc #16124 (Rejected): Let the transient heap belong to objspace
- transient heap was removed.
-
- Matz said that `Ractor.local_storage_once(key){ init_block }` can be acceptable if returning the assigned value is out-of-scope, even if it returns assigned value.
other ideas:
* `Ractor.local_storage_fetch(key){}` from `Hash#fetch... -
04:37 AM Bug #20934: `UnboundMethod#bind_call` may cause "double free or corruption" with Ractor
- Thanks for your comment. It looks like a race condition between `rb_method_definition_release()` and `method_definition_addref()`.
Applying the following patch suppressed the problem.
```patch
diff --git a/vm_method.c b/vm_method.c
...
12/07/2024
-
02:54 PM Bug #20934: `UnboundMethod#bind_call` may cause "double free or corruption" with Ractor
- Nice find! The repro script tips off ASAN too:
```text
../build-dev/ractor-issue.rb:7: warning: Ractor is experimental, and the behavior may change in future versions of Ruby! Also there are many implementation issues.
=============... -
- When I call `UnboundMethod#bind_call` on both main Ractor and child Ractor, probable errors can be encountered.
Here is an issue reproduce script `ractor_issue.rb`.
```
def foo
10000.times do
Object.instance_method(:object_id)... -
10:02 AM Revision bd831bcc (git): [Bug #20929] Win32: Use `wcsftime`
- `_strftime_l` is not available on msvcrt that is still used by 32bit
mingw compiler. -
08:47 AM Bug #20933: Unexpected IO::Buffer::MaskError in IO::Buffer#xor!
- I just gave your branch a quick test and can confirm it fixes this issue. Thank you!
-
08:15 AM Revision c9bbf7e3 (git): [ruby/openssl] ssl: do not clear existing SSL options in SSLContext#set_params
- Apply SSL options set in DEFAULT_PARAMS without clearing existing
options.
It currently clears options in order to avoid setting one of the
options included in OpenSSL::SSL::OP_ALL unless explicitly specified,
namely OpenSSL::SSL::OP_DO... -
- Respect the SSL options set by default by SSL_CTX() and by the
system-wide OpenSSL configuration file.
OpenSSL::SSL::SSLContext#initialize currently adds OpenSSL::SSL::OP_ALL
on top of the default SSL options. Let's stop doing it.
Open... -
- https://github.com/ruby/openssl/commit/9120fcde6a
-
- It was originally sorted in alphabetical order, but it has been broken
over time. Let's fix it.
https://github.com/ruby/openssl/commit/974c67f38f -
- https://github.com/ruby/openssl/commit/85d6b7f192
-
- get_asn1obj() is used by several methods in OpenSSL::Timestamp to get
the string representation of an OID. On an error, such as memory
allocation failure, it can raise OpenSSL::X509::AttributeError. It
should be OpenSSL::Timestamp::Times... -
- Internals of OpenSSL::PKCS7 should be kept within ossl_pkcs7.c.
Add a new ossl_pkcs7_new() function for duplicating and wrapping an
OpenSSL PKCS7 object in OpenSSL::PKCS7. This follows the convention
used by other ossl_*_new() functions... -
- Follow-up commit https://github.com/ruby/openssl/commit/0789643d7333 (openssl: clear OpenSSL error
queue before return to Ruby, 2016-05-18). It should raise
OpenSSL::X509::StoreError instead of OpenSSL::X509::CertificateError.
https://g... -
- It should raise OpenSSL::Netscape::SPKIError instead of
OpenSSL::X509::CertificateError.
No test cases covered this because it only occurs in exceptional
cases, such as memory allocation failure.
https://github.com/ruby/openssl/commit/... -
- Fix a copy-and-paste error introduced in commit https://github.com/ruby/openssl/commit/74f6c6175688 (pkey:
allocate EVP_PKEY on #initialize, 2021-04-12).
It should raise OpenSSL::PKey::ECError instead of
OpenSSL::PKey::DSAError.
https:... -
07:52 AM Revision 54448857 (git): [ruby/openssl] make configs shareable when frozen
- https://github.com/ruby/openssl/commit/654cb22e21
-
- https://github.com/ruby/openssl/commit/3cc1825435
-
- https://github.com/ruby/openssl/commit/50599513cf
-
- Check the ID_callback_state ivar after SSL_read() or SSL_write()
returns, similar to what ossl_start_ssl() does.
Previously, callbacks that can raise a Ruby exception were only called
from ossl_start_ssl(). This has changed in OpenSSL 1... -
- ssl_servername_cb() is a callback function called from OpenSSL and Ruby
exceptions must not be raised from it. Allocate the Array within
rb_protect().
https://github.com/ruby/openssl/commit/3a2bf74d35 -
05:34 AM Feature #18930: Officially deprecate class variables
- I'm still against deprecating, either soft or hard, but I believe the errors could be improved.
```ruby
class A
def self.foo
p @@foo ||= rand
end
end
class B < A
p @@foo = 2
end
B.foo
```
In this code, the `@@foo` variable... -
02:26 AM Feature #18930: Officially deprecate class variables
- Can we formally document that class instance variables are soft deprecated or not recommended for use? In the Ruby community we often see new folk struggle greatly with them and have to recommend against their use over and over.
-
- I really appreciate your report.
I am considering using poll(2) or `rb_thread_fd_select` instead of select(2) for this issue.
(Since this feature currently lacks an implementation for Windows, choosing the former shouldn't pose a major...
12/06/2024
-
08:11 PM Bug #20933: Unexpected IO::Buffer::MaskError in IO::Buffer#xor!
- Thank you for this bug report. I have a fix here: https://github.com/ruby/ruby/pull/12284
-
- The following script raises `Mask overlaps source buffer! (IO::Buffer::MaskError)` most of the time when running it on my Ubuntu 24.04 machine.
"Most of the time" means this sometimes (20% - 30%) works without issue.
```ruby
a = IO::B... - 06:51 PM Revision 8ad6860f (git): [DOC] New homepage for docs.ruby-lang.org/en (#12227)
-
06:14 PM Bug #20930: Different semantics for nested `it` and `_1`
- I think it's OK for `it` to always use the innermost block, but it should be a conscious choice and ideally documented (maybe even part of `NEWS`).
If we go there, I do think we should use the same semantics for `_1`, `_2`, etc for cons... -
-
05:25 PM Revision 8502a549 (git): YJIT: small fix to stats formatting. (#12282)
- Avoid division by zero and NaN%, e.g.
num_throw_break: 0 ( NaN%)
num_throw_retry: 0 ( NaN%)
num_throw_return: 0 ( NaN%) -
04:22 PM Bug #20920: When loading a file, __FILE__ gets relative paths expanded only when they start with "./"
- This is very related to #16978
And all this started with introduction of `require_relative` and it is a mess since then. IMHO, the path expansion is evil. It prevents usage of symlinks, it is troublesome with modifications of `$LOAD_P... -
- It's interesting that this highlights the only case where `load` searches in a different path than `require`
if path is absolute
load/require absolute path --> __FILE__ is absolute
elsif path starts with "." or ".."
load/re... -
-
03:19 PM Revision 48443c02 (git): [rubygems/rubygems] Skip unresolved deps warning on `Gem::Specification.reset` on benign cases
- If `Gem::Specification.reset` is used, but there are still unresolved
dependencies, RubyGems prints a warning. There are though, certain cases
where the situation will not cause any issues.
One such case is when the unresolved dependenc... -
- https://github.com/rubygems/rubygems/commit/3976326a7b
-
-
- To "Core classes updates" from "Language changes".
-
-
- RDoc displays instance methods defined in `Kernel` as in `Object`.
This behavior may be somewhat questionable now, but for now it is what
it is. -
- Make existing (including newly added) classes, modules and methods
linkable. Oppositely enclose removed names in backticks. -
11:01 AM Revision 69fb4a5f (git): typeprof-757303fe8de0cf5e5583b4a76f8abbbd55c44776 is working with Windows
-
-
10:20 AM Bug #20690: URI.encode_www_form_component method escapes tilde when it's not supposed to
- While `URI.encode_www_form_component` might not deal with what RFC3986 defines as "Percent-Encoding", `URI.encode_uri_component` does (I think?) and that exhibits the same behavior:
```
3.3.4 :006 > URI.encode_uri_component("ruby~tes... -
10:19 AM Bug #20929: TestTime have an assertion different from current implementation.
- Thank you for your response.
Regarding Time#zone encoding, I am experimenting with it in my branch https://github.com/YO4/ruby/tree/tzname_utf8.
I found this issue in my research for that.
At present, the change to utf-8 causes th... -
- Applied in changeset commit:git|78762b52185aa80ee55c0d49b495aceed863dce2.
----------
[Bug #20929] Fix `assert_zone_encoding`
The default internal encoding is not taken into account to encode
timezone name. -
-
- The default internal encoding is not taken into account to encode
timezone name. -
09:48 AM Revision 58b4e249 (git): [MMTk/CI] Skip Ractor btests with MMTk
- currently these are flaky, so until we can make them more robust, we'll
skip them for MMTk CI -
-
-
07:09 AM Revision 5f653219 (git): [ruby/reline] Combine MAPPINGS(single byte input to symbol) with
- key_bindings(escape sequence to symbol)
(https://github.com/ruby/reline/pull/715)
https://github.com/ruby/reline/commit/6a7e249374 -
- Sorry for the late response.
I believe the issue you reported has been resolved by the following change, so please have a look.
https://github.com/ruby/ruby/pull/12153
Currently, this feature is once again enabled by default on the mas... -
03:32 AM Bug #20926 (Closed): shareable_constant_value: experimental_everything crashes with parse.y
- Applied in changeset commit:git|6ccaa37eb365afd6b01359e63dac85aef35987a5.
----------
[Bug #20926] Fix a crashes with `shareable_constant_value: experimental_everything` using parse.y's parser
https://bugs.ruby-lang.org/issues/20926 -
- https://github.com/ruby/ruby/pull/12275
-
- https://bugs.ruby-lang.org/issues/20926
- 03:04 AM Revision af2fc89f (git): Bump actions/cache in /.github/actions/setup/directories
- Bumps [actions/cache](https://github.com/actions/cache) from 4.1.2 to 4.2.0.
- [Release notes](https://github.com/actions/cache/releases)
- [Changelog](https://github.com/actions/cache/blob/main/RELEASES.md)
- [Commits](https://github.co... -
02:41 AM Revision 892c4628 (git): [DOC] Sort links [ci skip]
-
- I added build job for `--with-jemalloc` with macOS to GitHub Actions at https://github.com/ruby/ruby/pull/12273
-
-
-
12/05/2024
- 10:51 PM Revision b021f6f8 (git): Use symbol.h in vm.c to get macro for faster ID to sym (#12272)
- The macro provided by symbol.h uses STATIC_ID2SYM
when it can which speeds up methods that declare keyword args.
Co-authored-by: Alan Wu <XrXr@users.noreply.github.com>
Co-authored-by: Takashi Kokubun (k0kubun) <takashikkbn@gmail.com>
C... -
09:59 PM Bug #20932 (Closed): Socket fast_fallback segfaults when fds are > FD_SETSIZE
- When `Socket.tcp_fast_fallback = true` and a socket ends up with an FD over FD_SETSIZE (typically 1024), it results in a buffer overflow and crashes when running FD_SET before select.
It may be necessary to update ulimits to be above ... -
- We should use the rb_gc_enable/rb_gc_disable_no_rest APIs instead of
directly setting the ruby_disable_gc variable. -
- https://github.com/ruby/mmtk/commit/f62e5803f1
-
- darray.h no longer depends on internal/bits.h, so we can remove it.
-
07:00 PM Revision 305318ed (git): [rubygems/rubygems] Apply suggestions from code review
- https://github.com/rubygems/rubygems/commit/7c634ecd72
-
- Removes usage of these classes as ACE gadgets
See https://nastystereo.com/security/ruby-3.4-deserialization.html
Signed-off-by: Samuel Giddins <segiddins@segiddins.me>
https://github.com/rubygems/rubygems/commit/89ad04db86 -
06:42 PM Bug #20918 (Closed): Prism error indicates line number of `-e` that does not exist
- Applied in changeset commit:git|6877c38866b4213f5aa476223d21a4f4b5364247.
----------
[ruby/prism] Fix error messages for unterminated ( and {
If we hit an EOF token, and the character before the EOF is a newline,
we should make EOF tok... -
- If we hit an EOF token, and the character before the EOF is a newline,
we should make EOF token start at the previous newline. That way any
errors reported will occur on that line.
For example "foo(\n" should report an error on line 1 ... -
05:44 PM Bug #20930: Different semantics for nested `it` and `_1`
- > I think _1 semantics are slightly better, at least _1 behaves like a normal local variable declared in the outer block then.
Yeah but `_1` isn't declared in the outer block (or anywhere), so `_1` doesn't necessarily need to behave l... -
12:13 AM Bug #20930: Different semantics for nested `it` and `_1`
- Good catch. I see two problems.
One is an incompatibility with Prism's handling of `_1`. I think it should be handled as an error like parse.y. Especially when parsed with the 3.3 version's syntax, there is no other choice but an error:... -
- https://github.com/ruby/mmtk/commit/e4d6b56824
-
- We have name fragmentation for this feature, including "shared GC",
"modular GC", and "external GC". This commit standardizes the feature
name to "modular GC" and the implementation to "GC library". -
02:38 PM Bug #20904: 3.4.0-preview2: Building miniruby.exe fails for mswin32
- nobu (Nobuyoshi Nakada) wrote in #note-4:
> Weird.
> ...
Yes. Reproduced locally.
```
C:\usr\src\x86\ruby-3.4.0-preview2>nmake process.i
Microsoft (R) Program Maintenance Utility Version 14.42.34433.0
Copyright (C) Microsoft Co... -
12:31 PM Revision 26ab20fe (git): [ruby/rdoc] Workaround JRuby's jar-dependencies error and test
- failures on CI
(https://github.com/ruby/rdoc/pull/1225)
* Workaround JRuby's jar-dependencies error on CI
* Skip problematic encoding test for JRuby
https://github.com/ruby/rdoc/commit/3f9897d64c -
- (https://github.com/ruby/rdoc/pull/1218)
* Deprecate :main: directive
* Deprecate :title: direcive
* Update documentation
* Remove :main: directive's usage
* Update test cases
* Add '.rdoc_options' to suggested alternatives
https:... -
09:25 AM Bug #20929: TestTime have an assertion different from current implementation.
- > Maybe we should use the W API and encode it in UTF-8 ranter than the locale.
agreed. -
08:58 AM Revision 866f1a1f (git): Launchable: Stop recording tests temporarily (#12268)
- There is a system trouble in Launchable, so I'm going to stop recording tests temporarily in compilers.yaml
- 08:17 AM Revision 4336f413 (git): Update default gems list at 811bc15c75ff12c1a89ecac0af7d09 [ci skip]
-
08:16 AM Revision 5335b140 (git): array.c: Remove unused `rb_ary_verify` function
-
- https://github.com/ruby/json/commit/e1f6456499
-
- Fix: https://github.com/ruby/json/issues/715
The first byte check was missing.
https://github.com/ruby/json/commit/93a7f8717d - 05:59 AM Revision 4b850ea0 (git): Update bundled gems list at 0ef4a7d745f51751c12468d9452ede [ci skip]
-
05:59 AM Revision 0ef4a7d7 (git): Bundle RBS 3.7 (#12265)
12/04/2024
-
- As for the limitation of `in`, there is a more easy-to-understand explanation. Consider `foo(a in 1, 2, 3)`. This is very ambiguous because there are three possible interpretations: `foo((a in 1), 2, 3)`, `foo((a in 1, 2), 3)`, and `foo(...
-
11:04 PM Bug #20931: Using `in` as an expression requires extra parentheses
- That works for me - thanks for the explanation.
-
- I'm closing this since I'm pretty sure this isn't a bug. An imperfect explanation follows. Feel free to jump in if anyone has a better explanation.
To understand the precedence, note that `in` has a symbolic friend `=>`, and much like h... -
- TBH - I'm not sure if this is a bug or not - but it certainly surprising behavior and I'd at least like to understand it.
Given a hash t - that can be pattern matched: `t = {a: 1, b:1 }`
``` ruby
r = t in {a: 1, c:1 } # returns `f... -
- When setting len to X we only need to grow the array
if len is bigger than capa. If they're equal we don't need to
increase capacity. - 09:34 PM Revision 1c4dbb13 (git): YJIT: Generate specialized code for Symbol for objtostring (#12247)
- * YJIT: Generate specialized code for Symbol for objtostring
Co-authored-by: John Hawthorn <john@hawthorn.email>
* Update yjit/src/codegen.rs
---------
Co-authored-by: John Hawthorn <john@hawthorn.email>
Co-authored-by: Maxime Cheval... -
-
- With `--parser=parse.y`:
```
$ ruby --parser=parse.y -ve '[1].each { p it; [5].each { p it } }'
ruby 3.4.0dev (2024-12-04T19:29:24Z master 3c91a1e5fd) [x86_64-linux]
1
5
$ ruby --parser=parse.y -ve '[1].each { p _1; [5].each { p _1... -
- With --parser=parse.y:
```
$ ruby --parser=parse.y -ve '[1].each { p it; [5].each { p it } }'
ruby 3.4.0dev (2024-12-04T19:29:24Z master 3c91a1e5fd) [x86_64-linux]
1
5
$ ruby --parser=parse.y -ve '[1].each { p _1; [5].each { p _1... -
-
- There's no case for when RUBY_MSAN_ENABLED, so the macro ends up doing
nothing when it should instead have __attribute__((__no_sanitize__("memory"))). -
- Partially: https://github.com/ruby/prism/issues/2123
https://github.com/ruby/prism/commit/1ffd693f9b -
- Partially: https://github.com/ruby/prism/issues/2123
https://github.com/ruby/prism/commit/a78da01ef6 -
- Partially: https://github.com/ruby/prism/issues/2123
https://github.com/ruby/prism/commit/2f473b0713 -
- Partially: https://github.com/ruby/prism/issues/2123
https://github.com/ruby/prism/commit/7be164e0b7 -
- kddnewton (Kevin Newton) wrote in #note-3:
> I looked into this this morning, it looks like ruby.c is automatically concatenating a \n onto the -e script here: https://github.com/ruby/ruby/blob/f43585b02c3634ab9a4e54049b08e04ab1a640fd/r... -
02:58 PM Bug #20918: Prism error indicates line number of `-e` that does not exist
- I looked into this this morning, it looks like ruby.c is automatically concatenating a \n onto the -e script here: https://github.com/ruby/ruby/blob/f43585b02c3634ab9a4e54049b08e04ab1a640fd/ruby.c#L1303. Is this desired behavior?
-
- ko1 (Koichi Sasada) wrote in #note-7:
> On `x[y()] ||= z()`, `z()` can change the context and it violates atomicity.
Hmm, I don't think so? Of course for the regular `||=` that would be the case, but in something like `x.assign_if_un... -
- Dan0042 (Daniel DeLorme) wrote in #note-6:
> Would it be possible to make `Ractor[:mtx] ||= Mutex.new` behave in an atomic way?
On `x[y()] ||= z()`, `z()` can change the context and it violates atomicity. -
- We can use the BUILDING_SHARED_GC flag to check if we're building gc_impl.h
as a shared GC or building the default GC. - 12:33 PM Revision f43585b0 (git): Update default gems list at 834d68238cfb4ffd701c65820c6d22 [ci skip]
- 12:32 PM Revision 834d6823 (git): [ruby/did_you_mean] Bump version to 2.0.0
- https://github.com/ruby/did_you_mean/commit/1cce337962
-
- https://github.com/ruby/did_you_mean/commit/e11bf81438
-
- Applied in changeset commit:git|86c01b6aa0833e1bddda6ba8315c9d414aef0f76.
----------
[Bug #20928] Fix build when `malloc_usable_size` is available
Copy from gc/default/default.c and revert the part of 51bd81651794. -
- Copy from gc/default/default.c and revert the part of 51bd81651794.
-
08:35 AM Revision 4d460944 (git): [rubygems/rubygems] Rework `Bundler.which` tests
- Refactor to use real test cases rather than mock.
Add relative path tests wich `Dir.chdir`.
https://github.com/rubygems/rubygems/commit/ed556a0a53 -
- https://github.com/rubygems/rubygems/commit/ed5b847f03
-
- https://github.com/rubygems/rubygems/commit/c982085f86
-
- The functions dereference `*dead_entry` without a NULL check
-
- https://github.com/ruby/shellwords/commit/2c7ae1b76c
-
- Since ruby 2.3, a file opened with `File::SHARE_DELETE` and
`File::BINARY` can be renamed or removed.
https://github.com/ruby/logger/commit/7b6146fee6 -
- https://github.com/ruby/logger/commit/f904ad2f7c
-
- Indeed, that assertion is incorrect.
But the locale is not the correct/expected encoding always on Windows.
For instance, in Japanese edition, `tm_zone` is always CP932.
```
> chcp.com 932
現在のコード ページ: 932
> ...
#<Encoding:Windows-31... - 07:02 AM Revision c516669f (git): Update bundled gems list as of 2024-12-04
-
-
- Coverity Scan alerts `for(i, j=0;...)` as a misuse of comma expression.
-
- maybe out of date
-
- Try with `GC.config`
-
-
-
- Get rid of repeated exec XRUBY recursively.
-
- In this context, `th` must not be NULL
- 03:06 AM Revision 200f93b0 (git): Bump github/codeql-action from 3.27.5 to 3.27.6
- Bumps [github/codeql-action](https://github.com/github/codeql-action) from 3.27.5 to 3.27.6.
- [Release notes](https://github.com/github/codeql-action/releases)
- [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md... -
- out of date
-
- https://github.com/ruby/setup-ruby has `debug` target.
-
- out of date
-
- out of date
-
- out of date
-
- out of date
-
- too old.
-
- The evaluation order of C arguments is unspecified.
`RSTRING_LEN(value)` would fail if the conversion to a String by
`StringValuePtr(value)` is not done yet.
Coverity Scan found this issue.
https://github.com/ruby/psych/commit/d1e6bf323a
12/03/2024
-
- (https://github.com/ruby/irb/pull/1039)
https://github.com/ruby/irb/commit/9eb14a3a0b -
-
- The evaluation order of C arguments is unspecified.
`RSTRING_LEN(str)` would fails if the conversion to a String by
`StringValuePtr` is not done yet.
Coverity Scan found this issue. -
- Partially fixes: https://github.com/ruby/prism/issues/2123
https://github.com/ruby/prism/commit/f1f8776973 -
- Partially: https://github.com/ruby/prism/issues/2123
https://github.com/ruby/prism/commit/3c01cc7c77 -
- Partially: https://github.com/ruby/prism/issues/2123
https://github.com/ruby/prism/commit/649ef29c29 -
-
- In some locations we were using shared->lock and in others
&shared->lock, and we were leaking the allocated memory. -
- test/ruby/test_time.rb have following assersion function.
```ruby
def assert_zone_encoding(time)
zone = time.zone
assert_predicate(zone, :valid_encoding?)
if zone.ascii_only?
assert_equal(Encoding::US_ASCII, zon... -
- It should work on Windows, hopefully
-
09:24 AM Bug #20928 (Closed): Current 3.4-dev cannot be built with jemalloc activated in macOS
- Today I found that the current 3.4-dev is unable to build with jemalloc activated, while 3.3.4 or any lower versions can be build as usual with or w/o jemalloc activated.
* macOS Sequoia: 15.1.1 (M3 Chip)
* env (FYI: `--with-opt-di... -
-
- I merged https://github.com/ruby/timeout/pull/51 now. Thank you.
-
- We discussed this with Matz at last developer meeting.
He said "Let's raise an `ArgumentError` against negative value". - 06:49 AM Revision f6b62d00 (git): [ruby/timeout] removed the non numeric check
- https://github.com/ruby/timeout/commit/7d2af46a00
Co-authored-by: Jeremy Evans <code@jeremyevans.net> - 06:49 AM Revision 7dc7aab4 (git): [ruby/timeout] updated doc string
- https://github.com/ruby/timeout/commit/4be6423de4
Co-authored-by: Jeremy Evans <code@jeremyevans.net> - 06:49 AM Revision e97225b1 (git): [ruby/timeout] updated tests
- https://github.com/ruby/timeout/commit/c6d121aa18
- 06:49 AM Revision b156efc2 (git): [ruby/timeout] updated doc and kept the nil compatiability
- https://github.com/ruby/timeout/commit/f992632cf3
- 06:49 AM Revision e7dd185e (git): [ruby/timeout] refactor the change to raise for nil and type-errror and added tests
- https://github.com/ruby/timeout/commit/ffc8d7c003
- 06:49 AM Revision 0839eae2 (git): [ruby/timeout] refactor the change to keep the compatability with nil and type-errror and added tests
- https://github.com/ruby/timeout/commit/e8a7dbdb87
- 06:49 AM Revision 0f2cd39e (git): [ruby/timeout] refactor the change to keep the compatability with nil and type-errror and added tests
- https://github.com/ruby/timeout/commit/8342544979
- 06:49 AM Revision 203a0234 (git): [ruby/timeout] added the check for negative sec
- https://github.com/ruby/timeout/commit/8e57887eee
-
-
- 05:06 AM Revision f713b870 (git): Update default gems list at ddf0080fd3d82e84aec48894d4e27f [ci skip]
-
- https://github.com/ruby/io-console/commit/467508a0c6
-
- https://github.com/ruby/etc/commit/8d585ea0c9
-
- On my environment with `sudo ufw default reject outgoing`,
outgoing packets are filtered without allow rules. - 04:53 AM Revision 9297a4cb (git): Update default gems list at e34163d7fe8d416f9952d775eb743b [ci skip]
-
- https://github.com/ruby/pp/commit/979f9d972d
- 04:39 AM Revision e16f3ad6 (git): Update default gems list at 9bd1e6ee04ed8f0cc88da3366534e0 [ci skip]
-
- https://github.com/ruby/io-nonblock/commit/16727a8ab3
- 03:12 AM Revision 8b987ed9 (git): Update default gems list at 043f26edee38fb52fe43e208a7ad57 [ci skip]
-
- https://github.com/ruby/error_highlight/commit/a8e9eb7f2f
-
-
-
- After reading the instruction sequences, I realized that Ruby 3.3 has an odd behavior with `shareable_constant_value: experimental_everything`. I filed an issue about it here: https://bugs.ruby-lang.org/issues/20927
I personally thin... -
- I created a bug for the parse.y version here: https://bugs.ruby-lang.org/issues/20926
The example @mame provides works on Ruby 3.3. I think it's supposed to emit instructions like this:
```
$ ruby -v --dump=insns test.rb
ruby 3.... -
-
- 02:09 AM Revision 326a6cbf (git): * 2024-12-03 [ci skip]
-
-
-
-
-
- This reverts commit 0fe82ae087130d7f360cc0607be93995cedbdb16.
-
- kddnewton (Kevin Newton) wrote in #note-7:
> The Prism portion should be fixed by https://github.com/ruby/prism/pull/3270.
Does Prism support older than VS 2015 that is the minimum version for ruby 3.4?
VS 2015 at least supports the... -
-
-
- These two programs produce different results
```ruby
# shareable_constant_value: experimental_everything
C = { **{ } }
p C
```
```ruby
C = { **{ } }
p C
```
The first one prints this:
```
$ ruby test.rb
{nil=>{... -
- This program crashes with parse.y as the parser:
```
./miniruby --dump=insns --parser=parse.y -v -e'# shareable_constant_value: experimental_everything
C = { **{ } }'
```
Backtrace from ...
12/02/2024
-
10:08 PM Revision af5c34fb (git): [ruby/rdoc] Prefer String#ord to #codepoints[0]
- (https://github.com/ruby/rdoc/pull/1220)
https://github.com/ruby/rdoc/commit/09d7f35420
Co-authored-by: Nobuyoshi Nakada <nobu@ruby-lang.org> -
- argument
(https://github.com/ruby/rdoc/pull/1222)
It is necessary for ClassModule's instance variable @superclass to
always be a String (or nil) so that the class can be saved with
`#marshal_dump` and loaded with `#marshal_load`.
Howev... -
08:28 PM Revision d588a1c8 (git): Correct order of listed methods
-
- Instead cast it inline to a double on Windows.
https://github.com/ruby/prism/commit/9064d872aa -
-
- I'm fine supporting this, but I'm not sure what the behavior should be since the current compiler just segfaults. What is the behavior if the value being splatted isn't an empty hash?
-
- Agreed this is a bug. For additional context, this is the same on parse.y and prism.
-
- The Prism portion should be fixed by https://github.com/ruby/prism/pull/3270.
-
- Partially fixes: #3171
https://github.com/ruby/prism/commit/d0d9699c27 -
- Partially fixes: https://github.com/ruby/prism/issues/3171
https://github.com/ruby/prism/commit/5c33fa5a1a -
- Fixes: https://github.com/ruby/prism/issues/3109
https://github.com/ruby/prism/commit/9ed989c30d -
- ```
❯ ruby --parser=prism --dump=parsetree -e "foo in *1"
ruby: -e:1: syntax error found (SyntaxError)
> 1 | foo in *1
| ^ unexpected integer, expecting end-of-input
2 |
``` -
- Partially fixes: https://github.com/ruby/prism/issues/2123
https://github.com/ruby/prism/commit/b8f40988ab -
- Partially fixes: https://github.com/ruby/prism/issues/2123
https://github.com/ruby/prism/commit/396c6d4340 -
- Partially fixes: https://github.com/ruby/prism/issues/2123
https://github.com/ruby/prism/commit/27f13fabc6 -
- Partially fixes: https://github.com/ruby/prism/issues/2123
https://github.com/ruby/prism/commit/1388ca389e -
- Partially fixes: https://github.com/ruby/prism/issues/2123
https://github.com/ruby/prism/commit/b1c2f323f9 -
- Partially fixes: https://github.com/ruby/prism/issues/2123
https://github.com/ruby/prism/commit/8353be1dfe -
- Partially fixes: https://github.com/ruby/prism/issues/2123
https://github.com/ruby/prism/commit/9c0ef71449 -
- Partially fixes: https://github.com/ruby/prism/issues/2123
https://github.com/ruby/prism/commit/480897eccf -
- Partially fixes: https://github.com/ruby/prism/issues/2123
https://github.com/ruby/prism/commit/75d1bde6cc -
- Partially fixes: https://github.com/ruby/prism/issues/2123
https://github.com/ruby/prism/commit/d1570f2e06 -
- Partially fixes: https://github.com/ruby/prism/issues/2123
https://github.com/ruby/prism/commit/145ae8f993 -
- (https://github.com/ruby/reline/pull/790)
Minimize the call of STDOUT.write
This will improve rendering performance especially when there is a busy thread `Thread.new{loop{}}`
https://github.com/ruby/reline/commit/a6fe45f5ba -
- Would it be possible to make `Ractor[:mtx] ||= Mutex.new` behave in an atomic way? Like maybe add a special `[]||=` method which is automatically called such that `Ractor[:mtx] ||= Mutex.new` becomes equivalent to `Ractor[:mtx] || Racto...
-
- https://github.com/rubygems/rubygems/commit/722d4c6926
- 12:47 PM Revision 8f57204c (git): Avoid test failures on hosts that only support IPv4 (#12213)
- To verify the behavior of HEv2, some tests were prepared. But unexpected failures occur in certain environments.
This happens in environments where "localhost" resolves only to an IPv4 address during tests that verify connections to IPv6... - 08:43 AM Revision c6b8a52f (git): Update default gems list at 2b895a7ad53d025e91566c4f51eac3 [ci skip]
-
- https://github.com/ruby/net-http/commit/6475fa68ba
- 08:04 AM Revision 9a005ad5 (git): Update default gems list at 157fe74795b151413150b0f79b9b8b [ci skip]
-
- https://github.com/ruby/logger/commit/2d07f086f8
-
- https://github.com/ruby/io-console/commit/fdad351501
- 07:52 AM Revision 10900701 (git): Update default gems list at 229592f175eab0a42071bdd237107b [ci skip]
-
- https://github.com/ruby/date/commit/a3295ad262
- 07:45 AM Revision 10b16705 (git): Update default gems list at ff52431ee5a9bdefa8240e69ea4220 [ci skip]
-
- https://github.com/ruby/securerandom/commit/53f97f3151
-
-
- https://github.com/ruby/securerandom/commit/40ddef8a83
-
- https://github.com/ruby/securerandom/commit/90c7e390f5
-
- https://github.com/ruby/securerandom/commit/bb1c078e9f
-
- https://github.com/ruby/securerandom/commit/da7d324c7d
-
- https://github.com/ruby/io-console/commit/aa79919f79
-
- Truffle ruby seems to lack it.
https://github.com/ruby/io-console/commit/839c1e80eb -
-
- 01:50 AM Revision 9a7f050e (git): [ruby/strscan] test: don't omit "(...)" for method calls that have at least one argument
- https://github.com/ruby/strscan/commit/dddae9c99a
-
- (https://github.com/ruby/strscan/pull/117)
Profiling shows a lot of time spent in various encoding check functions.
I'm working on optimizing them on the Ruby side, but if we assume most
strings are one of the simple 3 encodings, we can... -
- Followup: https://github.com/ruby/strscan/pull/115
`scan_integer` is now implemented in Ruby as to efficiently handle
keyword arguments without allocating a Hash. Given the goal of
`scan_integer` is to more effciently parse integers wit... -
- test
(https://github.com/ruby/strscan/pull/118)
https://rubyci.s3.amazonaws.com/debian11/ruby-master/log/20241128T153002Z.log.html.gz
```
/home/chkbuild/chkbuild/tmp/build/20241128T153002Z/ruby/test/strscan/test_stringscanner.rb:908: wa... -
-
- This reverts commit 2923f42ed7622f6310c63aab4c0abf05402f9a04.
https://github.com/ruby/actions/actions/runs/12108034481/job/33755653615#step:23:1031
```
/home/runner/work/actions/actions/snapshot-master/lib/rdoc/code_object.rb:322:in 'R... -