Activity
From 09/10/2024 to 09/16/2024
09/16/2024
-
08:35 PM Feature #20309: Bundled gems for Ruby 3.5
- Eregon (Benoit Daloze) wrote in #note-34:
> There is an additional issue with making fiddle a bundled gem: it means any usage now must have libffi headers available or it will fail to install.
> ...
I don't think it is bad idea to star... -
10:27 AM Feature #20309: Bundled gems for Ruby 3.5
- There is an additional issue with making fiddle a bundled gem: it means any usage now must have libffi headers available or it will fail to install.
Before, it would just work because fiddle would have been built when CRuby was built.
... -
07:58 PM Revision 50d4840b (git): Move desired_compaction_pages_i inside of GC_CAN_COMPILE_COMPACTION
- Fixes the following warning on WebAssembly:
gc/default.c:7306:1: warning: unused function 'desired_compaction_pages_i' [-Wunused-function]
desired_compaction_pages_i(struct heap_page *page, void *data) -
07:55 PM Bug #20747 (Closed): [prism] regression in retry precedence
-
- I have opened a PR to fix this: https://github.com/ruby/prism/pull/3073.
-
08:26 AM Bug #20747 (Closed): [prism] regression in retry precedence
- Since prism has been made the default, our test suite now fail to boot with the following error:
```ruby
syntax error found (SyntaxError)
298 | raise e
299 | else
> 300 | retry
| ^~... -
- Fixes [Bug #20747]
https://github.com/ruby/prism/commit/d3194715a9 -
- Applied in changeset commit:git|2ea1950510003dbce5a761a712039ed69fa499f2.
----------
[ruby/prism] Do not leak explicit encoding
Fixes [Bug #20744]
https://github.com/ruby/prism/commit/f1b8b1b2a2 -
- I have opened a PR to fix this.
https://github.com/ruby/prism/pull/3071 -
- Thank you for the report, I will take a look.
-
07:07 AM Bug #20744: syntax error found (SyntaxError) `UTF-8 mixed within US-ASCII source` reported Ruby with Prism parser
- I'm unsure if this is the same case as Rails, but I found a reproduce code.
``` ruby
# encoding: US-ASCII
str = String.new("hello \xFC", encoding: Encoding::ISO_8859_1).encode(Encoding::UTF_8)
puts str =~ /hello \u{fc}/
```
#... -
04:33 AM Bug #20744 (Closed): syntax error found (SyntaxError) `UTF-8 mixed within US-ASCII source` reported Ruby with Prism parser
- I'm reporting this issue based on Rails Nightly CI against Ruby 3.4.0dev.
https://buildkite.com/rails/rails-nightly/builds/1023#0191ed31-1d77-4705-ab65-cecab76e2c88/1175-1209
I have not able to create a minimum test case without Rails... -
- Fixes [Bug #20744]
https://github.com/ruby/prism/commit/f1b8b1b2a2 -
- These functions are not used publicly, so we don't need to export them.
-
-
- I have submitted a PR that will fix this https://github.com/ruby/ruby/pull/11632.
-
- Fixes [Bug #20741]
-
05:36 PM Revision 6c4ce726 (git): [ruby/irb] Use InstructionSequence#script_lines to get method source
- (https://github.com/ruby/irb/pull/1005)
It works with both prism and parse.y
https://github.com/ruby/irb/commit/bcfaa72d5a -
04:33 PM Revision 1c3981cb (git): [DOC] Tweaks for Array#select!
-
-
04:14 PM Misc #20717: DevMeeting-2024-10-03
- * [Misc #20728] Add eileencodes as a core committer
* She's made many useful contributions
* She's currently helping to maintain Prism / Prism Compiler and it would be helpful if she can merge her own commits -
- * [Misc #20746] Request to migrate the `json` gem from `flori/json` repository to `ruby/json` (byroot)
* Current maintainers don't have full administrative rights over the repo, which is problematic.
* We've been trying to contact ... -
03:54 PM Feature #20742: Trying to assign to a variable in statement modifier should emit a warning
- Actually, the pattern is fairly common, I should have searched for `unless` usage in addition to `if`:
```
lib/rdoc/code_object/any_method.rb: return nil unless klass = @store.find_class_or_module(klass_name)
lib/rdoc/code_obje... -
- Eregon (Benoit Daloze) wrote in #note-2:
> jeremyevans0 (Jeremy Evans) wrote in #note-1:
> ...
The pattern is used in the standard library. Here's a list of assignments in post-conditionals that don't use parentheses around the assign... -
- jeremyevans0 (Jeremy Evans) wrote in #note-1:
> Assigning in post-conditionals is a fairly common in Ruby.
Is it? I don't think I've seen that often or maybe even never.
-
- Applied in changeset commit:git|1e52dde82af10f2a2ec648b34dce30bec4154245.
----------
[PRISM] Match defined behavior for explicit block
Fixes [Bug #20748] -
03:29 PM Bug #20748: Issue with defined? given method call with block in prism compiler
- I agree it's weird but it could cause an incompatibility I guess, `defined?()` is a weird one for sure.
-
- I have opened a PR for this to match the behavior exactly, but I will say I think Prism's behavior is actually correct here. Right now compile.c results in:
```ruby
puts defined?(undefined_method(){}) # => "expression"
puts defined?... -
- test.rb
```ruby
puts defined?(undefined_method(){})
```
```
./ruby --parser=parse.y -I../ruby/lib -I. -I.ext/x86_64-linux -I.ext/common -r./x86_64-linux-fake ../ruby/test.rb
expression
```
```
./ruby --parser=prism -I../ruby... -
- Fixes [Bug #20748]
-
-
06:42 AM Bug #20237: Unable to unshare(CLONE_NEWUSER) in Linux because of timer thread
- Thank you @ko1 for sharing the current situation. I'm fine with closing this ticket as it is due to the design decision and (AFAIK) the original behavior had never been documented.
-
- test.rb:
```ruby
p = Proc.new
```
```
./ruby --parser=parse.y -I../ruby/lib -I. -I.ext/x86_64-linux -I.ext/common -r./x86_64-linux-fake ../ruby/test.rb
../ruby/test.rb:1:in 'Proc.new': tried to create Proc object without a bloc... -
-
-
-
01:13 PM Revision f4f46af9 (git): Complete spec
- Co-authored-by: Vít Ondruch <vondruch@redhat.com>
-
- By the time `cached_gem` is called, default gem cache has already been
handled. So no need to try redownload it again, it's enough to check the
cache location directly.
https://github.com/rubygems/rubygems/commit/70e10236b6 -
-
- +1, as I wrote in https://github.com/flori/json/issues/591 I think this is important for many reasons.
-
- ### Context
The `json` gem, which is part of Ruby's default gems, is the only default gem (aside from `rubygems` itself) for which the source repository isn't under the `ruby/` organization.
@naruse and @hsbt, the two maintainers h... -
- https://github.com/rubygems/rubygems/commit/edbb2e3475
-
- https://github.com/rubygems/rubygems/commit/174a8e5284
-
- `#set_string` in combination with `.for` with a block has the same problem.
```shell-session
% docker run --platform=linux/amd64 --rm ruby:3.3.5-alpine3.20 ruby -e 's=+"0123456789"; IO::Buffer.for(s) {|b| b.set_string(s, 3, 7, 0) }; ... -
- The current implementation of `IO::Buffer#copy` uses `memcpy` to copy data between the two memory regions. `memcpy` has a requirement that the source and destination must not overlap; otherwise the behavior is undefined.
When copying ... -
01:35 AM Feature #20738: Removing a specific entry from a hash literal
- It would be better to explain the motive. This is an appropriate code.
``` ruby
{
foo: 1
bar: 2
}
```
This is not a mistake, but it's a circuitous code.
``` ruby
h = {}
h[:foo] = 1
h[:bar] = 2
h
```
The gist of ... -
- I would like to offer that as I used a simple grep pattern, I could only find simple examples. I wanted to show that this is not as rare as it seems.
09/15/2024
-
07:15 PM Bug #20726: Issue with hash without braces when assigned to constant with ractor literals
- This problem was not reproduced with `--parser=prism`, but with `--parser=parse.y`.
```ruby
# shareable_constant_value: literal
# test.rb
puts RUBY_DESCRIPTION
A = [a: 1]
p A
```
```shell
$ ruby --parser=prism test.rb
r... -
06:07 PM Bug #20743: ruby doesn't properly split RUBY_DEBUG_LOG_FILTER into items
- Apparently introduced in the following commit:
https://github.com/ruby/ruby/commit/5a4f997b2e8e819ed40731cd769826112072a9d4#diff-1cae4f3b0e13ea38a331366fa5370f5648b2c37090a19e8fba9b8e921c36f505R369 -
- ```
$ docker run --rm alpine:3.20.3 sh -euxc '
apk add git build-base autoconf ruby yaml-dev zlib-dev openssl-dev libffi-dev
git clone https://github.com/ruby/ruby
cd ruby
git checkout 532af89e3b5b78dd3a6fe29c6cc64ad... -
- > There are several Rails codes that can be improved with this feature.
As one of the maintainer of the code you linked to, I agree with @jeremyevans0 that it's currently fine as it is. I wouldn't use such feature if it was added. -
- ursm (Keita Urashima) wrote in #note-9:
> There are several Rails codes that can be improved with this feature. In my opinion, it is especially useful in multiple situations, such as generating JSON responses and constructing HTTP reque... -
- Eregon (Benoit Daloze) wrote in #note-8:
> I don't think it's very frequent to need this to warrant a syntax change either.
There are several Rails codes that can be improved with this feature. In my opinion, it is especially useful ... -
- Assigning in post-conditionals is a fairly common in Ruby. If this is to be a warning, it would have to be limited to cases where the variable being assigned in the post-conditional was not in scope before the post-conditional, and is a...
-
05:42 PM Feature #20742 (Open): Trying to assign to a variable in statement modifier should emit a warning
- There is an example in Control Expressions documentation:
```
p a if a = 0.zero? # raises NameError “undefined local variable or method ‘a’”.
```
However, if we had already defined `a` there would be no exception raised. If one u... -
- I think good error recovery is key to have helpful error messages when writing Ruby code.
Maybe one way here is to not show warnings if there are any errors?
OTOH I think it is not a big usability problem, warnings appear first and t... -
12:51 AM Bug #20736: prism emits wrong warnings in syntax-error code
- https://github.com/ruby/ruby/pull/11626
-
- I wonder if error recovery is needed in the interpreter's parser. It might be a benefit to be able to output almost all syntax errors in one run. However, I am not sure about the benefit, given the such confusing warnings.
Well, let's... -
- > prism?
Yes:
```
$ ./miniruby --parser=parse.y -we 'p RubyVM::InstructionSequence.compile("42").eval'
42
$ ./miniruby --parser=prism -we 'p RubyVM::InstructionSequence.compile("42").eval'
<compiled>:1: warning: possibly useles... -
- ```
$ ./local/bin/ruby -we 'p RubyVM::InstructionSequence.compile("42").eval'
<compiled>:1: warning: possibly useless use of a literal in void context
42
``` -
-
09/14/2024
-
- I don't think it's OK to magically drop entries from a literal based on some value, it's way too surprising.
Notably this would make the capacity of the literal potentially wrong, etc.
And of course `Hash::DROP` could leak into some vari... -
- I believe that the following two points will prevent the same problems as in the past:
1. Use a value that is never used (e.g., Hash::DROP) instead of nil.
2. Special treatment of “special value” only if the hash is constructed with ... -
- History. Long ago in Ruby, such a special value actually existed. It was `nil`.
```ruby
# ruby 1.4.6
h = { 1 => 2 }
p h #=> {1=>2}
# This removes the key 1
h[1] = nil
p h #=> {}
```
However, there were more and more ... -
07:54 AM Bug #20730: LoadError if Rakefile has shebang
- `ruby` command handles a shebang, but it is not a part of the Ruby syntax.
Parsers should not consider shebang lines.
09/13/2024
-
- Right now Prism is lexing `9a` as an integer and then an identifier. So it's effectively parsing it as `1; 2; 9; a`. That's why it's warning that `9` is a useless literal. I could change this in the parser to parse it instead as a missin...
-
- Although I can understand the technical reason, I still feel a bit uncomfortable when the warning says “use of a literal” since `9a` is clearly not a literal to the human eye.
As a practical matter, this behavior causes a lot of warni... -
-
- This is because Prism recovers from the syntax error. For example:
```ruby
eval("1; 2; 9a; 3; 4; 5; 9b")
```
with Prism this will give:
```
(eval at test.rb:1):1: warning: possibly useless use of a literal in void context
(e... -
- ```
$ ./local/bin/ruby -w --parser=parse.y -e 'begin eval("0a"); rescue SyntaxError; end'
$ ./local/bin/ruby -w --parser=prism -e 'begin eval("0a"); rescue SyntaxError; end'
(eval at -e:1):1: warning: possibly useless use of a literal... -
- https://github.com/ruby/prism/commit/4ed7de537b
-
- Okay, makes sense. Maybe if/when ractors are used more I'll take a look at this again.
-
- https://github.com/ruby/prism/commit/0b527ca93f
-
-
- I have opened https://github.com/ruby/ruby/pull/11622 to fix this.
-
- ```
$ ./local/bin/ruby -w --parser=parse.y -e 'def foo(&) = nil; foo &:bar'
$ ./local/bin/ruby -w --parser=prism -e 'def foo(&) = nil; foo &:bar'
-e:1: warning: ambiguous `&` has been interpreted as an argument prefix
``` -
- Applied in changeset commit:git|9afc6a981deae6e23d938cf5c2c4baadfeaafdb1.
----------
[PRISM] Only parse shebang on main script
Fixes [Bug #20730] -
- I have opened https://github.com/ruby/ruby/pull/11617 to fix this.
-
01:19 AM Bug #20730 (Closed): LoadError if Rakefile has shebang
- `LoadError` exception will be raised when invoke the rake task with latest ruby 3.4-dev.
### Reproduce code
Here is example code.
```ruby
#!/usr/bin/env rake
p "Hello"
```
### Result
```
$ ruby -v
ruby 3.4.0dev (2024-09... -
- Fixes [Bug #20735]
-
- Regarding `irb`, I find it concerning that we need to add code like this: https://github.com/ruby/ruby/blob/9afc6a981deae6e23d938cf5c2c4baadfeaafdb1/prelude.rb#L12-L44. Those are internals of Bundler that are likely to break, and I can't...
-
- Agreed, I didn't expect new warnings in 3.3.5 when 3.3.4 did not warn, and extra warnings can break CI (e.g. #20713).
-
05:57 AM Bug #20737 (Closed): Accidentally changed warning target on Ruby 3.3
- https://github.com/ruby/ruby/pull/11613
-
04:10 AM Bug #20737: Accidentally changed warning target on Ruby 3.3
- Makes sense. Let's revert that back to the Ruby 3.3.4 one in Ruby 3.3.6.
-
- I heard that concern from yhonda.
I request to backport bundled_gems.rb that is same version of the current master. After that, Ruby 3.3.5 show warnings when some default gems was loaded.
https://github.com/ruby/ruby/blob/ruby_3_3/... -
- I think it's a real issue and sometimes valuable to fix (it hurts the coverage of tests * flags).
#6648 could be helpful to automatically inherit passed flags.
Alternatively, we could ensure we only pass options for tests through `RUBYOP... -
- I'm not sure if anything needs to change here, but I wanted to report this in case anyone had any particular ideas. When running the ruby/ruby test suite, lots of tests call `EnvUtil.invoke_ruby` directly or indirectly through `assert_in...
-
-
- I have opened https://github.com/ruby/ruby/pull/11620 to fix this.
-
-
- @mame
Thanks! -
- The wrong warning with `rss` gem is a different issue. I have created a separate ticket #20732.
-
- I also have similar issues with `rss`.
```
/Users/hsbt/Documents/github.com/ruby/ruby/gems/src/rss/lib/rss/1.0.rb:81: warning: mismatched indentations at ‘else’ with ‘if’ at 79
(snip)
```
https://github.com/ruby/rss/blob/master/... -
- ### Steps to reproduce
1. Create a `case_sample.rb` file
```
foo = :bar
case foo
when :bar
p 'foo is :bar'
when :baz
# do something
else
# do something
end
```
2. Run this file against the latest Ruby 3.4.0... -
- Fixes [Bug #20730]
-
- Fixes [Bug #20731]
-
- PR here: https://github.com/ruby/ruby/pull/11621
-
- I found a coding issue in prism_compile.c but I can't find a bug that would result from it.
The `current_block` is not set back when a block is given. -
- Applied in changeset commit:git|74f315c3f5908512dfdeeab2dd76d93e98149769.
----------
[PRISM] Turn off mismatched indentation warnings in eval
Fixes [Bug #20732] -
- I have opened https://github.com/ruby/ruby/pull/11618 to fix this.
-
- ```ruby
eval(<<-EOC)
if @check
end
EOC
```
```
$ ruby --parser=parse.y -w t.rb
$ ruby --parser=prism -w t.rb
(eval at t.rb:1):2: warning: mismatched indentations at 'end' with 'if' at 1
```
This issue actually occurs in ... -
- Fixes [Bug #20732]
-
03:05 PM Revision 353997dd (git): [ruby/prism] Refactor and move common node flags count into a constant to reuse in templates
- https://github.com/ruby/prism/commit/c20bf05ecc
-
- https://github.com/ruby/prism/commit/dbb7e0a44e
-
- With the previous idea, I can't have both removing entries and returning nil depending on the condition.
``` ruby
# If user.child? is true and user.parent is nil, I want parent_name: nil, but the entry is removed.
{
?parent_name:... -
- nobu (Nobuyoshi Nakada) wrote in #note-1:
> "A special value" doesn't feel like a good idea to me.
Hmmm, does that mean we should extend the syntax? For example, something like this?
``` ruby
{
foo: 1,
?bar: nil
} #=> {foo... -
- Yes, I sometimes do that as well. However, I am not happy that the shape of the resulting hash is unclear.
-
- How about using `**`?
```ruby
def bar? = false
{
foo: 1,
**(bar? ? { bar: 2 } : {})
}
# => {:foo=>1}
```
Also, you can use `**nil` in ruby 3.4-dev.
```ruby
def bar? = false
{
foo: 1,
**({ bar: 2 } if bar?)... -
- "A special value" doesn't feel like a good idea to me.
-
- Sometimes I want to decide whether or not to add a particular entry to a hash depending on a condition. If the entire hash does not use nil, I can use Hash#compact.
```ruby
{
foo: 1,
bar: bar? ? 2 : nil
}.compact
```
But i... -
- Fixes this compiler warning:
thread.c:4530:18: warning: storing the address of local variable ‘stack_end’ in ‘*stack_end_p’ [-Wdangling-pointer=]
4530 | *stack_end_p = &stack_end;
| ~~~~~~~~~~~~~^~~~~~~~~~~~ -
- https://github.com/ruby/prism/commit/a2f57ef6e3
-
- As long as we use a high enough test version, the default version of
Bundler should never get in the middle.
https://github.com/rubygems/rubygems/commit/d63f0818aa -
- They are used by default.
https://github.com/rubygems/rubygems/commit/0b7f7d879f -
- https://github.com/rubygems/rubygems/commit/d850ea1d95
-
- Applied in changeset commit:git|24493779b79bb57fd2e71bf6e0ababe95448a9d6.
----------
[Bug #20725] Should not call compare on `nil`-endpoint
It means unbounded, always inclusive of other ranges. -
- https://github.com/ruby/ruby/pull/11609
-
- It means unbounded, always inclusive of other ranges.
-
-
07:45 AM Bug #20723: `IO#close` is broken on Ruby 3.3+ when using the Fiber scheduler.
- Sorry about this. I think https://github.com/ruby/ruby/pull/11614 is the smallest diff that will fix the issue (and this should probably be backported to 3.3).
Separately to that, I wonder if we need to wrap up some common function fo... -
-
-
- 05:35 AM Revision 58942023 (git): typo otherBasis -> orthoBasis
- The original function name in ao.c was orthoBasis.
I guess the function is generating orthonormal basis (https://en.wikipedia.org/wiki/Orthonormal_basis). -
-
- ```
/home/chkbuild/chkbuild/tmp/build/20240913T003003Z/ruby/test/net/http/utils.rb:32: warning: assigned but unused variable - e
/home/chkbuild/chkbuild/tmp/build/20240913T003003Z/ruby/test/net/http/utils.rb:61: warning: assigned but unu... -
-
-
- FreeBSD 14.1 build is also failure with ruby master. This is different error from #20733
```
[hsbt@freebsd ~/ruby]$ make
BASERUBY = /usr/local/bin/ruby --disable=gems
CC = clang
LD = ld
LDSHARED =... -
- FreeBSD 13.3 build on Ruby CI was failure from 1 week ago. I manually build ruby master on FreeBSD 13 and got the following error.
```
[hsbt@freebsd /usr/home/hsbt/ruby]$ make
BASERUBY = /usr/local/bin/ruby --disable=gems
... -
- I thought she was a committer long ago.
-
- I got the following failure with mswin environment.
```
1) Failure:
TestRubyOptions#test_command_line_progname_nonascii [C:/Users/hsbt/DevDrive/github.com/ruby/ruby/test/ruby/test_rubyoptions.rb:1086]:
[ruby-dev:48752] [Bug #1055... -
09/12/2024
-
- +1
-
- +1
-
08:25 PM Misc #20728: Propose Eileen Uchitelle as a core committer
- +1
-
- +1, I think Eileen would make a great addition, especially as a maintainer on the Prism parser / compiler. She's also been participating in the MMtk GC integration and her help in that area is valuable as well.
-
- I'd like to propose Eileen Uchitelle (@eileencodes) as a core committer. Now that Prism ([Feature #20564]) is merged, I would like her help maintaining the Prism parser and compiler without having to go through me to get patches merged.
... -
- >Is there the criteria for reverting this until Ruby 3.4 release?
I'm still waiting this answer. -
- Per this ticket, I have merged https://github.com/ruby/ruby/pull/11497 to switch the default parser on master. The caveats in this ticket still apply, and I will be working on those next.
As a part of this PR I have added a new GitHub... -
- If we are during heap traversal, we don't want to call rb_gc_impl_mark_weak.
This commit moves that check from rb_gc_impl_mark_weak to rb_gc_mark_weak. -
-
-
-
-
-
-
-
- Truthfully it might not be worth adding these optimizations. It's a lot to maintain in both compilers, and this kind of literal is extremely unlikely to be used with Ractors until other problems with Ractors are solved. I would just as s...
-
- I added back the array literal optimizations here: https://github.com/luke-gru/ruby/tree/bug20473
I didn't send a PR because it's not working with prism yet. Let me know if this is an okay solution, I could get it working for prism to... -
- For a while we've been seeing an occasional segfault in production inside of YJIT's invalidation code. It seems to happen most often when a invalidation on a widely used CME.
```
[BUG] Segmentation fault at 0x0000000000000014"
"ruby... -
05:43 PM Bug #20586 (Closed): Some filesystem calls in dir.c are missing error handling and can return incorrect results if interrupted
- Applied in changeset commit:git|f2919bd11c570fc5f5440d1f101be38f61e3d16b.
----------
Add error checking to readdir, telldir, and closedir calls in dir.c
Raise SystemCallError exception when these functions return an error.
This change... -
-
- https://github.com/ruby/prism/commit/d68ea29d04
-
-
-
- The description has been updated when running with Prism to have
+PRISM, which means that tests asserting against the description
when running with --parser=parse.y will be incorrect if the
subprocess ends up using Prism. We need to fix ... -
-
-
-
- This commit switches the default parser to Prism. There are a
couple of additional changes related to this that are a part of
this as well to make this happen.
* Switch the default parser in parse.h
* Remove the Prism-specific workflow ... -
- Raise SystemCallError exception when these functions return an error.
This changes behavior for the following case (found by the tests):
```ruby
dir1 = Dir.new('..')
dir2 = Dir.for_fd(dir1.fileno)
dir1.close
dir2.close
```
The above c... -
- https://github.com/ruby/prism/commit/e8c862ca1f
-
- of irb_break irb_catch and irb_next command
(https://github.com/ruby/irb/pull/1004)
* Remove KEYWORD_ALIASES which handled special alias name of irb_break irb_catch and irb_next command
* Remove unused instance variable user_aliases
C... -
- Single `Integer` argument means an exact match to the major version.
-
-
-
-
- Do not release GVL around get{pwuid,pwnam,grgid,grnam} calls,
as doing so is not thread-safe. Another C extension could have
a concurrent call, and derefencing the returned pointer from
these calls could result in a segfault.
Have rb_h... -
- I submitted a pull request to implement this: https://github.com/ruby/ruby/pull/11605
In terms of compatibility issues:
* For singleton classes that prepend a module, and have the method defined in both the singleton class and prep... -
- The GC always locks the VM, so we don't need to lock it in rb_vm_ci_free.
-
- ```ruby
# shareable_constant_value: literal
a = 'hi'
A = ['hello' => a]
p A
```
gives:
```
./ruby -I../ruby/lib -I. -I.ext/x86_64-linux -I.ext/common -r./x86_64-linux-fake ../ruby/test.rb
-- raw disasm--------
trace:... -
01:03 PM Bug #20725 (Closed): Inconsistent handling of doubly-unbounded ranges in Range#overlap?
- The new `Range#overlap?` method does not seem to have a clear definition of how it behaves when passed ranges with nil begin **and** end `(nil..)`.
In the following two cases, it seems to treat this type of range as an "infinite" rang... -
12:06 PM Revision f47c057c (git): Remove unnecessary file
-
-
-
-
-
-
-
-
- >I think it's more prudent to do 15.1 first, then 16.0.
Agreed, thanks! -
03:21 AM Feature #19908: Update to Unicode 15.1
- hsbt (Hiroshi SHIBATA) wrote in #note-8:
> Unicode 16.0 has been released.
> ...
I think it's more prudent to do 15.1 first, then 16.0. I hope to be able to work on this soon. I created a separate issue for 16.0. -
- Unicode 16.0 has been released.
https://www.unicode.org/versions/Unicode16.0.0/
Should we move this instead of 15.1? -
- Unicode 16.0 has been released (see https://www.unicode.org/versions/Unicode16.0.0/). We should update to 16.0 after updating to 15.1.
09/11/2024
-
- Applied in changeset commit:git|5d358b660d41e64de301f428dc0300a52a6f9566.
----------
Fix issue with super and forwarding arguments in prism_compile.c
Fixes [Bug #20720] -
- Fixes [Bug #20720]
-
- https://github.com/ruby/prism/commit/487f0ffe78
-
07:03 PM Bug #20722: curious search result order on docs.ruby-lang.org
- You might have more luck reporting this at the RDoc repository:
https://github.com/ruby/rdoc -
05:07 AM Bug #20722 (Closed): curious search result order on docs.ruby-lang.org
- If you search for "String" on https://docs.ruby-lang.org/en/3.3/ the first four results returned are obscure:
1. Gem::SafeMarshal::Elements::String
2. Prism::StringFlags
3. Prism::StringNode
4. Reline::Terminfo::StringWithTiparm
5... -
- https://github.com/rubygems/rubygems/commit/03ddfd7610
Co-authored-by: Jonathan Hefner <jonathan@hefner.pro> -
- This was commented out almost 10 years ago, but I think it passes now!
https://github.com/rubygems/rubygems/commit/4a6b1aba3c - 05:19 PM Revision efc77d53 (git): [ruby/psych] Ensure strings with only underscores are not processed as Integer
- A string similar to "0x____" should be treated as a string.
Currently it is processed as an Integer.
This alters the regex specified by http://yaml.org/type/int.html
to ensure at least one numerical symbol is present in the string
befor... -
-
-
-
- https://github.com/ruby/prism/commit/ebd2889bee
-
- https://github.com/ruby/prism/commit/31154a389a
-
-
-
-
-
-
- In a `bundle exec` context, the local specification will actually be
part of the known specifications, so RubyGems will assume it has already
been installed, which is not actually true.
This will cause `RequestSet` to rebuild extensions... -
- DSLError prints the specific line in a Gemfile where the error was
raised. That's helpful when the error was explicitly raised by the
Gemfile DSL or, in the case it's implicitly raised, when the offending
code lives right in the Gemfile.... -
- Things like OOM, or StackOverflow should be raised immediately.
https://github.com/rubygems/rubygems/commit/11691ce492 -
- https://github.com/rubygems/rubygems/commit/b4ecb66224
-
- https://github.com/rubygems/rubygems/commit/ab44fa9ee4
-
10:49 AM Bug #20723: `IO#close` is broken on Ruby 3.3+ when using the Fiber scheduler.
- I've added the following work-around: <https://github.com/socketry/io-stream/commit/7d1546fa829d3fe046f66f559d9a774497390f3e>
-
- It may be related to https://github.com/ruby/ruby/commit/66871c5a06d723f8350935ced1e88d8cc929d809
-
- The following program seems to work okay on Ruby 3.2 but hangs on Ruby 3.3:
```ruby
#!/usr/bin/env ruby
require 'bundler/inline'
gemfile do
source 'https://rubygems.org'
gem 'async'
end
require 'socket'
def close_w... -
- I agree with @Dan0042, the new API should not have this error-prone behavior, it should raise if out of bounds instead of silent truncation.
I also think we should fix setbyte to not have this behavior, but that's a different issue.
... -
09:20 AM Feature #20594: A new String method to append bytes while preserving encoding
- Dan0042 (Daniel DeLorme) wrote in #note-31:
> Ironically, HexaPDF now uses an explicit modulo 256, so it would actually be fine if #setbyte raised an out-of-bound error.
> ...
Yes, as mentioned in the linked issue #15460 I implemented ... -
02:34 AM Feature #20594: A new String method to append bytes while preserving encoding
- Ironically, HexaPDF now uses an explicit modulo 256, so it would actually be fine if #setbyte raised an out-of-bound error.
https://github.com/gettalong/hexapdf/blob/master/lib/hexapdf/filter/predictor.rb#L166
imho better safe than s... -
01:54 AM Feature #20594: A new String method to append bytes while preserving encoding
- Dan0042 (Daniel DeLorme) wrote in #note-29:
> I understand the idea of keeping things consistent. But why does `setbyte` have this behavior in the first place? A few years back there was an attempt to check bounds, and then in #15460 Ma... -
- I understand the idea of keeping things consistent. But why does `setbyte` have this behavior in the first place? A few years back there was an attempt to check bounds, and then in #15460 Matz apparently decided he "prefers mod 256 behav...
-
-
-
-
-
- The clean targets should clean up all extensions, including those have
nothing to build for any reason, e.g., platform requirements etc. -
- exts.mk should deal with cleanings of extensions, including bundled
gems. - 04:49 AM Revision 6c16598a (git): [ruby/pathname] use delete_prefix instead of sub in find method
- delete_prefix with a string is easier to read than a regular expression
also it should be faster. It is available since ruby 2.5 and the gem requires
ruby 2.7.
https://github.com/ruby/pathname/commit/0070f43f19 -
04:41 AM Revision c37b6677 (git): [rubygems/rubygems] Make an exe file executable when generating new gems
- Currently, an exe file isn't executable when generating new gems
because it doesn't have the correct permission.
This PR sets the correct permission same as files under the `bin`.
https://github.com/rubygems/rubygems/commit/6509bf128a -
- With Ruby 3.3.5, every gem executable under `$prefix/bin` has a `.lock` file. This was [an unintended change](https://github.com/ruby/ruby/pull/11252#issuecomment-2337520641), which was fixed in rubygems master at https://github.com/ruby...
-
12:38 AM Revision 55ddfd58 (git): Fixes [Bug #20718] (#11576)
- Fixes [Bug #20718]
Allow objects that are not of type `RTypedData` to use the default free function, as `RTYPEDDATA_EMBEDDED_P` can return a false positive when casting non-`RTypedData` objects -
09/10/2024
-
- Dan0042 (Daniel DeLorme) wrote in #note-27:
> > > For integers, the i & 0xff masking behavior comes from String#setbyte.
> ...
I don't think there is a specific use case (or maybe the use case is the same as when providing out-of-bound... -
- > > For integers, the i & 0xff masking behavior comes from String#setbyte.
> ...
Can anyone explain what is the use case for this behavior? It seems strange to me that silently truncating integers would be a desirable behavior. Especial... -
- String#append_as_bytes was newly introduced in #11552.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
02:46 PM Bug #20716: Different instance_method behavior in Ruby 2.7 and Ruby 3.x
- Hi Evans,
Thank you for your guidance and the quick fix.
I truly appreciate it -
- I was able to track down the cause and submitted a pull request to fix this: https://github.com/ruby/ruby/pull/11582
It appears to be introduced by commit:ad729a1d11c6c57efd2e92803b4e937db0f75252, which I wrote and which was a fix for... -
- We don't use the key, so we can speed it up by not needing to convert the
key to ID in the iterator. -
- I've created a patch here: https://github.com/luke-gru/ruby/tree/20472 (the latest commit)
For kwsplat, it just calls compile_hash (which generates `hash_merge_kw` call after the hash generation), generates a `freeze` call on the compil... -
01:22 PM Feature #18368: Range#step semantics for non-Numeric ranges
- The compatibility with `(:a .. :z).step(3)` has also been restored.
https://github.com/ruby/ruby/pull/11573 -
09:15 AM Misc #20013: Travis CI status
- I see the case that the jobs are running with showing the outputs (and failing as expected).
https://app.travis-ci.com/github/ruby/ruby/builds/272246788
-
- We drop Travis CI for ruby/zlib, ruby/prism too. Because the Travis infra issues are still ongoing since my last report.
* https://github.com/ruby/zlib/pull/84
* https://github.com/ruby/prism/pull/3047
The Travis CI status page is... -
- https://github.com/ruby/tmpdir/commit/628c5bdc59
-
- The listening TCP socket is closed by `with_udp_and_tcp` helper, but
the connected socket is leaking.
```
Leaked file descriptor: TestResolvDNS#test_multiple_servers_with_timeout_and_truncated_tcp_fallback: 12 : #<TCPSocket:fd 12, AF_IN... -
- https://github.com/ruby/resolv/commit/3189d16b69
-
-
- https://github.com/ruby/ruby/pull/11581
-
-
- 07:00 AM Revision 30d00a0b (git): * 2024-09-10 [ci skip]
-
- Remove `.ceil` from base time calculation that makes 10x gap.
This will make the assertion more strict and also less flaky. -
- strscan, ipaddr and some default gems still support Ruby 2.4.
After this, I extract this CoreAssertions to their repositories. -
-
- Some symbol argument might not be accepted by Process.clock_gettime.
-
- To prevent influence from other processes.
-
-
- Increase the timeout limit when variance at rehearsal is small.
-
-
-
- The following case is resolved at Xcode CLI RC and macOS 15.1 beta3
> pid = fork { p File.realpath "/" }
> ...
-
- `make test-bundler` on ruby/ruby don't have installed gemspec.
So, `require "psych"` didn't activate psych as default gems on ruby repo.
https://github.com/rubygems/rubygems/commit/f8ca514cbb -
- https://github.com/rubygems/rubygems/commit/d46b6a49af
-
- https://github.com/rubygems/rubygems/commit/6b1e8a14bd
-
- https://github.com/rubygems/rubygems/commit/8d94c14ca0
Co-authored-by: Jonathan Hefner <jonathan@hefner.pro> -
- `DSL#to_definition` already verifies this.
https://github.com/rubygems/rubygems/commit/c596f0af83 -
- https://github.com/rubygems/rubygems/commit/0b7be7bb77
Co-authored-by: Jonathan Hefner <jonathan@hefner.pro> -
- This is a bit off-topic, but I've often thought it would be nice to have multiple "levels" of warnings. So we could have the fine-grained `Warning[:strict_unused_block]` which, if unset, defaults to the coarse-grained `Warning[:strict]` ...