Activity
From 04/22/2019 to 04/28/2019
04/28/2019
-
09:29 PM Revision daa08740 (git): CLOCK_MONOTONIC_RAW_APPROX seems less precise than advertised on macOS
- * https://travis-ci.org/ruby/ruby/builds/525651487
-
-
-
- * Fixes "No behavior expectation was found in the example"
* https://rubyci.org/logs/rubyci.s3.amazonaws.com/centos6/ruby-trunk/log/20190428T093004Z.fail.html.gz -
- mame (Yusuke Endoh) wrote:
> a beginless range has only one use case (DSL-like usage)
I'm not sure what you mean by DSL-like usage, but I wouldn't be surprised if many people use it like `array[..-2]` (instead of `array[0..-2]`).
In... -
12:17 PM Bug #15745: There is no symmetry in the beginless range and the endless range using `Range#inspect`
- Eregon (Benoit Daloze) wrote:
> Yes, I think it's a possibility and is rather consistent.
Agreed, it is the most consistent. IMHO, `p (1..) #=> 1..nil` is a bit verbose, though.
I think that an endless range will be much more com... -
- Yes, I think it's a possibility and is rather consistent.
Otherwise, we need to special-case #inspect for beginless, endless and begin+endless ranges as you showed above.
I'd rather have a straightforward implementation for Range#ins... -
05:45 PM Bug #15808 (Rejected): Forwardable doesn't allow forwarding the 'print' message
- This is not a bug in Forwardable, this is due to the fact that OpenStruct doesn't override `print`, as `Kernel#print` is already defined. You must undefine the `print` method in OpenStruct if you want this to work. Example:
```ruby
... -
04:04 PM Bug #15808 (Rejected): Forwardable doesn't allow forwarding the 'print' message
- The following program forwards two messages to `@foo`: message 'print' and message 'bar'.
When I forward the 'print' message, I see a warning and the return value of `print` is always `nil`
(despite the fact that I specified my own ret... -
05:06 PM Misc #14632: [ANN] git.ruby-lang.org
- Today and yesterday I updated ruby-commit-hook to deal with race condition and corner cases of notifications, like pushing multiple commits at once. Now ruby-commit-hook should be correctly working for much more situations.
@nobu and ... -
-
04:48 PM Bug #15809 (Closed): GC.verify_compaction_references - intermittent SEGV's on multiple platforms
- See
https://travis-ci.org/ruby/ruby/jobs/525627187#L2684
https://ci.appveyor.com/project/ruby/ruby/builds/24138134/job/i7e441u7se11w7ey#L3402
Both have an error similar to:
```
/ruby/test/ruby/test_gc_compact.rb:128: [BUG] ROOT ... -
- as both backport source repository and backport destination repository.
-
04:23 PM Revision f0776e32 (git): Add more debug print for random CI failure on osx Travis
- and remove `git status` with noisy rvm trace log
see r67347 -
- 04:00 PM Revision 75260d36 (git): * remove trailing spaces.
-
- because it's hard to understand what's going on when indentation depth
is too deep.
Sorry for polluting git blame, but most of the Merger's lines are
updated recently anyway. -
- repository.
- 03:22 PM Revision bbad0d05 (git): * 2019-04-29
-
-
- Applied in changeset commit:git|6bedbf462544a7917fdc8d8c44276079a6e156cf.
----------
numeric.c: Extend Integer#[] to support range arguments
````
0b01001101[2, 4] #=> 0b0011
0b01001100[2..5] #=> 0b0011
0b01001100[2...6] #=> 0b0011
... - 02:42 PM Revision 555d1dda (git): * expand tabs.
-
- ````
0b01001101[2, 4] #=> 0b0011
0b01001100[2..5] #=> 0b0011
0b01001100[2...6] #=> 0b0011
^^^^
````
[Feature #8842] -
02:29 PM Bug #15807: Range#minmax is slow and never returns for endless ranges
- mame (Yusuke Endoh) wrote:
> `Range#max` is not consistent with `Enumerable#minmax`.
Thanks for pointing this out, I wasn't aware of that. Floats are another example:
``` ruby
(1..(5.5)).max # => 5.5
(1..(5.5)).minmax # => [1, 5]
... -
- I'm never against fixing this issue but I have one concern. Currently, `Range#max` is not consistent with `Enumerable#minmax`.
```
p ("a".."aa").max #=> "aa"
p ("a".."aa").minmax #=> ["a", "z"]
```
Thus, if `Range#minmax` is... -
- current situation:
- `(1..).minmax` runs forever
- `(1..).max` raises "cannot get the maximum of endless range"
- `(1..Float::INFINITY).minmax` runs forever
- `(1..Float::INFINITY).max` returns instantly
- `(1..1_000_000_000).minm... -
-
- updating indentation (and slightly changing styles) for areas already
supporting Git. -
- * See https://travis-ci.org/ruby/ruby/jobs/525595997
-
- for SVN as a backport source.
This was a mistake in de5378233b2ff5434f024ac66285e699794a321d... -
- to avoid having impact from other places.
-
-
-
- * https://rubyci.org/logs/rubyci.s3.amazonaws.com/scw-9d6766/ruby-trunk/log/20190428T051708Z.fail.html.gz
* https://rubyci.org/logs/rubyci.s3.amazonaws.com/scw-ad7f67/ruby-trunk/log/20190428T045405Z.fail.html.gz -
- I'm unsure how many cases people want to implement the index resolving code, but if it is not rare, I'm for the proposal.
I don't think that we will often add a new concept (like begin/end-less Ranges) that affects the resolving code,... -
-
- from https://github.com/ruby/irb/commit/e8e79d569ed59fe4ed4fbca968917ce799f02a5e.
This colorizes Range object on IRB inspect. -
-
- to clarify it's not needed for Git support.
-
- because it's not used outside the Module.
-
-
-
- so that we do not monkey-patch all classes by defining methods on
top-level (Object class).
Not arranging indentation in it to keep `git blame` for now. -
- from https://github.com/ruby/irb/commit/96f05e726879e9858eb015c8d043c9f52b864ff9.
Just syncing newer test changes so that conflicts do not happen when trunk is
modified and we need to backport that to ruby/irb. -
- from https://github.com/ruby/irb/commit/44301d382794d91e2caa16dd4efe62439e0041d8.
This includes some fixes for string interpolation highlight fixes. -
-
- * Clocks don't match the reported precision.
* https://rubyci.org/logs/rubyci.s3.amazonaws.com/freebsd11zfs/ruby-trunk/log/20190428T093003Z.fail.html.gz -
- In my understanding, `VM_CHECK_MODE` should be Integer and I'm not sure
how `-DVM_CHECK_MODE` would behave. To make the matters simple, let me
pass the mode explicitly. -
-
04:46 AM Revision 4c8f1078 (git): Make the range to export as changelog optional
- * `from` is defaulted to the beginning of the branch inclusively,
otherwise the given revision is excluded as the previous.
* `to` is defaulted to the head. -
- akr (Akira Tanaka) wrote:
> PATH_MAX is dangerous.
> ...
I'm not sure if this is still a problem on modern Linux, but here's an updated patch that passes a NULL pointer as the second argument to realpath(3), and then frees the pointer ... -
03:37 AM Feature #15797: Use realpath(3) instead of custom realpath implementation if available
- PATH_MAX is dangerous.
Quotes from http://man7.org/linux/man-pages/man3/realpath.3.html
```
BUGS
The POSIX.1-2001 standard version of this function is broken by
design, since it is impossible to determine a suitabl... -
- Attached is an updated patch against trunk, now that the taint fix in #15803 was committed. One other change in this patch is that the `realpath_rec` function is no longer compiled if the native realpath(3) implementation is used.
-
-
-
-
- It is nonsense with `-n1` option.
-
- Committed at a15f7dd1fb1148c3d586238ee6907875f2e40379
-
02:07 AM Revision d0a54673 (git): Update rubygems with latest upstream changes
- Closes: https://github.com/ruby/ruby/pull/2154
-
01:47 AM Revision a15f7dd1 (git): Always mark the string returned by File.realpath as tainted
- This string can include elements that were not in either string
passed to File.realpath, even if one of the strings is an
absolute path, due to symlinks:
```ruby
Dir.mkdir('b') unless File.directory?('b')
File.write('b/a', '') unless Fi... -
-
- duerst (Martin Dürst) wrote:
> As for the assignment, just using parentheses looks confusing to me. It's clear we can't use `>=` or `|=`, but `|>=` or some other combination would be much clearer than just parentheses.
OK, I separate... -
04/27/2019
-
11:41 PM Misc #15806 (Assigned): Explicitly initialise encodings on init to remove branches on encoding lookup
- References Github PR https://github.com/ruby/ruby/pull/2128
I noticed that the encoding table is loaded on startup of even just `miniruby` (minimal viable interpreter use case) through this backtrace during ruby setup:
```
/home/l... -
- References Github PR https://github.com/ruby/ruby/pull/2140
In current trunk only the `imemo_tmpbuf` type's auxiliary malloc heap buffer is factored into `obj_memsize_of`. The following IMEMO types also allocate on the malloc heap:
... -
- I'd like to close this issue tentatively. Feel free to reopen if you still think it is needed.
-
- Just confirm, @eregon, do you mean endless range's inspect should also show nil?
```
p(1..) #=> 1..nil
p(..1) #=> nil..1
p(nil..nil) #=> nil..nil
``` -
- Maybe always showing `nil` is clearer, since anyway the current implementation of begin/end-less Ranges leaks that detail? (e.g., through `#begin` and `#end`)
Somewhat related about leaking Range's implementation details: #15804. -
- * https://rubyci.org/logs/rubyci.s3.amazonaws.com/unstable11x/ruby-trunk/log/20190427T182404Z.fail.html.gz
-
- * clock_getres() seems to be incorrect on BSD:
https://rubyci.org/logs/rubyci.s3.amazonaws.com/freebsd11zfs/ruby-trunk/log/20190427T183003Z.fail.html.gz -
- Currently, the implementation of begin/end-less Ranges leaks the representation of infinite ranges (it's a `nil` value for `begin` or `end`).
For instance, this "works" but I think it's potentially confusing:
```ruby
s = "abcdef"
t... -
- I think making Set unordered would be a big breaking change, similar to making Hash unordered (as it was in 1.8).
Maybe people forgot, but I find it pretty bad to work with unordered Hashes,
e.g., every iteration method like `each` yie... -
- Indeed, AFAIK it's the ABI version.
MSP-Greg (Greg L) wrote:
> If the version with 'teeny' was used, one would be recompiling extension gems everytime a 'teeny' release was done?
Which IMHO is a safer thing to do, but I suppose so... -
-
-
- because it makes the CI unstable
https://ci.appveyor.com/project/ruby/ruby/builds/24143365/job/yrx7b8ce2qg9wro2 -
- nobu (Nobuyoshi Nakada) wrote:
> The tainted-ness issue seems a different story.
> ...
Added #15803 for that. -
- The tainted-ness issue seems a different story.
Could you make it a separate ticket? -
- This string can include elements that were not in either string
passed to File.realpath, even if one of the strings is an
absolute path, due to symlinks:
```ruby
Dir.mkdir('b') unless File.directory?('b')
File.write('b/a', '') unl... - 05:02 PM Revision ed4f3318 (git): * remove trailing spaces.
-
- from https://github.com/ruby/irb/commit/89e9add06da3fd5f9ce91a2f5fa0b0190aa5d42f.
This adds syntax highlight support for Module on inspect.
In addition to that, I'm adding a trailing space in test_color.rb for
testing ruby-commit-hook'... -
-
-
- References Github PR https://github.com/ruby/ruby/pull/2151 - another small change, but posting here for further discussion.
While having a look through `String` specific allocation paths with [dhat](http://valgrind.org/docs/manual/dh... - 04:25 PM Revision 80be9e98 (git): * 2019-04-28
-
-
- * Mostly to try the new git repository.
-
- Oops, don't backport doc/ChangeLog-2017 file to 2.5, of course.
-
- Please backport:
* af1e487e9bb763b939dc6704c9a343c9eafa1637
Updated marked commits for ChangeLog
* 6f8ac2cb28f99a4b2588c59ec44eff6ed38c4d3b
Include the beginning commit in ChangeLog
-
-
-
02:23 PM Misc #15782: DevelopersMeeting20190522Japan
- * [Feature #15772] Proposal: Add `Time#ceil`
* I want to hear the opinions of developers.
* [Feature #13645] Syntactic sugar for indexing when using the safe navigation operator
* I presented a use case.
-
01:26 PM Misc #15782: DevelopersMeeting20190522Japan
- * [Feature #15765] [PATCH] `Module#name` without global constant search
* This fixes the performance problems for `#name` on anonymous module / classes, but also comes with some small behavioral changes. Are they okay? -
- * [Feature #14915] Deprecate `String#crypt`
* I think we should add a real deprecation warning in 2.7 so we can remove it in a later version. -
02:19 PM Feature #15799: pipeline operator
- > I think there is nothing wrong with having parentheses for Range, I
> ...
My comment is not meant in regards to the example given for Range here, but more in general.
I am not sure if having mandatory parentheses is a (visual/syntact... -
- My early thinking about this syntax is it's a very narrow use-case.
Is it anything more than `.` and no need for parentheses in some rare cases?
There is also the RHS assignment which feels very unnatural to me.
I think there is not... -
10:28 AM Feature #15799: pipeline operator
- Thanks for creating an issue.
The `|>` symbol looks reasonable to me, but I'd like to see more examples where this notation is preferable to
```ruby
(1..).take(10).map {|x| x*2}
```
As for the assignment, just using parenthes... -
- Implemented the pipeline operator `|>`, a topic of "ruby committers vs the world" in RubyKaigi 2019.
Also a casual idea of rightward assignment.
```ruby
1.. |> take 10 |> map {|e| e*2} |> (x)
p x #=> [2, 4, 6, 8, 10, 12, 14, 16, 18... -
- VCS::GITSVN#format_changelog generates previous format, similar to
svn-log, and VCS::GIT#format_changelog stores just git-log as-is
for now. -
-
-
-
- like https://ci.appveyor.com/project/ruby/ruby/builds/24142523/job/v6aq4srj7c3hgt86
-
- Synced from https://github.com/ruby/irb/commit/5feb361ed80736efa5b2c2b629837ec2a5fc2cdb.
This includes a support to colorize named Class instance on IRB inspect. -
- References PR https://github.com/ruby/ruby/pull/2135 - it's a very small change, but runnin due diligence past the list too for discussion.
I noticed `onig_region_resize` (called from `onig_region_copy`) would default to allocating a ... -
- Thank you, fixed at https://git.ruby-lang.org/ruby.git/commit/?id=3f9562015e651735bfc2fdd14e8f6963b673e22a.
-
- * string.c (str_duplicate): share the root shared string if the
original string is already sharing, so that all shared strings
refer the root shared string directly. indirect sharing can
cause a dangling pointer.
[Bug #15792] -
- as it's unstable on the environment
https://ci.appveyor.com/project/ruby/ruby/builds/24138134/job/i7e441u7se11w7ey -
-
03:55 AM Revision bc01f7b7 (git): Fix description of NODE_IN
-
03:35 AM Revision 7fe04850 (git): Add class ref to `UnboundMethod#owner` doc
- It refers to `Method#receiver` in the doc, but
there's no class reference in current doc.
Some tools automatically make it a link so it's useful.
Closes: https://github.com/ruby/ruby/pull/2156 - 03:35 AM Revision ecf660e4 (git): ia64: Don't clear register_stack_start
- r59829 stopped clearing stack_start and enabled the code for
!FIBER_USE_NATIVE, but we need to do the same for register_stack_start
on ia64, otherwise we end up with NULL in cont_save_machine_stack.
Closes: https://github.com/ruby/ruby/... -
- Wercker seems to randomly fail
https://app.wercker.com/ruby/ruby/runs/mjit-test1/5cc3c1c423fcb70008db9b64?step=5cc3c46a03f4460007da0659
To help debugging, let me isolate the impact from GC.compact in the JIT
testing on Wercker. -
- ```
% ruby -ve 'p (nil..).first'
ruby 2.6.3p62 (2019-04-16 revision 67580) [x86_64-darwin18]
nil
% ruby -ve 'p (nil..).begin'
ruby 2.6.3p62 (2019-04-16 revision 67580) [x86_64-darwin18]
nil
``` -
-
- chocolateboy (Chocolate Boy) wrote:
> > `using` is already used for refinements, and here were are dealing with block arguments, which are unrelated. It would be confusing to use the same keyword with different meanings.
> ...
`using` ... -
-
- Backport changes from ruby/irb.
-
02:31 AM Revision 782e4872 (git): suppress warning in test/irb
- https://rubyci.org/logs/rubyci.s3.amazonaws.com/centos7/ruby-trunk/log/20190421T040003Z.fail.html.gz
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67678 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
Re-committing https://github.com/ruby/rub... - 12:17 AM Revision a2219e68 (git): * 2019-04-27
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67679 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66866 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
04/26/2019
-
- When using UBF_TIMER_PTHREAD, the timer_pthread_fn function will
not signal the main thread with SIGVTALRM in cases where
timer_pthread is armed before consume_communication_pipe is called.
This is because consume_communication_pipe w... -
- I think the new proposition by @jeremyevans0 is much better than the current state, and sounds good to me.
`@` might not be ideal, but at least it's less confusing than `@` and doesn't have complicated compatibility problems.
From my... -
07:54 PM Misc #15723: Reconsider numbered parameters
- sawa (Tsuyoshi Sawada) wrote:
> This looks to me like splitting Ruby into two dialects and letting the programmer declare when using the non-default one. I think it would be a start of a nightmare in which Ruby has many dialects.
`... -
- One reason to do this is simplicity, as this approach is ~30 lines of
code instead of ~200.
Performance wise, this performs 25%-115% better, using the following
benchmark on OpenBSD 6.5:
```ruby
require 'benchmark'
f = File
... -
08:21 PM Bug #15792: GC can leave strings used as hash keys in a corrupted state
- I guess it is caused by the combination of `str_duplicate` and `rb_fstring` from r52074.
```
$ cat bug15792.rb
a = ('a' * 24).b.strip
->{ eval "", binding, a, 1 }.call
puts "Before garbage_collection: a=#{a.inspect}"
4.times... -
03:08 PM Bug #15792: GC can leave strings used as hash keys in a corrupted state
- Édouad Chin bisected the script against the MRI repository, and found https://bugs.ruby-lang.org/issues/15251 the first commit to trigger the problem.
That being said it's unlikely to really be the source of the bug. It's much more li... -
- Actually, even simpler repro script:
```
#!/usr/bin/env ruby --disable-gems
a = ('a' * 24).encode(Encoding::ASCII).strip
hash = {}
hash[a] = true
puts "Before garbage_collection: a=#{a.inspect}"
4.times { GC.start }
puts "A... -
- The following script showcase the issue:
```
#!/usr/bin/env ruby --disable-gems
a = ('a' * 24).encode(Encoding::ASCII).gsub('x', '')
b = ('b' * 24).encode(Encoding::ASCII).gsub('x', '')
hash = {}
hash[a] = true
hash[b] = true
... -
04:47 PM Bug #15796 (Third Party's Issue): Ramdon console crashes
- This is the error log, followed by the one in the Library folder
-- Control frame information -----------------------------------------------
c:0078 p:---- s:0444 e:000443 CFUNC :initialize
c:0077 p:---- s:0441 e:000440 CFUNC :new... -
- > This is current situation.
Thanks for the summary.
> ...
I think it's fair enough for usages of Binding.of_caller to have to care about this.
@ko1 The `debug_inspector` gem just makes the Bindings of the stack available to Rub... -
01:28 PM Bug #15795 (Closed): Some test fails on Haiku
- ```/sources/ruby-2.6.3/.ext/common/fiddle/import.rb:89:in `rescue in block in dlload': can't load /sources/ruby-2.6.3/test/-ext-/arith_seq/test_arith_seq_extract.rb (Fiddle::DLError)```
-
-
- This reverts commit 6669c966d2744f21315047d1725ad4494d15b8ba.
It seems to make tests fail... let me fix this later. -
- inspect.
Change is made with: `$ make -C .ruby sync-default-gems GEM=irb` -
- from https://github.com/ruby/irb/commit/e6739d8c66dc78562930adb0b96935c9b38acf74
-
- to run tool/sync_default_gems.rb
-
-
09:14 AM Bug #15794 (Third Party's Issue): Can not start Puma with Rails after bundle install
- I have big issue and I don't know how to resole.
``` ruby
rails s -p 5000
=> Booting Puma
=> Rails 4.2.10 application starting in development on http://localhost:5000
=> Run `rails server -h` for more startup options
=> Ctrl-C t... -
- see r67347
-
- I have no strong opinion about this, but `(nil..nil).inspect #=> ".."` looks less reasonable because we cannot actually write the literal as is, so we need to decide the behavior of this corner case.
-
07:19 AM Bug #15793 (Closed): Please backport 7b7043e5da8589e01b94575d4ed647e909e5c875
- 7b7043e5da8589e01b94575d4ed647e909e5c875 is a fix of use-after-free. Worth backporting methinks.
-
07:11 AM Misc #15782: DevelopersMeeting20190522Japan
- * [Bug #15745] There is no symmetry in the beginless range and the endless range using `Range#inspect` (koic)
* I think that the symmetry of beginless range and endless range becomes more clear by unifying whether it displays `nil` or... -
- The configuration cannot but be written here and there....
-
-
- Seems clang-7 has false-positives around memory sanitizer.
This line should not be reported because the memory region is
correctly unpoisoned beforehand:
https://travis-ci.org/ruby/ruby/jobs/524766381
Clang 8 seems to fix it. -
-
-
- rb_io_fptr_finalize_internal frees the memory region.
=================================================================
==85264==ERROR: AddressSanitizer: heap-use-after-free on address 0x610000000d8c at pc 0x5608e38077f7 bp 0x7ffee12d54... -
- ec->cfp->iseq might not exist at the very beginning of a thread.
=================================================================
==82954==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x7fc86f334810 at pc 0x55ceaf013125 bp ... -
- obj_ivar_heap_alloc already handles that situation.
-
- This header is poisoned to detect unintentional buffer overrun.
However in this (and forthcoming) function, we are intentionally
looking at the header. We have to unpoison before anything. -
- memo.float_value might change inside of hash_sum. In case it
flipped from false to true there, and the calculated sum is Inf,
memo.c might not be initialized at all. This is bad.
Found using memory sanitizer:
==55293==WARNING: Memory... -
- autoload_reset() can read this state.result. Because autoload_reset
is a function passed to rb_ensure, there is a chance when an
execption raises before actually filling this memory region.
test/ruby/test_defined.rb:test_autoload_noloa... -
- Depending on architectures, setjmp might not fully fill a jmp_buf.
On such machines the union can contain wobbly bits. They are then
scanned during mark_locations_array(). This is bad. -
- Sanitizers report something inside of this function but it is
beyond my brain capacity. Also the code is proven to work.
Let me ignore. -
- The size of `ptr` here is not the same as the variable `size`.
We were counting the size of header twice. -
- These functions purposefully read from memory regions potentially
not handled well. Should let sanitizers avoid checking them. -
-
- It seems sanitizers require extra amount of machine stacks. Without
extending them the process tends to stack overflow. -
- These assertions check if a newly allocated object (which is marked
as an uninitialized memory region in MSAN) is in fact a T_NONE.
Thus they intentionally read uninitialized memory regions, which do
not interface well with MSAN. Just ... -
- while heap->obj is a VALUE. A cast should be there.
-
- It seems to be my fault to leave the variable disasm unused.
-
-
- Closed at https://git.ruby-lang.org/ruby.git/commit/?id=54eac83b2ad77ddea84fa6d66c09e0bb014cf61e
-
- * parse.y (internal_id): number the ID serial for internal use by
counting down from the neary maximum value, not to accidentally
match permanent IDs.
[Bug #15768]
04/25/2019
-
11:16 PM Bug #15774 (Closed): OptionParser doesn't accept Date options as stated in the docs
-
06:37 PM Bug #15774: OptionParser doesn't accept Date options as stated in the docs
- Oh, thanks, I wasn't aware of that. Now that you said I re-read the documentation and found the instructions to use those built-in conversions. Thanks. This ticket can be closed. I'm not allowed to close it myself.
-
- I always consider `RbConfig::CONFIG['ruby_version']` as the ABI version, which is used in naming `--user-install` gem folders, etc.
If the version with 'teeny' was used, one would be recompiling extension gems everytime a 'teeny' rele... -
03:44 PM Bug #15791 (Closed): Clarify reason for RbConfig's ruby_version not reflecting "teeny" value
- I did not realize that MRI always reports `RbConfig::CONFIG['ruby_version']` without the "teeny" value. Instead, it makes it always 0:
```
$ rvm ruby-2.6.2 do ruby -v -e 'p RbConfig::CONFIG["ruby_version"]'
ruby 2.6.2p47 (2019-03-13... - 04:43 PM Revision 5689c464 (git): * 2019-04-26
-
-
- We must note this feature is heavily inspired by Pry.
-
-
- Details: https://github.com/ruby/ruby/pull/2150
Note that this introduction is discussed with @aycabta who is allowed to
make some changes to IRB by the IRB maintainer, keiju. -
- I'm +1 for single variable using `@`.
-
- Closes: https://github.com/ruby/ruby/pull/2150
- 03:47 PM Revision 022cbb27 (git): Do not color IRB output on 'dumb' TERM
- Co-Authored-By: k0kubun <takashikkbn@gmail.com>
Closes: https://github.com/ruby/ruby/pull/2150 -
- Closes: https://github.com/ruby/ruby/pull/2150
-
- Closes: https://github.com/ruby/ruby/pull/2150
-
- see [r67606](https://github.com/ruby/ruby/commit/3ee0648dc7a5465b2cbadd7246fc2edbd676d759)
-
01:05 PM Feature #12698: Method to delete a substring by regex match
- The suggestion by @knu is pretty cool if you think about it: Since both `sub` and `gsub` exist, the uncertainty whether only one or all occurrences are deleted is gone. Also, with this in place, `delete` could be deprecated IMO (and remo...
-
-
- see r67347
-
-
-
- `call xxx, yyy` seems to pass " yyy" instead of "yyy".
-
09:54 AM Feature #15323: [PATCH] Proposal: Add Enumerable#filter_map
- I've updated the patch file increasing the ruby version in *spec/ruby/core/enumerable/filter_map_spec.rb*
`Enumerable#filter_map` was already accepted in the last developers meeting: https://docs.google.com/document/u/2/d/e/2PACX-1vTU... -
- May merge multiple github pull requests at once. e.g.,
$ make pr-123456789 pr-987654321 -
-
- You can use this like `make checkout-github PR=1234`
-
-
- A pull request based on an old commit may rewind too many files,
even if unnecessary. As rewinding some files, e.g., common header
files, configure.ac, will result in full-rebuild, rebase in a
separate directory to get rid of such rewind. -
- shyouhei (Shyouhei Urabe) wrote:
> Thank you for posting the issue! Tell us any updates when you want us to know.
Solved in Haiku: https://git.haiku-os.org/haiku/commit/?id=0e4b529df5c65d51d81f998055c6aac52f55437f
Thanks and sorr... -
-
- Closes: https://github.com/ruby/ruby/pull/2119
04/24/2019
- 08:28 PM Revision 9bfc185a (git): Upgrade test-unit to 3.3.2
-
- jeremyevans0 (Jeremy Evans) wrote:
> More work should be done if this is accepted. Specifically, we need to decide:
> ...
I've updated my branch (https://github.com/jeremyevans/ruby/tree/keyword-argument-separation) to add support for... -
07:57 PM Bug #15790 (Closed): Strange interaction between autoload and $LOADED_FEATURES
- If an autoload fails and we remove its associated file from `$LOADED_FEATURES`, the autoload is back:
```
$ cat x.rb
Y = 1 # should be X, emulates a typo
$ cat test.rb
def au
Object.autoload?(:X).inspect
end
x_rb = File.r... -
07:23 PM Bug #15766: Crash in 2.4, 2.5 involving at_exit
- It is indeed an exact duplicate of #15282, which you backported to 2.5.
However, you didn't backport it then to 2.4. I understand that now it's probably a bit too late for a backport.
Nevertheless, as I didn't see you closing this ... -
- wishdev (John Higgins) wrote:
> The file you mention is required to be readable because it is the core of the rubygems module - but there is nothing written to that file at all.
Well, it's trying to lock the file, which is readonly, ... -
01:47 PM Bug #15787: LoadError by EPERM on read-only volume
- There is no such requirement as rubygems.rb in that folder being written to. I run locked down lxc containers on a daily basis that have no such writing ability (read only roots) and ruby works just fine. That folder is also not generall...
-
- shevegen (Robert A. Heiler) wrote:
> This is indeed unfortunate but I guess the code could be changed. Keep in mind that the ruby core
> ...
I know, this is why i am here :) Our ruby port is way too old and needs to be updated, but for... -
04:18 PM Bug #15789 (Closed): Parse error when numbered parameter is used in a lambda that is a default value of other optarg
- Sorry if the name of the ticket is not desccriptive
While working on backporting these commits into a parser gem:
https://github.com/ruby/ruby/commit/6ca9e7cc0785c33f6d382176dbd79d6c91db72fe
https://github.com/ruby/ruby/commit/ae07b... - 04:09 PM Revision 7d2cb60e (git): * 2019-04-25
- 04:08 PM Revision 68e3f819 (git): add DRbObject dereference test (Preparation for investigation of Bug #15711)
-
-
03:31 PM Bug #15773: Net::HTTP doesn't try next IP address in case of timeout
- I thought long and hard about how to reply to this.
Let's put it this way: the fact that you are using glibc isn't the problem at all. The fact that you are badly using its results is.
Any other big piece of code out there that is... -
- is true
Closes: https://github.com/ruby/ruby/pull/2148 -
- Closes: https://github.com/ruby/ruby/pull/2147
-
- see r67347
-
- [Bug #15784]
-
07:46 AM Feature #15778: Expose an API to pry-open the stack frames in Ruby
- Now we are not publishing Ruby API because we shouldn't use this kind of API on application code.
For example, if people rely on Binding.of_caller, we can't use delegation code freely.
I understand debugger like tools require the API, ... -
- Thank you for posting the issue! Tell us any updates when you want us to know.
-
- Seems to be a bug in Haiku: https://dev.haiku-os.org/ticket/15025
-
- I'll set Backport field for 2.5 as REQUIRED since https://bugs.ruby-lang.org/issues/15717 claims the issue was not fixed on ruby_2_5.
-
- jeremyevans0 (Jeremy Evans) wrote:
> As I expressed in the developer meeting today, after a lot of thought, I believe if we want to support implicit block arguments, we should limit support to a single argument, and use `@` to represent... -
02:57 AM Misc #15723: Reconsider numbered parameters
- chocolateboy (Chocolate Boy) wrote:
> [P]ragmas by overloading comments ... could be used here as well e.g.:
> ...
This looks to me like splitting Ruby into two dialects and letting the programmer declare when using the non-default one... -
- All stable versions have this bug.
-
- I can confirm the bug. Here is a single-line reproducer:
```
$ ruby -e 'autoload :X, "foo"; p Object.const_defined?("X")'
Traceback (most recent call last):
3: from -e:1:in `<main>'
2: from -e:1:in `const_defined?'
1: from /home... -
- [Bug #15784]
-
- `make update-src` shows latest commit hash for convinience.
However, `rev-parse --short` option shows different length
(maybe) between git versions. This fix force 10 chars
with `--short=10`.
04/23/2019
-
- This is indeed unfortunate but I guess the code could be changed. Keep in mind that the ruby core
team probably has not that much experience with haiku - most will use linux or mac OSX, some
windows or one of the BSDs.
Your problem... -
- On Haiku the package management just virtually extracts/populates the files, and as it doesn't have write-overlay feature, the populated files are read-only.
Issue: Ruby has to maintain a list of installed gems in a single file, in ru... -
10:26 PM Revision 19d454a9 (git): syntax error can move, so do not cache
-
- For example when an array containing objects is a hash key, the contents
of the array may move which can cause the hash value for the array to
change. This commit makes the default `hash` value based off the
object id, so the hash valu... -
- ```
~ » uname -a
Haiku shredder 1 hrev53091 Apr 22 2019 22:17:21 x86_64 x86_64 Haiku
```
miniruby crashes during the compilation phase in pthread_attr_get_np.See the attachements for more information.
Current (WIP) ruby recipe... -
-
- do not exist
-
- After `GC.compact`, test/shell/test_command_processor.rb seems to be made
unstable on osx Travis like https://travis-ci.org/ruby/ruby/jobs/523487997.
For investigating whether it's impacting that or not, let me try isolating
that for os... - 03:40 PM Revision 9629f4c0 (git): * 2019-04-24
-
-
03:02 PM Misc #15782: DevelopersMeeting20190522Japan
- * [Feature #15323] [PATCH] Proposal: Add `Enumerable#filter_map`
* It's expressive as Ruby lang itself
* Make `filter_map(&:predicate) { |elem| elem * 2 }` syntax possible
* Should also consider adding `#filter_map!`
* It enables... -
- * [Feature #15281] Speed up `Set#intersect` with size check.
* Everyone likes faster code. But the question is: are Sets ordered? I think Matz must decide. -
02:12 PM Bug #15786 (Closed): numbered parameterを使ったprocのparametersに記号が現れる
- ~~~ruby
->{@100}.parameters.map{@2}.join
#=> "!\"\#$%&'()*+,-./:;<=>?@[\\]^`"
~~~
`proc{@100}.parameters` の場合はそれに加え、`[[:opt, nil]...]` になる
`RubyVM::InstructionSequence.of(->{@100}).to_a`
`RubyVM::InstructionSequence.disasm(->{@... -
- @hsbt wrote:
> I restored now. Thanks for your notification.
Thanks, but I didn't do much. You fixed it, and very quickly. Thank you.
Greg -
01:28 PM Bug #15785 (Closed): GitHub - all tags are gone?
- I restored now. Thanks for your notification.
-
01:28 PM Bug #15785: GitHub - all tags are gone?
- They seem to be back now
-
- This has broken the “commit logs” links in Ruby release notes, e.g.
https://www.ruby-lang.org/en/news/2019/04/17/ruby-2-6-3-released/,
which is from less than a week ago. -
- There are also no tags at https://git.ruby-lang.org/ruby.git...
-
-
- Accidentally merged when 89271d4a3733bc5e70e9c56b4bd12f277e699c42
"Adjusted indents". -
- I announced https://www.ruby-lang.org/en/news/2019/04/23/move-to-git-from-svn/
We still have some issues. But I will close this.
If you find the issues, Please file them to bugs.ruby-lang.org or https://github.com/ruby/b.r-l.o espe... -
- Today, We move to Git from Subversion.
https://www.ruby-lang.org/en/news/2019/04/23/move-to-git-from-svn/
We can keep your original commit now. -
-
11:08 AM Revision f2cd4f4c (git): IRB is improved with Reline and RDoc, take 2
-
- ```
% RUBY_DEBUG=gc_stress gdb --args ./miniruby -vep
GNU gdb (Ubuntu 8.1-0ubuntu3) 8.1.0.20180409-git
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
T... -
- Could you please show us the reproducible code?
-
-
-
- Thank you for reporting and investigations.
I'll close this ticket because it was fixed on trunk and the stable maintainers watch Closed tickets for backport.
[Bug #15282] seems related. -
-
-
-
-
-
- 03:34 AM Revision e50e60b9 (git): * expand tabs.
-
- Unused T_MOVED objects can live on the stack, so we need to make sure
that they can be accounted for in book keeping -
03:16 AM Bug #15783 (Closed): 引数のデフォルト値にNumbered parameterを書ける、キーワード引数の場合デフォルト値にNumbered parameterを書くとSEGVする
- Applied in changeset commit:ruby-git|ae07b66aaa092c59ac9d544c9b582712290dc357.
----------
Fix internal error of `->x:@2{}`
[Fix GH-2139] [Bug #15783] -
- [Fix GH-2139] [Bug #15783]
-
- [Fix GH-2139] [Bug #15783]
-
- Before this commit, classes and modules would be registered with the
VM's `defined_module_hash`. The key was the ID of the class, but that
meant that it was possible for hash collisions to occur. The compactor
doesn't allow classes in ... -
01:49 AM Bug #15774: OptionParser doesn't accept Date options as stated in the docs - You need to `require 'optparse/time'` to use built-in Time conversion (it doesn't seem to be stated explicitly in the documentation, but it is demonstrated throughout the examples) and you need to `require 'optparse/date'` to use Date or...
-
-
- 01:19 AM Revision a9b57862 (git): * 2019-04-23
- 01:19 AM Revision a8d4dc28 (git): * expand tabs.
- 01:19 AM Revision 98ee6369 (git): Symbols can move, so don't cache in static pointer
- This changes the static pointers to use IDs then look up the symbols
with the ID. Symbols can move, so we don't want to keep static
references to them.
04/22/2019
-
- TL; DR: a keyword (e.g. `it`) could be used without breaking backwards-compatibility via a **pragma** e.g.:
```ruby
# implicit_parameter: true
http.get(url).then { JSON.parse(it) }
```
---
I don't mind `@1, @2` etc., given ... -
06:52 PM Bug #15508: Mutex recursive lock error when combined with Thread#raise
- I verified that this issue is fixed by [PR #2131](https://github.com/ruby/ruby/pull/2131).
-
- キーワード引数のデフォルト値にNumbered parameterを使うとSEGVしました。
再現コードです
```ruby
->x:@2{}
```
キーワードじゃない引数でも以下のような感じでNumbered parameterを使えるようです。
```ruby
->x=@1{}
```
以下のようにまぜて使った場合はシンタックスエラーになるのに、デフォルト値として書いた場合はシンタックスエラーにならないのはバグだと思います。
... -
- This change adds an explicit reference to `TracePoint` in the
documentation for `binding`. Currently it only refers to the now
deprecated `Kernel#set_trace_func`. This reference is left alone for
continuity in the documentation.
[Fix GH-... -
- [Fix GH-2084]
-
- k0kubun (Takashi Kokubun) wrote:
> * Verify committer email from SSH user (@mame)
Done.
* I've created a script named [check-email.rb](https://github.com/ruby/ruby-commit-hook/blob/master/bin/check-email.rb) which includes the cor... -
- ## Remaining tasks related to Git migration
* Add more git support in:
* Git support to backport to future `ruby_2_7` branch:
* `tool/merger.rb`
* Discuss the timing to rename the branch "trunk" to "master"? (#15782) -
- naruse (Yui NARUSE) wrote:
> Anyway chat is out of this topic.
Yes please. Don't let the chat involve this kind of things. -
- In this ticket, there's a list of pre and post tasks.
You can always add "pre-announcement" and "post-announcement" in these 3 months.
About git migration, investigation and organizing tasks themselves are also hard work.
I'm very a... -
- hsbt (Hiroshi SHIBATA) wrote:
> >Next time tell us BEFORE you disable something, OK?
> ...
I now feel I am excluded from the community because I was not on the chat. Does this mean anyone _must_ join the slack if they have to be consi... -
- >Next time tell us BEFORE you disable something, OK?
I will make an effort next time. Can you join ruby-lang slack team again?
We discuss the internal workflow on this slack.
-
- hsbt (Hiroshi SHIBATA) wrote:
> done. I disabled the writable operation of trunk branch on svn.ruby-lang.org
Next time tell us BEFORE you disable something, OK? -
- @k0kubun Thanks to your works.
I enabled and disabled some changes on our repository.
>Operations
> ...
done. I disabled the writable operation of trunk branch on svn.ruby-lang.org
> Also prohibit force-push to git.ruby-lang.o... -
- broken by 5da52d1210625fb00acd573b3f32281b4bde1730
-
-
- * [Misc #14632] git.ruby-lang.org
* See [5da52d1210](https://github.com/ruby/ruby/commit/5da52d1210625fb00acd573b3f32281b4bde1730). I committed tentative `RUBY_REVISION`/`RUBY_DESCRIPTION` behaviors for preview1 as follows. Is it okay... -
- Please comment your favorite ticket numbers you want to ask to discuss with your *SHORT* comment or summary.
(your summary/comment will help us because we don't need to read all of ticket comments)
*DO NOT* discuss then on this ticke... -
-
- from Subversion.
This behavior is tentative and not discussed well. The point of
discussion will be just the length of commit hash, and I thought we
should include this kind of change in 2.7.0-preview1 release even before
the length is ... -
- https://github.com/ruby/ruby/commit/303dc3c591e324b6bbc691326d8bea76fe3b8fda
-
- On ruby_2_5, I bisected the fix to be ruby_2_5|r65582.
With r65581:
```
../Bug-15766.rb: unexpected return
C:/Dev/msys64-20161025/opt/ruby_2_5/lib/ruby/gems/2.5.0/gems/minitest-5.11.3/lib/minitest.rb:60: [BUG] Segmentation fault
... -
-
-
-
- This issue depends what compiler is used.
Could you show what is your compiler and environment? -
10:04 AM Misc #15630 (Closed): Clarification on Comparable documentation
- Applied in changeset commit:ruby-git|f005ccc771574e8e4e17b7a35c19b352e0b7dc73.
----------
Clarify requirements of <=>
A return value of <=> is automatically converted to -1, 0, or 1, so
other values can be returned. [Misc #15630] -
-
- A return value of <=> is automatically converted to -1, 0, or 1, so
other values can be returned. [Misc #15630] -
- Whether an issue is "Bug" or "Feature" practically depends whether the fix should be backported or not.
Anyway as far as I understand, Ruby has following categories of characters.
* First character for constants (upper case)
* First... -
- https://www.ruby-lang.org/en/news/2019/03/31/support-of-ruby-2-3-has-ended/
- 02:33 AM Revision beaddd1d (git): Now only supports Git repository
- 01:06 AM Revision b26a7c8d (git): * remove trailing spaces.
-
- Backported 4c570abf77 to Japanese
- 12:55 AM Revision 44a468cc (git): * remove trailing spaces.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67701 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- We started to switch from SVN to Git. Because GitHub would be more
reliable than our single-host cgit, I continued to list GitHub mirror
repository in the first place.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67700 b2dd03c8-39d...