Activity
From 05/25/2019 to 05/31/2019
05/31/2019
-
11:00 PM Misc #15892 (Closed): Appveyor - full MSYS2 update - 5:25
- Thanks. I managed to pass the CI with the idea in https://github.com/ruby/ruby/pull/2217, but it added 8 minutes, not 5.
I'm slightly reluctant to add 8 minutes to msys2 build time, so I'll consider applying it when AppVeyor fails on ... -
09:42 PM Misc #15892: Appveyor - full MSYS2 update - 5:25
- I used:
```
pacman -Syuu --noconfirm --noprogressbar --nodeps
pacman -Suu --noconfirm --noprogressbar --nodeps
```
With the current state of the Appveyor MSYS2 system, both are needed. The -y option updates the package database.... -
- Thanks to share. As the last appveyor.yml update has worked for only 3 days, the "full MSYS2 update" would be worth trying.
However, as I'm not familiar with MSYS2 and pacman that much, I don't know what exact code you imagine by "ful... -
- Just tried a full MSYS2 update on Appveyor, and it took 5:25.
The most recent Ruby build (which finished within minutes of the MSYS2 update) took about 39 minutes, but it may have been waiting. Past builds occasionally take 45 to 50 ... -
08:29 PM Bug #15876: 1.to_s.encoding != Encoding.default_internal
- Hanmac (Hans Mackowiak) wrote:
> is there a way to see if two encoding objects are compatible or can that only be checked on the string?
`Encoding.compatible?` can take Encoding arguments too:
> Encoding.compatible?(Encoding::... -
05:37 PM Bug #15876: 1.to_s.encoding != Encoding.default_internal
- There is `Encoding.compatible?` which might help to check if two strings/symbols has a common encoding
@naruse i don't know if you are the right contact person for this, but is there a way to see if two encoding objects are compatible... -
04:10 PM Bug #15876 (Feedback): 1.to_s.encoding != Encoding.default_internal
- What is the problem you are actually troubled with?
If it is just a testing problem, I feel it should just use correct assertions.
But if there's a frequent pitfall, I may reconsider it. -
07:31 PM Bug #15807: Range#minmax is slow and never returns for endless ranges
- i had the same problem with minmax in Range.
I made a MR
https://github.com/ruby/ruby/pull/2216 -
05:44 PM Bug #15891 (Closed): FrozenError when assigning frozen class to constant
- Applied in changeset commit:git|c1e52997870a63168835fde49562cb3c822c968a.
----------
Fix FrozenError when assigning frozen class to constant
* variable.c (set_namespace_path): modules/classes can get named
by assignment to constant, ... -
01:25 PM Bug #15891 (Closed): FrozenError when assigning frozen class to constant
- This code used to work in Ruby 2.6 and before: `C = Class.new.freeze`. Now it raises a FrozenError for class and module instances, while other frozen things seem to still work.
I am not sure if this is a bug or an intentional change. ... -
- * variable.c (set_namespace_path): modules/classes can get named
by assignment to constant, even if frozen. [Bug #15891] -
- This issuse is caused by MSYS2 changing from using ncurses to pdcurses.
Appveyor's MSYS2 is so out-of-date that partial updates are 'troublesome'... -
-
-
- 03:03 PM Revision 8fc552ad (git): * 2019-06-01
-
03:02 PM Revision 88770c2a (git): Support Home and End key to move to beg and end
-
02:24 PM Bug #15886: return in rescue block breaks Timeout.timeout
- moio (Silvio Moioli) wrote:
> Well, as a Timeout.timeout user I would like to be able to wrap any code in a block and have a guarantee it will actually terminate after the specified number of seconds - no matter how the wrapped code loo... -
12:26 PM Bug #15886: return in rescue block breaks Timeout.timeout
- Well, as a Timeout.timeout user I would like to be able to wrap any code in a block and have a guarantee it will actually terminate after the specified number of seconds - no matter how the wrapped code looks like and especially if it is...
-
-
-
01:15 PM Revision 913661cc (git): Bump irb version to 1.1.0.pre.1.
- Becausee the current irb support reline and have many of changes.
-
12:58 PM Misc #15723: Reconsider numbered parameters
- I prefer the single @ syntax as well. It will be a huge help since I don't like using the (&:method) syntax. I like avoiding syntax that intuitively makes code *unnecessarily* slower without much syntactical benefit, even for a languag...
-
- @shevegen Please do not write such long comments, and express your opinion more concisely.
This helps everyone to read discussions faster and get the main point.
> This is based on the assumption that there has to be a "fix" at all i... -
- duerst (Martin Dürst) wrote:
> Can you tell us where and when that talk was given?
At the Ruby committer meeting before RubyKaigi. -
12:00 PM Misc #15723: Reconsider numbered parameters
- > TBH, I wish the multi numbered parameters feature would not make it in
> ...
This is based on the assumption that there has to be a "fix" at all in the first place
to begin with; and if so, what the assumed "fix" would then be.
Na... -
07:00 AM Misc #15723: Reconsider numbered parameters
- Eregon (Benoit Daloze) wrote:
> * Here is a [link to the slides I presented](https://docs.google.com/presentation/d/1oNnZQaYj9yiGTzKV0MB13dxX3Z7_mOGfzhOJIucNfGg/edit?usp=sharing), which highlight most Rubyists who answered my poll disag... -
- [ruby-dev:50790]
* https://www.meti.go.jp/press/2019/05/20190520006/20190520006.html
* https://www.meti.go.jp/press/2019/05/20190520006/20190520006-2.pdf
[ci skip] -
- to get rid of side-effect by existing .irbrc file.
-
-
07:11 AM Bug #15887 (Closed): Process.argv0 can return bad values in Ruby 2.5
- Applied in changeset commit:git|ea42423908ed055f9039b1dce6e9a232a3b2dd90.
----------
Keep vm->orig_progname alive
`vm->orig_progname` can be different from `vm->progname` when user
code assigns to `$0`. While `vm->progname` is kept ali... -
- I've reviewed and tested the pull request and it appears to be the correct fix to me. I confirmed this does crash immediately on 2.5.5, 2.6.3, 2.7.0-preview1, and trunk, and the fix makes it no longer crash. This fix should be backporte...
-
- Here's is a one line crasher: `ruby -e '$0 = "hi"; 4.times { GC.start }; Process.argv0.class'`
This crashes 2.5.5 and 2.6.3, but 2.4.6 seems to be immune. Bisect points to 478003f6df40dc79d33c6ec86919f2dde07284be.
I have a PR for this:... -
- * internal.h (UNALIGNED_MEMBER_ACCESS, UNALIGNED_MEMBER_PTR):
moved from eval_intern.h.
* compile.c iseq.c, vm.c: use UNALIGNED_MEMBER_PTR for `entries`
in `struct iseq_catch_table`.
* vm_eval.c, vm_insnhelper.c: use UNALIGNED_MEMB... -
- `vm->orig_progname` can be different from `vm->progname` when user
code assigns to `$0`. While `vm->progname` is kept alive by the
global table, nothing marked `vm->orig_progname`.
[Bug #15887] -
- Could you try newer version, 2.5.5, 2.6.3 or 2.7.0-preview1?
-
-
04:50 AM Feature #15665: Cannot compile socket extension on Mojave
- nobu (Nobuyoshi Nakada) wrote:
> Applied in changeset commit:git|fe3ff5afb07e171fd950623c69abfbabbb2762a3.
> ...
I have verified that the changeset works for 2.6 on my machine. It is currently in trunk, which would go to 2.7 eventually... -
-
-
-
- Only if the short revision differs from the full revision.
-
01:41 AM Bug #11512 (Closed): DelegateClass.#public_{instance_}methods are returning difference values.
- Applied in changeset commit:git|e8c710b11a02c6ab82b358fc671a14f378cb1974.
----------
Fix visibility of some methods when using DelegateClass
Public instance methods added to a delegated class after the
creation of the delegate class we... -
- Applied in changeset commit:git|1cd93f1cdfbe6f7e71b05b3f8e707f21d70e94ba.
----------
Allow DelegateClass() to module_eval given block
Methods that return classes often module_eval the given block
(e.g. Class.new and Struct.new). This ... -
- Public instance methods added to a delegated class after the
creation of the delegate class were not returned by the
public_instance_methods class method of the delegate class.
Protected instance methods in the delegated class when the
... -
- Methods that return classes often module_eval the given block
(e.g. Class.new and Struct.new). This allows DelegateClass to
work similarly. This makes it easier to use DelegateClass
directly without subclassing, so as not to create an ... -
05/30/2019
-
11:02 PM Bug #15890 (Closed): psych.so is not deterministic
- psych.so is not binary identical across builds (it's hash changes), as the order of its sources is random.
You probably want to add a sort to
https://github.com/ruby/ruby/blob/6a5e89e23c433199f926d757481bc3c29fce7854/ext/psych/extcon... -
- * [Misc #15723] Reconsider numbered parameters.
* To matz: Could you agree on Jeremy's single-argument patch? -
- As it failed to commit like:
https://app.wercker.com/ruby/ruby/runs/mjit-test1/5cefd8a8105780001c4f2d5d?step=5cefdd1e48fad200077fa3f8 -
- @matz Could @jeremyevans0 merge his patch for single argument?
* The original author proposed a single argument (#4475).
* Jeremy who proposed the currently implemented syntax [said](https://bugs.ruby-lang.org/issues/15723#note-91)... -
- Let's say we are in progress to write `"foo"`:
```
irb> "fo
```
at this moment, nothing is wrong.
It would be just a normal way to write `"foo"`.
Prior to this commit, the `fo` part was warned because of
5b64d7ac6e7cbf759b859428f12553... -
- because 5b64d7ac6e7cbf759b859428f125539e58bac0bd made it hard to
understand #colorize_code for me and this change is needed for my next
commit. -
-
-
-
07:08 PM Bug #15889 (Closed): Enumerator#each_slice size FloatDomainError with infinite enumerator
- Calling `#size` on an infinite `each_slice` Enumerator results in a `FloatDomainError` exception:
``` ruby
1.step.size # => Infinity
1.step.each_slice(2).size # => FloatDomainError
```
```
Traceback (most recent call last):
..... -
05:05 PM Bug #15888 (Closed): Segmentation fault at 0x000070000afc2450 ruby 2.5.1p57 (2018-03-29 revision 63029) [x86_64-darwin18]
- This happens on a Ruby on Rails app which has recently been upgraded from Ruby version 1 to ruby version 2.5.1
-
- I was able to run the benchmarks in a Linux virtual machine. This includes the benchmarks I added for `File.realdirpath` and for `File.realpath` where the paths that do not exist. `File.realdirpath` always uses the emulated code on Linu...
- 03:01 PM Revision c55db6aa (git): * 2019-05-31
-
-
- Not to download Unicode data files at building from the packages.
-
-
12:16 PM Bug #15884: Time module fails to identify timezone correctly - Thanks for such a good explanation John! What you said makes perfect sense so I'm happy to close this as "invalid", or whatever is the most appropriate status. Unfortunately, I don't seem to be able to update the Status on this ticket.
-
-
-
- * parse.y (here_document): adjust token to the here-doc identifier
in compile_error when a here-document misses the closing
identifier. -
-
-
-
-
- 09:14 AM Revision 39ee412b (git): merge revision(s) dcb6a6ae3e2b8a3e298e7f0d4a3e7f8ff102a30e:[Backport #15845]
- Windows simply causes an error to open invalid path
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/branches/ruby_2_5@67709 b2dd03c8-39d4-4d8f-98ff-823fe69b080e - 08:12 AM Revision 106843d8 (git): * expand tabs.
-
08:12 AM Revision 5fc9f000 (git): reorder bitmap clearing.
-
- pinned_bits are not used frequently (only GC.compact use it) so
move it at the end of struct heap_page. -
- Usually PINNED_BITS are not needed (only for GC.compact need it)
so skip updating PINNED_BITS if the marking is not by GC.compact. -
- so that we can colorize binding.irb source lines.
-
-
-
-
-
-
- * parse.y: continue parsing the rest of the here-document starting
line, after the terminator was not found. -
-
-
- This reverts commit 05bc14d81a1d7f6af826a92371aeff0c3fb2a67e.
We have decided that the cost of reintroducing support for 1.8
BASERUBY outweighs the benefit. If you are still using 1.8 and want
to build master/trunk, build and install t...
05/29/2019
-
- Interesting. I just did Process.argv0 in irb and irb crashed right away.
If I put it into a .rb file it works fine. I haven't systematically tested
what causes the issue or whether my crash is related to the one here (I am
on linux ... -
07:43 PM Bug #15887 (Closed): Process.argv0 can return bad values in Ruby 2.5
- MacOS 10.14.5 on a clean (source, using ruby-install) installation of Ruby 2.5.5
```
$ ruby --version
ruby 2.5.5p157 (2019-03-15 revision 67260) [x86_64-darwin18]
$ gem install vault vcr virtus webmock webrick
$ echo Process.argv0 |... - 07:13 PM Revision 5867e51e (git): * 2019-05-30
-
- in GC.compact.
While `in_jit` is false, GC.compact is allowed to run and it may be
moving ISeq-related pointers. So calling rb_iseq_path() when `in_jit`
is true is illegal. -
- I don't believe this is a bug or specifically related to `Timeout` (or to the other issues you linked). If an exception is raised and an `ensure` or a `rescue` block does an explicit `return` (or a non-local exit such as `throw`), the e...
-
- Passing `Timeout.timeout` a block with a rescue clause that contains a return statement prevents `Timeout::Error` to be raised as expected.
Reproducer:
``` ruby
require 'timeout'
begin
Timeout.timeout(1) do
begin
... -
- * lib/irb/color.rb (IRB::Color.colorize_code): colorize
`compile_error` part as same as `on_parse_error`. -
- * lib/irb/color.rb (IRB::Color.colorize): get rid of nesting string
interpolations not to confuse ruby-mode.el -
- * parse.y (parse_atmark): return EXPR_END or EXPR_ENDFN, depending
on the previous state, even incomplete names consistently. -
- This reverts commit ab7a6e1a1651d82d327d155b78a8e3af1d976707.
-
- The 559dca509d2a98584b09c7d9a6d74749ce793ad7 contains an excess range in
using "require". -
10:29 AM Bug #15885 (Closed): Duplicated `:raise` tracepoint event when exception inside `load` call happens
- Hi!
A long time ago, [this ruby-core change](https://github.com/ruby/ruby/commit/1998039ea4f867583d7e37ce200a88490707c330) broke a test in byebug related to post-mortem debugging. See https://github.com/deivid-rodriguez/byebug/issues/... -
-
- * ext/ripper/lib/ripper/lexer.rb (Ripper::Lexer#scan): parses the
code and returns the result elements including errors.
[EXPERIMENTAL] -
- by showing line number only when it's Fixnum.
When it's not Fixnum, we need to call a method to know the line number. -
- because FIX2INT might crash by moving method entry pointer:
http://ci.rvm.jp/results/trunk-mjit@silicon-docker/2063412 -
-
- String#lines seems to return Enumerator in Ruby 1.9.3, and it does not
respond to #delete_if https://travis-ci.org/ruby/ruby/jobs/538559919 -
- This has not worked since the merge https://travis-ci.org/ruby/ruby/jobs/538438184
-
-
-
-
04:16 AM Revision aee36bf1 (git): Fix Possible Control flow issues (DEADCODE)
- Coverity Scan says `Execution cannot reach this statement: "poison_object(v);"`,
so do nothing when `ptr` is always 0 without address_sanitizer. -
04:01 AM Revision e04d10b2 (git): test/rubygems/test_gem_stream_ui.rb (test_ask_for_password): extend the timeout
- for Solaris.
https://rubyci.org/logs/rubyci.s3.amazonaws.com/unstable10s/ruby-master/log/20190528T191908Z.fail.html.gz -
- This reverts commit c7f3c222c9b82736c993419daa6bfb643e5c0793.
-
- Colorize `compile_error` parts as well as `on_parse_error` parts.
-
-
-
-
- Closes: https://github.com/ruby/ruby/pull/2208
Merging the PR for fixing AppVeyor msys2 failure related to GCC 9 like:
https://ci.appveyor.com/project/ruby/ruby/builds/24877992/job/ned5k4k5rwxnld5j -
- and dependent commits c67934b1c3b40dda5f170b032423e520511c68dd and
f0d1dc5cee87dfb023cb43a2db9bcdef5a8dee8f.
RubyCI and ci.rvm.jp are almost dead by timeout since this commit.
---
Revert "Skip a reline test hanging on Wercker since 3b...
05/28/2019
-
- pointers.
Instead of 4fe908c1643c3f355edd787bb651aefb53b996c0, just locking the MJIT
worker may be fine for this case. And also we might have the same issue
in all `gc_compact_after_gc` calls. -
- People seem to consider BASERUBY is either 1.8 or 1.9 now. Since this
file may be executed by BASERUBY from file2lastrev.rb, I think we should
not rely on Ruby 2.0 in this file for now. -
- is yes.
We ignored the failure status of file2lastrev.rb on 73da429c36c, but it
was for an environment without BASERUBY. I think we should skip running
file2lastrev.rb on HAVE_BASERUBY=no, and run it and check the status on
HAVE_BASERUB... -
- like https://app.wercker.com/ruby/ruby/runs/mjit-test1/5cedad11105780001c4e7001?step=5cedaf6b48fad200076fe77b
-
- because it's hard to identify which test causes a hang for now.
-
-
-
-
-
- We have no clear assertion or check of BASERUBY requirement.
I want to make the current situation more explicit.
I'm NOT saying we should support Ruby 1.9.3 here,
but I'm just checking the situation as per 05bc14d81a1d7f6af826a92371aeff... -
-
-
-
-
- This has been unused since b7f5c573ef20dbbf5534ee3a45625c7f9d45f2ec.
-
- As ko1 added some improvements on GC.compact, I want to check if it
solved the problem too. -
03:37 PM Bug #15884: Time module fails to identify timezone correctly
- I think this shows the logic behind what is occurring here.
On my system
Time.new(2002, 12, 1).zone
=> PST
(Time.new(2002, 12, 1) + 60 * 60 * 24 * 180).zone # Add 180 days
=> PDT
Time.new(2002, 12, 1).utc.zone
=> UTC
(Time... - 03:05 PM Bug #15884 (Rejected): Time module fails to identify timezone correctly
- I think the following snippet is the best summary of the problem I could write:
```
irb(main):001:0> Time.new(2012, 12, 1).utc?
=> false
irb(main):002:0> Time.new(2012, 12, 1).zone == 'UTC'
=> true
``` - 03:07 PM Revision abd55695 (git): * 2019-05-29
-
- * parse.y (warn_space_char_code): warn whitespace characters
escaped with meta/control prefix. -
-
- phluid61 (Matthew Kerwin) wrote:
> `a|:b` means `a | :b` and `a=:b` means `a = :b`
Yes I implied that a space is necessary for |: or =: to be distinguishable. It's better to have that requirement than have the three-character operat... -
11:41 AM Feature #15799: pipeline operator
- ```ruby
1.. |> take 10 |> map {|x| x*2} |> (x)
```
I believe that the ONLY sane reason for the new operator is ending the long chain with "...and now, put it into variable". The rest is total mistery, however you look at it, e.g. wh... -
09:33 AM Feature #15799: pipeline operator
- `a|:b` means `a | :b` and `a=:b` means `a = :b`
-
- konsolebox (K B) wrote:
> nobu (Nobuyoshi Nakada) wrote:
> ...
Or `=:` which is the reverse of Pascal's assignment operator. Personally I would want it to have it as an alias to `|:` than replace `|:` because `=:` would look good if i... -
- nobu (Nobuyoshi Nakada) wrote:
> duerst (Martin Dürst) wrote:
> ...
`|>=` looks heavy. Please consider `|:` instead.
-
11:26 AM Feature #10344: [PATCH] Implement Fiber#raise
- Shortly after I started to work on a library implementing algebraic effects (https://github.com/dry-rb/dry-effects) I stumbled upon lack of `Fiber#raise`. From the user POV it is important to signal improper use of effects with a meaning...
-
09:54 AM Misc #15874: DevelopersMeeting20190613Japan
- * [Feature #15777] `Module#autoload?(cname, inherit=true)`
* By default `autoload?` also check in the ancestors chain, such option would be consistent with `Module#const_defined?` and totally backward compatible.
* For more context... -
- It's clear that the order of evaluation has to be the way it is currently. But in this case, `if` just sounds wrong, not only because of examples such as `puts 1 if condition`, but also because of general English.
So I think changing ... -
- rb_gc_finalize_deferred() is remained for compatibility with
C-extensions. However, this function is no longer working
from Ruby 2.4 (crash with SEGV immediately).
So remove it completely. -
-
-
-
05:28 AM Feature #15879: Proposal: Time#to_i accepts :unit keyword
- > In contrast to this, your proposal with Time#to_i seems to return rounded results even though the method name is to_i. I think this is confusing. Is this your intention?
It is not important whether the result is rounded or truncated... -
-
-
- Here malloc() is enough because all elements of the page_list
will be overwrite. -
-
- The size of page_list is heap_eden->total_pages, but
init_cursors() assumes the size of page_list is `heap_allocated_pages`.
This patch fix it. -
-
-
- `heap_pages_sorted` includes eden and tomb pages, so we should not
use tomb pages for GC.compact (or we should move all of tomb pages
into eden pages). Now, I choose only eden pages. If we allow to
move Zombie objects (objects waiting fo... -
-
- followed up ae2a904ce9bffedee7d110dc60fd51c0a2879a5b
- 01:07 AM Revision 165ddfda (git): * remove trailing spaces.
-
- The old certificate files (for example, test/rubygems/ca_cert.pem) were
signed by SHA1. This message digest is considered too weak and rejected
by OpenSSL 1.1.1 or later. Because of this, the test suite does not
pass on Debian 10.
htt... -
- but on "master" branch.
For Pull Request, I changed the approach from
d9b338a53f520b2dbb05555f18b8de8072300f40 and
277e68825a8e4d0e6503a32e41f8b1b6c078b567. -
- `FrozenError#receiver` was added recently for getting the related object programmatically. However, there are cases where FrozenError is raised and not handled, and in those cases the resulting error messages lack detail, which makes de...
-
-
-
- * parse.y (parse_atmark): numbered parameter name is not allowed
as a symbol regardless the context.
05/27/2019
-
-
09:01 PM Bug #15877: Incorrect constant lookup result in method on cloned class
- I tested this on 2.5, 2.4 and the behavior is the same there. Also this applies to subclasses as well. The first class READ determines the values for all of them.
``` ruby
class Unrelated
TEST='UNRELATED'
def test
T... -
-
-
-
-
-
05:13 PM Bug #15882 (Closed): OpenSSL::X509::Name.parse usage
- in ruby 2.5 and 2.6 the OpenSSL::X509::Name.parse_ssl method requires strings to start with forward slashes to use it as a delimiter
-
-
-
04:37 PM Bug #15880 (Rejected): Wrong precedence of the if modifier in pattern matching
- This is necessary so the `if` can depend on the variables of the matching, e.g. `in [Integer => x] if x.odd?`
-
01:51 PM Bug #15880 (Rejected): Wrong precedence of the if modifier in pattern matching
- When "If" is used as an "If modifier" it runs before the expression that it wraps:
``` ruby
=> puts 1 if (puts 2; true)
2
1
```
However, when it's used in the pattern matching destructuring runs first:
``` ruby
class A
def d... -
04:32 PM Revision b2b5ed14 (git): Supress duplicated warning
-
- ```ruby
class A
def deconstruct
puts 'deconstruct called'
[1]
end
end
case A.new
in [2]
2
in [1]
1
else
end
```
Currently this outputs:
```
deconstruct called
deconstruct called
=> 1
```
Shouldn... -
-
- This reverts commit 77bfebebc44c5e46ebd156d074081846c037f882.
- 03:20 PM Revision 11778fd2 (git): * 2019-05-28
-
-
-
-
- * parse.y (ripper_token): added Ripper#token which returns the
current token string. [EXPERIMENTAL] -
- I agree with sawa's comment - this is a bit surprising, at the least to me as well. It would
be better to re-use the same idioms, so that ruby users are not surprised by behaviour, if
it can be avoided.
But I think this is only one ... -
- You can also use `Time#to_r`:
```ruby
{
event_id: id,
name: name,
tracked_at: (tracked_at.to_r * 1_000).to_i,
tracked_at_micro: (tracked_at.to_r * 1_000_000).to_i
}
```
At least it's always the same multiply-and-trun... -
10:17 AM Feature #15879: Proposal: Time#to_i accepts :unit keyword
- With `Float#to_i`, the decimal part is truncated, not rounded:
```ruby
123.7.to_i # => 123
123.7.round # => 124
```
In contrast to this, your proposal with `Time#to_i` seems to return rounded results even though the method name ... -
- By analogy from `Time#round`, which takes as an argument an integer representing the precision in decimal places, and from `String#to_i`, which takes an integer, I think that passing an integer representing the number of decimal places w...
-
- I often need Unix time as microseconds or nanoseconds to serialize for other language environments.
For example, Java uses milliseconds(nanoseconds) basically.
In such a situation, current Ruby code is like below.
``` ruby
{
e... -
09:53 AM Misc #15874: DevelopersMeeting20190613Japan
- * [Bug #15733] Inconsistent `__FILE__` and `Kernel#__dir__`
-
01:00 AM Misc #15874: DevelopersMeeting20190613Japan
- * [Feature #15725] Add `Array#reverse_sort`, `#revert_sort!`, `#reverse_sort_by`, and `#reverse_sort_by!`
I would like to propose these methods as the preferred way for developers to create reverse sorted array, which is to call `sort... -
-
-
-
- Fix debug output to dump more useful information on GC.compact
debugging.
check_rvalue_consistency_force() now accepts `terminate` flag
to terminate a program with rb_bug() or only print error message.
GC.verify_internal_consistency use... -
- is_pointer_to_heap(obj) checks this obj belong to a heap page.
However, this function returns TRUE even if the page is tomb page.
This is re-commit of [712c027524].
heap_page_add_freeobj() should not use is_pointer_to_heap(), but
should... -
-
-
- OpenSSL 1.1.1 requires 2048 bits or more. This change will fix:
https://rubyci.org/logs/rubyci.s3.amazonaws.com/debian/ruby-master/log/20190527T003004Z.fail.html.gz#test%2Fopen-uri -
03:27 AM Bug #15875 (Closed): const_defined? behavior inconsistency in 2.6.x series
-
-
02:19 AM Feature #15878: Make exit faster by not running GC
- chrisseaton (Chris Seaton) wrote:
> Is Ruby's GC conservative? So even if a GC is performed at exit are IO buffers guaranteed to be flushed?
Yes and yes. There is a special handling code for process termination, somewhere around htt... -
01:55 AM Feature #15878: Make exit faster by not running GC
- Is Ruby's GC conservative? So even if a GC is performed at exit are IO buffers guaranteed to be flushed?
-
- IMHO it is challenging to make a GC-less exit fundamentally safer than exit!
GC does some important tidy-up tasks for you, like ensuring contents in IO buffers flushed. -
- * lib/irb/context.rb (IRB::Context#evaluate): separate the code
from wrapping lines to propagate the given exception, not to show
the wrapping lines when SyntaxError. -
-
-
- Thank you for your initial feedback. I would like to quote one thing:
> I myself usually use `.sort` and `.sort_by`, and then apply `.reverse` afterwards.
That's definitely the reason why I submit this proposal, because `array.sort...
05/26/2019
-
-
-
-
- 09:32 PM Revision 29c16b30 (git): Add support for history with Reline backend
-
-
-
-
- to avoid cancelling overall build pipeline when stucking there.
-
07:13 PM Feature #15878 (Assigned): Make exit faster by not running GC
- I noticed that exit takes 0.2 ... I'm trying to write a fast cli, so any improvement here would be great or an option to opt-out of certain cleanup tasks
exit! takes a constant low time
```
ruby -rbenchmark -e 'puts Benchmark.realti... -
-
- for improving readability of the condition. It may be slightly faster, or may not.
-
- Applied in changeset commit:git|39eadca76b48fc7841da688f6745e40897ec37ff.
----------
Add FrozenError#receiver
Similar to NameError#receiver, this returns the object on which
the modification was attempted. This is useful as it can pin... - 06:10 PM Revision 5a6c77bb (git): * expand tabs.
-
- Similar to NameError#receiver, this returns the object on which
the modification was attempted. This is useful as it can pinpoint
exactly what is frozen. In many cases when a FrozenError is
raised, you cannot determine from the context... -
- The reason why we were checking lexer state in addition to token was
that we do not want to colorize local variable, method call, etc., while
they share the :on_ident token with a name of method definition which
should be colored as blue... -
-
-
- and sorted the token names alphabetically.
-
- Previous fix was 2993b361333147f6dfb86a153971c22329ffbaf4.
-
-
- 03:45 PM Revision 2a7821b2 (git): * 2019-05-27
-
- * parse.y (here_document): broke the terminator condition down
into each piece, the positional condition, resetting the
dedented here-document indentation, and matching identifier.
suppress a false warning by icc. -
-
01:31 PM Bug #15877: Incorrect constant lookup result in method on cloned class
- Running with `RubyVM::InstructionSequence.compile_option = {inline_const_cache: false}` produces the correct result.
-
- This behavior seems wrong to me:
``` ruby
class Foo
def test
TEST
end
end
Bar1 = Foo.clone
Bar2 = Foo.clone
class Bar1
TEST = 'bar-1'
end
class Bar2
TEST = 'bar-2'
end
# If these two lines are reorder... -
- It has not been stable recently. Let's stop notifying them for now.
-
- * parse.y (parser_yylex): adjust the error indicator of unexpected
fraction part.
before:
~~~
1.2.3
^~~
~~~
after:
~~~
1.2.3
^~
~~~ -
-
- https://rubyci.org/logs/rubyci.s3.amazonaws.com/solaris11s-sunc/ruby-master/log/20190526T052508Z.fail.html.gz
-
- It is a wrapper for Timeout.timeout with the scale factor applied.
-
- * parse.y (parser_yyerror, parser_compile_error): revert
r67224 (e5d10cda07b23682e5e4e64d1324e4d3247d4785) "Flush erred
token". -
- for Solaris.
https://rubyci.org/logs/rubyci.s3.amazonaws.com/unstable10s/ruby-master/log/20190525T211908Z.fail.html.gz -
-
- Please refer to the tests again.
-
- See tests for what kind of things are fixed.
-
- I have added a pull request for this feature (https://github.com/ruby/ruby/pull/2205), and made the necessary changes so it passes Travis and AppVeyor. This changes related to fixing encoding issues and working around issues in glibc re...
-
- Symbol color was made blue as a workaround because it was hard to
distinguish `foo`s in `:foo` and `def foo; end` (both are :on_ident).
But I wanted to make it yellow like pry.
`:Struct` had the same problem in :on_const. Because the :o... -
- @grosser said
> I ran into strange looking test output when I compared .to_s with an expected text, saying that the encoding was different
I thought that some string-comparison assertions (maybe attributed to an external testing fr... -
- @mame:
What @grosser is saying is that
```
p s1.encoding == s2.encoding #=> false
```
but he expects the result to be true. But you are right that what counts is the equality of the strings, not the encodings. -
- @grosser, could you elaborate your problem? I cannot reproduce the warning. What warning did you see? And how?
```
s1 = 1.to_s
p s1.encoding #=> #<Encoding:US-ASCII>
s2 = "1"
p s2.encoding #=> #<Encoding:UTF-8>
p s1 == s2 ... -
- for Solaris.
https://rubyci.org/logs/rubyci.s3.amazonaws.com/unstable10s/ruby-master/log/20190525T131909Z.fail.html.gz
05/25/2019
-
- CI looks clean with https://github.com/ruby/ruby/pull/2200, so I'll be committing it in about a week if there are no objections.
-
- > which is confusing/annoying especially to users that don't know
> ...
I personally finally switched into UTF-8 (oddly enough, primarily due to emoji and
unicode-symbols that can be used for simple indications both on the commandline ... -
- I ran into strange looking test output when I compared .to_s with an expected text, saying that the encoding was different, which is confusing/annoying especially to users that don't know how encodings work in ruby.
1.to_s.encoding shou... -
-
- FWIW, I believe this is a bug.
> When a block is given and the argument is an IO-like object, it may not reach its end after exiting the each method
You mean if the block interrupts the processing with `break`, `return` or `raise`... -
-
-
- Heredoc, %i, :Foo, { 'a': ... }, ...
:'a' is still half-broken. - 03:00 PM Revision a4d44b08 (git): * 2019-05-26
-
-
- because otherwise prompt and other things could be polluted.
-
-
-
-
-
- I added a couple more specs to check that in https://github.com/ruby/ruby/pull/2198/commits/d59a5c93dd4b20aa0898a24fab78a68a2cc84925, but I'm not sure where I can check whether they pass on Windows or not.
-
- New option to direct formats of RDoc to install.
-
- Show document format list to install, not only enabled or disable.
-
- RDoc needs to parse all files at once for the cross-reference.
-
- We might need to do the same thing in IRB::Color now, but I'm not doing
that as I assume ANSI escape sequence does not come from a user input
though Reline. -
- Closes: https://github.com/ruby/ruby/pull/2202
-
- Bisected to commit:bf8cc37b467e1d372e1b01b4d25e9ef6f8cc927f.
Backporting commit:d10451f3fd51f577e704db770de48d05044eb45c to 2.6 fixes this bug. -
-
- pp Ripper.lex('{ "a": 3 }')
=>
[[[1, 0], :on_lbrace, "{", EXPR_BEG|EXPR_LABEL],
[[1, 1], :on_sp, " ", EXPR_BEG|EXPR_LABEL],
[[1, 2], :on_tstring_beg, "\"", EXPR_BEG|EXPR_LABEL],
[[1, 3], :on_tstring_content, "a", EXPR_BEG|EXPR_LABEL]... -
- I think a pipeline operator can be helpful in a functional language, based on my experience with `$` in Haskell. However, I don't think it is a good idea to implement a replacement for the `.` operator just to avoid parentheses. If it...
-
- I did some testing of this recently. With ruby 2.6, the memory use is constant. With ruby 2.5, there is slight memory growth. However, considering the extensive thread changes between ruby 2.5 and ruby 2.6, it is unlikely the particul...
-
- I haven't seen `TestException#test_machine_stackoverflow` SIGSEGV in a long time on OpenBSD. I'm guessing the numerous improvements in the last 5 years make this is no longer an issue. Is anyone else seeing `TestException#test_machine_...
-
- Fixed by commit:832b601e49fd402ec7f30b36a95473131e93ae94. As taca explained, PTHREAD_COND_INITIALIZER should not be used for pthread_condattr_t.
-
- Applied in changeset commit:git|1ef39d8d099f145222b9352423af16a2bab6e05b.
----------
Fix process not waking up on signals on OpenBSD
When using UBF_TIMER_PTHREAD (the UBF handler on OpenBSD), the
timer_pthread_fn function will not sign... - 12:51 AM Revision 809ac9f2 (git): * expand tabs.
-
- When using UBF_TIMER_PTHREAD (the UBF handler on OpenBSD), 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
c... -
- * [Feature #14111] ArgumentErrorが発生した時メソッドのプロトタイプをメッセージに含む
Include the method prototype in the message when `ArgumentError` occurred
* [Feature #14145] Proposal: Better `Method#inspect`
* [Feature #15799] pipeline operator