| Age | Commit message (Collapse) | Author |
|
|
|
* ZJIT: setglobal should not return output
* Let the caller wrap Some
|
|
|
|
|
|
|
|
|
|
As Set is now a core collection class, it should have special inspect
output. Ideally, inspect output should be suitable to eval, similar
to array and hash (assuming the elements are also suitable to eval):
set = Set[1, 2, 3]
eval(set.inspect) == set # should be true
The simplest way to do this is to use the Set[] syntax.
This deliberately does not use any subclass name in the output,
similar to array and hash. It is more important that users know they
are dealing with a set than which subclass:
Class.new(Set)[]
# this does: Set[]
# not: #<Class:0x00000c21c78699e0>[]
This inspect change breaks the power_assert bundled gem tests, so
add power_assert to TEST_BUNDLED_GEMS_ALLOW_FAILURES in the workflows.
Implements [Feature #21389]
|
|
|
|
v1.245.0 is not working with the following issue:
https://github.com/ruby/ruby/actions/runs/15769771616/job/44464179119?pr=13661
```
D:/a/ruby/ruby/src/test/rubygems/mock_gem_ui.rb:83:in 'Gem::MockGemUi#terminate_interaction': Gem::MockGemUi::TermError (Gem::MockGemUi::TermError)
D:/a/ruby/ruby/src/lib/rubygems/user_interaction.rb:157:in 'Gem::UserInteraction#terminate_interaction'
D:/a/ruby/ruby/src/lib/rubygems/commands/exec_command.rb:175:in 'Gem::Commands::ExecCommand#install'
D:/a/ruby/ruby/src/lib/rubygems/commands/exec_command.rb:70:in 'Gem::Commands::ExecCommand#execute'
D:/a/ruby/ruby/src/lib/rubygems/command.rb:326:in 'Gem::Command#invoke_with_build_args'
D:/a/ruby/ruby/src/lib/rubygems/command.rb:304:in 'Gem::Command#invoke'
D:/a/ruby/ruby/src/test/rubygems/test_gem_commands_exec_command.rb:43:in 'TestGemCommandsExecCommand#invoke'
D:/a/ruby/ruby/src/test/rubygems/test_gem_commands_exec_command.rb:274:in 'block in TestGemCommandsExecCommand#test_gem_with_platform_and_platform_dependencies'
D:/a/ruby/ruby/src/lib/rubygems/user_interaction.rb:46:in 'Gem::DefaultUserInteraction.use_ui'
D:/a/ruby/ruby/src/lib/rubygems/user_interaction.rb:69:in 'Gem::DefaultUserInteraction#use_ui'
D:/a/ruby/ruby/src/test/rubygems/test_gem_commands_exec_command.rb:272:in 'TestGemCommandsExecCommand#test_gem_with_platform_and_platform_dependencies'
D:/a/ruby/ruby/src/tool/lib/test/unit/testcase.rb:202:in 'Test::Unit::TestCase#run_test'
D:/a/ruby/ruby/src/tool/lib/test/unit/testcase.rb:170:in 'Test::Unit::TestCase#run'
D:/a/ruby/ruby/src/tool/lib/test/unit.rb:1683:in 'block in Test::Unit::Runner#_run_suite'
D:/a/ruby/ruby/src/tool/lib/test/unit.rb:1670:in 'Array#map'
D:/a/ruby/ruby/src/tool/lib/test/unit.rb:1670:in 'Test::Unit::Runner#_run_suite'
D:/a/ruby/ruby/src/tool/lib/test/unit.rb:1374:in 'Test::Unit::ExcludesOption#_run_suite'
D:/a/ruby/ruby/src/tool/lib/test/unit/parallel.rb:52:in 'Test::Unit::Worker#_run_suite'
D:/a/ruby/ruby/src/tool/lib/test/unit/parallel.rb:24:in 'block in Test::Unit::Worker#_run_suites'
D:/a/ruby/ruby/src/tool/lib/test/unit/parallel.rb:23:in 'Array#map'
D:/a/ruby/ruby/src/tool/lib/test/unit/parallel.rb:23:in 'Test::Unit::Worker#_run_suites'
D:/a/ruby/ruby/src/tool/lib/test/unit/parallel.rb:122:in 'Test::Unit::Worker#run'
D:/a/ruby/ruby/src/tool/lib/test/unit/parallel.rb:220:in '<main>'
running file: D:/a/ruby/ruby/src/test/rubygems/test_gem_commands_exec_command.rb
```
|
|
|
|
|
|
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/13660
|
|
|
|
|
|
|
|
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/13651
|
|
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/13634
|
|
Notes:
Merged-By: k0kubun <takashikkbn@gmail.com>
|
|
I'm not sure why vcpkg cache is not using while recent weeks.
Notes:
Merged: https://github.com/ruby/ruby/pull/13582
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/13490
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/13473
|
|
https://github.com/ruby/ruby/commit/72bda0f981c7136f50254c433bbfb97a953f634b
Notes:
Merged: https://github.com/ruby/ruby/pull/13453
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/13386
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/13391
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/13377
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/13376
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/13379
|
|
- Quote % inside `if` block
- Use short branch name
|
|
Get rid of hardcoded paths
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/13345
|
|
This reverts commit cb88edf0bfdc2ce6bfbe3b4e0463a4c2dc5d2230.
It didn't help. You need to go to a different repository (ruby/ruby.wasm)
to see meaningful backtraces.
https://github.com/ruby/ruby.wasm/actions/runs/15000135135/job/42144675968#step:16:176
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/13262
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/13330
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/13330
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/13330
|
|
https://github.com/ruby/ruby/actions/runs/15008767265/job/42173424631
"error while executing at wasm backtrace" doesn't have meaningful
symbols. We can't debug this from just looking at the "[BUG] Cannot
malloc during GC" message.
As suggested by the error message, this commit sets WASMTIME_BACKTRACE_DETAILS=1.
Let me see if this improves the backtrace.
|
|
Notes:
Merged-By: k0kubun <takashikkbn@gmail.com>
|
|
It currently fails like: Can't find 'action.yml'
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/13304
|
|
|
|
|