Activity
From 03/16/2019 to 03/22/2019
03/22/2019
-
10:41 PM Bug #15558: Should Exception#exception copy the backtrace?
- @nobu and other MRI committers: what do you think?
It's somewhat inconsistent with Exception#clone which does copy the backtrace.
Would it make sense to follow JRuby and TruffleRuby's behavior, by copying the backtrace too, here? -
09:18 PM Feature #15724: Optionally suppress output from IRB for assignment expressions
- shevegen (Robert A. Heiler) wrote:
> I don't know if the original suggestion is good as is, but I think it is an interesting idea to support
> ...
The only option is `@context.echo` which turns all echo-ing on or off.
> I don't thin... -
- alanwu (Alan Wu) wrote:
> You can type `a = 1; nil` to stop irb from calling inspect on the assignment expression result, just FYI.
Yes, this feature is so that one doesn't have to remember to do that after each expression they would... -
05:05 PM Feature #15724: Optionally suppress output from IRB for assignment expressions
- While I use a similar approach suggested by Alan Wu - and there is nothing wrong with that - I think
it may still be useful to have a simpler toggle-way for silencing output by default (or, via a toggle).
I don't know if the original... -
03:49 PM Feature #15724: Optionally suppress output from IRB for assignment expressions
- You can type `a = 1; nil` to stop irb from calling inspect on the assignment expression result, just FYI.
-
- Most REPLs I've used don't print out the output of assignment expressions like `a = 1`. Being able to suppress this output is very useful when you have a string which is essentially a blob, an object with a large string representation, ...
-
08:51 PM Feature #15626: Manual Compaction for MRI's GC (`GC.compact`)
- One problem with automatically compacting on full GC: compaction appears to require two full GCs to do its thing. It might be possible to integrate this into Ruby's normal cycle. But I don't think this is designed for that as-is.
Aaro... -
09:21 AM Feature #15626: Manual Compaction for MRI's GC (`GC.compact`)
- I got segfault with this patch
I added 1 extra change to fix compile error on MacOS
https://github.com/ruby/ruby/compare/trunk...PikachuEXE:feature/gc-compact/15626
Installed via
rvm install ruby-head --reconfigure --repo https://g... -
07:22 PM Misc #15723: Reconsider numbered parameters
- @matz wrote:
> I am not fully satisfied with the beauty of the code with numbered parameters, so I call it a compromise.
@shevegen wrote:
> ...
Sorry, but it sounds like the new feature is an ugly compromise ...
I learned Ruby – ... -
04:06 PM Misc #15723: Reconsider numbered parameters
- alanwu (Alan Wu) wrote:
> The feature isn't even release[d] and we have confusion already #15708.
That is because it has not been documented yet. After the comments from the developers, now I understand it. There is no problem unders... -
- I don't like this feature because it adds a special case to the meaning of `@`.
Before this, I can look at `@` and understand that it's an instance variable, now there is extra mental overhead.
Every new feature added to the language... -
02:18 PM Misc #15723: Reconsider numbered parameters
- @sos4nt, I agree with you. Naming a parameter is good, I think.
By the way, The Ruby Style Guide that you mentioned says:
```
# bad
names.map { |name| name.upcase }
# good
names.map(&:upcase)
```
I dislike this style too... -
- I personally like the change. I think it is good for quick debugging.
Stefan picked only one example, though:
Hash.new { @1[@2] = "Go Fish: #{@2}" }
But who is to say that ruby users have to (only) write code like the above?... -
01:54 PM Misc #15723 (Feedback): Reconsider numbered parameters
- Yes, I admit `{ @1[@2] = "Go Fish: #{@2}" }` is cryptic. But `{@1 * @2}` is not. So use numbered parameters with care (just like other features in Ruby). The **possibility** to make code cryptic itself should not be the reason to withdra...
-
- I just learned that *numbered parameters* have been merged into Ruby 2.7.0dev.
For readers not familiar with this feature: it allows you to reference block arguments solely by their *index*, e.g.
```ruby
[1, 2, 3].each { |i| puts ... -
05:36 PM Bug #15712: DateTime#=== should be defined and compare date and time instead of just the date
- @nobu Not sure why I wrote false (maybe I confused === with == in my testing), I'm getting `true` on ruby 2.5.3, 2.6.1, 2.6.2 and ruby-head (2.7.0 (same as the one registered in the issue)).
```
rvm ruby-head do ruby -e 'require "dat... -
- This is an interesting idea. I have not thought through all implications but not withholding
that, I like it so +1 from me. I think matz has to decide whether this may be useful. Since
I love `case`/`when` in ruby in general, any extens... -
- If such method, if any, should be rather defined on `Object`, that would be fine. I was not sure whether I should have requested this for `Kernel` or for `Object`.
-
- osyo (manga osyo) wrote:
> How about `Enumerable#case?` ?
> ...
What is to be evaluated is `bar`, not the objects that you put in the arrays. `bar` has to be the receiver. That also matches with how `case`-construction works. Furtherm... -
09:13 AM Feature #15722: `Kernel#case?`
- How about `Enumerable#case?` ?
Comparing with `===` like `Enumerable#include?`.
```ruby
bar # => "bar"
["foo", "bar", "baz"].case? bar # => true
["qux"].case? bar # => false
[Symbol, String].case? bar # => tru... -
- I often want to use `===` to match a single object on the right side against multiple objects on the left, as is used in `case`-constructions, just to return a truth value, and end up writing like this:
```ruby
bar # => "bar"
flag1 ... -
03:32 PM Misc #15610: Could bundler & rubygems be shipped in site_ruby?
- Just for completeness, this is my proposal:
https://bugs.ruby-lang.org/issues/5617 -
- svnpenn (Steven Penny) wrote:
> shevegen (Robert A. Heiler) wrote:
> ...
It's actually only 1 way. The `--` is just a command line option/argument parsing convention to mark an explicit break between options and arguments. It's useful ... -
- Since this ticket is closed, I've opened a new one to express my concerns:
https://bugs.ruby-lang.org/issues/15723 -
06:56 AM Feature #4475: default variable name for parameter
- gkemmey (Gray Kemmey) wrote:
> Is there a reason to do this other than to save some typing? I'm not sure we've proposed any terribly real-world cases here where this made code better.
Exactly my thought: Why? what will this make bett... -
12:31 AM Feature #4475: default variable name for parameter
- For those who want to change anything, I suggest to create new feature issues. It doesn't make sense to continue discussing a closed issue.
-
12:19 AM Feature #4475: default variable name for parameter
- As I'm reading through this I am warming up to this idea. However, I would prefer to keep `@` for instance variables.
Ruby currently does not allow naming variables or methods starting with a number. Could we utilize this?
```ruby... -
11:04 AM Revision 56557ec2 (git): [DOC] fix markups [ci skip]
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67337 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
10:22 AM Bug #15384: ssl_certs are duplicated in RubyGems and Bundler
- I did update the latest patch: https://github.com/bundler/bundler/pull/7035
-
- Attached the patch for this feature.
-
- I might got a similar issue with 2.6.2 (also crash at os_log_type_enabled + 627)
https://bugs.ruby-lang.org/issues/15623#note-2
See update #2 -
07:57 AM Revision c671f836 (git): add debug counters to count call cache fastpath.
- Add counters to count ccf (call cache fastpath) usage.
These counters will help which kind of method dispatch
is important to optimize.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67336 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- I came up with the method name:
```ruby
solid?
```
-
06:25 AM Feature #15721 (Open): optimize comparison of special const
- ## Description
optimize comparison between special consts in `comparable_by_identity`.
it is called from `==` .
## Benchmark
```ruby
num_array = Array.new(1_000_000) { 1 }
num_array.include? nil
# 0.156 => 0.0089 ... -
- 2.0.0 リリース時のディスカッションなので閉じておきます。
- 12:21 AM Revision 4d2bac1f (git): * 2019-03-22
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67335 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
- 12:21 AM Revision a433f2c5 (git): * expand tabs.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67334 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- similar idea to r67315, provide the following optimization
for method dispatch with lead and kw parameters.
(1) add a special branch to check passing kw arguments to
a method which has lead and kw parameters.
ex) def foo(x, k:1)...
03/21/2019
-
11:33 PM Bug #15718: YAML raises error when dumping strings with UTF32 encoding
- I see. There are other regexp based code similar to what `Psych::Visitors::YAMLTree.visit_String` does. Not sure if testing for encoding before matching as I initially proposed is the way to go. What else do you suggest that could be a f...
-
10:04 PM Bug #15718: YAML raises error when dumping strings with UTF32 encoding
- rubenochiavone (Ruben Chiavone) wrote:
> Since it relates to mismatch of regex and YAML text encoding a possible fix is to only attempt to match the text when encoding matches or when text encoding is `ascii_compatible?`. WDYT?
What ... -
- Since it relates to mismatch of regex and YAML text encoding a possible fix is to only attempt to match the text when encoding matches or when text encoding is `ascii_compatible?`. WDYT?
Still I'm not sure why on other versions it wor... -
- It may be related to a code range bug.
By adding `o.valid_encoding?` to `Psych::Visitors::YAMLTree#visit_String`, the error raises in ruby 24 too. -
08:07 PM Bug #15720 (Closed): SystemStackError when referencing a refinement in a module that isn't used
- ```ruby
module M1
refine Kernel do
def foo
'foo called!'
end
end
end
module M2
refine Kernel do
def bar
'bar called!'
end
end
end
using M1
puts foo
puts bar
```
Expected:
... -
04:24 PM Feature #15628: init_inetsock_internal should fallback to IPv4 if IPv6 is unreachable
- > Net:HTTP with timeout (Net::OpenTimeout) after after 60 seconds
I meant "Net:HTTP will timeout (Net::OpenTimeout) after 60 seconds".
Any suggestion on fixing this would very helpful 
01:32 PM Bug #15649 (Closed): Dir.glob regression with braces and Windows drive letters - Applied in changeset trunk|r67332.
----------
dir.c: fix Dir.glob starts with brace
* dir.c (ruby_glob0): expand braces if a glob pattern starts with
brace.
[ruby-core:91728] [Bug #15649] -
01:32 PM Revision 0f63d961 (git): dir.c: fix Dir.glob starts with brace
- * dir.c (ruby_glob0): expand braces if a glob pattern starts with
brace.
[ruby-core:91728] [Bug #15649]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67332 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67331 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
06:48 AM Revision 969156ce (git): Check argument_arity_error condition in inlinable_iseq_p
- to avoid inlining a method call when it becomes argument_arity_error,
fixing a potential bug.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67330 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67329 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- ありがとうございます。とりあえず明らかな型バグがあったので修正しました。
```
$ ./miniruby /tmp/test.rb
Traceback (most recent call last):
1: from /tmp/test.rb:in `each'
/tmp/test.rb:3:in `foo': error! (RuntimeError)
```
↑のように、嘘の行番号は出なくなりました。 -
- Applied in changeset trunk|r67326.
----------
Fix a wrong lineno in backtrace for cfunc
lineno is an int, and INT2FIX(0) was assigned.
[Bug #15719] [ruby-core:91911] -
03:13 AM Bug #15719 (Closed): to_enum を使用した場合にバックトレースが意図しないものになる
- to_enum を使用するとバックトレースの呼び出し元が実行ファイルの1行目 each と出力されます。
再現コードの 8 行目や、to_enum に指定した foo メソッドがバックトレースに出てくるべきかと思います。
### 再現コード
```ruby
def foo
return to_enum(__method__) unless block_given?
raise 'error!'
yield 1
end
enum ... -
- because it's not used outside vm*.c, and also having non-static function
without MJIT_STATIC is harmful for mswin JIT system.
I hope this fix mswin test failure starting from r67315.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67... - 05:59 AM Revision 3c4b7898 (git): * expand tabs.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67327 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- lineno is an int, and INT2FIX(0) was assigned.
[Bug #15719] [ruby-core:91911]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67326 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- because stderr did not have sufficient information
https://ci.appveyor.com/project/ruby/ruby/builds/23242505/job/dirugxujk70nnhp6
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67325 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- ```
To prevent this, a new "pinning" table was introduced. Any object marked via
rb_gc_mark is "pinned" and is not allowed to move. C extensions must mark
their references in order to keep them alive. Since C extensions use
rb_gc_mar... -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67324 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- I forgot to explain it in the previous commit
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67323 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67322 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
03:24 AM Revision 7aacb650 (git): Remove duplicated and change order
- `reg*` affects `doc/regexp.rdoc`, but it is not a file of the Oniguruma/Onigmo regular expression engine.
`reg*.[ch]` matches `reg*` except `doc/regexp.rdoc`.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67321 b2dd03c8-39d4-4d8f-98... -
- Eregon (Benoit Daloze) wrote:
> The same as "1 byte hash value".
> ...
I think so. I'm unsure how may people encounter this incompatibility.
```
class Foo
def hash
$hash
end
end
obj = Foo.new
h = {}
$hash = 0
h[o... -
- What version of DateTime do you use?
With the trunk I got:
```ruby
require 'date'
dt1 = DateTime.new(2001, 2, 3)
dt2 = DateTime.new(2001, 2, 3, 12)
p dt1 === dt2 #=> true
p dt1 == dt2 #=> false
``` -
-
- microweb10 (Julian Herrero) wrote:
> I would like to work on this one.
Please do, patches are always welcome. -
- I have verified that with the beta files for Unicode Version 12.1.0 at https://www.unicode.org/Public/12.1.0/ucd/, Ruby compiles and runs all tests (make check) successfully.
Please note that different from other betas, this beta uses... -
-
- ファイルの存在は確認できた、ということで閉じます。何かアクションがある場合は Status 戻して進めてください。
03/20/2019
-
-
- Applied in changeset trunk|r67320.
----------
Add Enumerator::Lazy docs.
* explanation of the class concept, with examples;
* docs for all class methods (most of them just say "Like Enumerable#<methodname>, but chains operation to ... -
- * explanation of the class concept, with examples;
* docs for all class methods (most of them just say "Like Enumerable#<methodname>, but chains operation to be lazy-evaluated.", but I believe they are useful this way because now have ... -
- I couldn't reproduce this with Mojave.
```
~ > ls /usr/include/netinet6/in6.h
/usr/include/netinet6/in6.h
```
It seems your development environment issue. -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67319 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67318 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- ```shell
ruby -r yaml -e "p YAML.dump( ''.force_encoding('UTF-32LE') )"
Traceback (most recent call last):
4: from -e:1:in `<main>'
3: from /Users/work/.rvm/rubies/ruby-2.6.1/lib/ruby/2.6.0/psych.rb:513:in `dump'
2: from /Users... - 07:57 PM Revision 02df0f38 (git): * 2019-03-21
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67317 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
- 07:57 PM Revision 5c439ebf (git): * expand tabs.
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67316 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- There is a special optimization for "only lead parameters"
method dispatch using specialized dispatcher functions
`vm_call_iseq_setup_normal_0start...`.
Other cases (opt, rest, post, ...) we don't use specialized
dispatcher and call with... -
- There is a commit that claims to backport #15270, `ruby_2_5@66225` / `aba207b7620d963e212e4187213db7e1eee7a790 `.
However, the patch in #15270 wasn't actually backported. For reference, here is a script that outputs
```
"2.6.2"
3... -
05:31 PM Feature #13677: Add more details to error "Name or service not known (SocketError)"
- shyouhei (Shyouhei Urabe) wrote:
> The proposed functionality sounds fine but no one currently have spare time to implement this; patch welcomed.
I would like to work on this one. -
01:30 PM Feature #15663: Documenting autoload semantics
- Eregon (Benoit Daloze) wrote:
> I was thinking maybe the require lock per path should be used for everything, but then since #autoload calls `require` dynamically, how to keep track which thread is loading the constant and so should o... -
- akr (Akira Tanaka) wrote:
> Eregon (Benoit Daloze) wrote:
> ...
It seems tricky implementation-wise, constant resolution (e.g. #const_get) has the constant data structure, and #require has the expanded file path + related lock but none... -
- akr (Akira Tanaka) wrote:
> > Could we start a document specifying the semantics?
> ...
Of course, there is no problem to describe the single thread semantics. -
- Eregon (Benoit Daloze) wrote:
> I would have thought `require autoload_path` would basically do the same as triggering the autoload of the constant (such as `Foo`). But the results above show they differ.
Agreed.
I think no one ... -
-
- @headius Could you attach a diff for the weakref-based approach?
It seems the GitHub link doesn't work well (it shows the list of commits for me). -
- @seki
Can you handle this?
-
- Well, as @shyouhei described, daily builds are testing wider range of environments which we do not want for every commit. As the original title "Duplicate builds on travis-ci?" and the description "This seems unnecessary" were wrong, I r...
-
- I removed CRON jobs from Travis CI.
-
- Eregon (Benoit Daloze) wrote:
> Should this "global autoload lock" also be locked for normal non-autoload `require`?
I think requiring a library which is configured for autoload should lock "global autoload lock".
Currently I think ... -
- Should this "global autoload lock" also be locked for normal non-autoload `require`?
Otherwise I think it could deadlock:
```
T1: require "foo"; AutoloadC;
T2: AutoloadC; require "foo";
``` -
- Made some changes for "auto compaction"
I am a newbie in C programming
This is just for discussion, not tested nor compiled yet
https://github.com/ruby/ruby/compare/trunk...PikachuEXE:feature/gc-compact/pika
-
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67314 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- Applied in changeset trunk|r67313.
----------
Improve TracePoint docs.
* Mention new :script_compiled event;
* Deduplicate __enable/enable methods;
* Document target: and target_line: arguments.
[Bug #15484][ruby-core:90801]
... -
- * Mention new :script_compiled event;
* Deduplicate __enable/enable methods;
* Document target: and target_line: arguments.
[Bug #15484][ruby-core:90801]
Co-authored-by: zverok <zverok.offline@gmail.com>
git-svn-id: svn+ssh://... -
- I created a patch.
> I would like to get this patch tested side-by-side at Discourse, GitHub and Shopify.
Could you test the patch attached? -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67312 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- I created a patch for the bug.
-
- * string.c: remove
-
-
- 僕が決められるのかわかりませんが、5年以上経っているので消していいと思います。
-
- I was also unable to reproduce.
```
~ > docker run --rm -ti alpine
/ # apk update
/ # apk add ruby-irb
/ # ruby -v
ruby 2.5.3p105 (2018-10-18 revision 65156) [x86_64-linux-musl]
```
-
-
- * string.c (rb_str_crypt): fix indent not to make the whole list
verbatim entirely.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67310 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
-
- The next meeting issue is here: https://bugs.ruby-lang.org/issues/15459
- 12:31 AM Revision eee58ca6 (git): * 2019-03-20
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67309 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67308 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
03/19/2019
-
- Sorry, your inconvenience experience. We have an issue of bugs.ruby-lang.org. I fixed it on this morning(JST).
I removed duplicated issues and copy from them.
@nobu said:
Intended.
It equals
```ruby
a.map{|x,| x} # => [1, 2, ... -
- > Honestly, I'm not a fan of the behavior, though.
I think it comes down a lot to personal preferences. For example I actually
like being able to use @NUMBER_HERE :) - although in "production" code,
I may use the oldschool variant s... -
- Yes, it is actually intended. `@1` is equivalent to `|at1, at2, at3, ...|`'s `at1`.
```
a = [1, 2, 3]
a.map{|x,| x} # => [1, 2, 3]
a.map{@1} # => [1, 2, 3]
a = [[1], [2], [3]]
a.map{|x,| x} # => [1, 2, 3]
a.map{@1} # => [1, 2... -
- In the following, `@1` refers to the entire item iterated:
```ruby
a = [1, 2, 3]
a.map{|x| x} # => [1, 2, 3]
a.map{@1} # => [1, 2, 3]
```
whereas in the following, `@1` refers to the first item achieved by decomposing the item ... -
- @localhostdotdev
I fixed an issue of our tracker. I deleted 15713-15716. -
- DateTime#=== is inherited from Date#=== without overwriting the #=== method, this leads to DateTime#=== comparing only dates and ignore the time part.
```
DateTime.new(2001, 2, 3) === DateTime.new(2001, 2, 3, 12)
=> false
```
I ... -
05:42 PM Feature #15667: Introduce malloc_trim(0) in full gc cycles
- As a maintainer of the quoted glibc code I'd be really interested in the results of this work. Please share when ready.
-
05:12 PM Bug #15711: Remove use of _id2ref from DRb
- Ok, unfortunately I'm not sure that WeakMap will work for this purpose. It works based on identity (which would not work in implementations where Fixnum-ranged Integers are not guaranteed to be the same object every time), attempts to at...
-
- I added a mutex and pushed the base implementation as a PR here: https://github.com/ruby/ruby/pull/2102
I can try to work up patches for the other two implementations, but they'll need some additional work within MRI to support. -
- We almost had agreement on adding a reference queue here: https://bugs.ruby-lang.org/issues/6309
-
- This issue relates to https://bugs.ruby-lang.org/issues/15408
DRb uses `_idref` internally to implement a weak map, and this issue seeks to replace that code with an implementation that does not use `_id2ref`.
We will be deprecatin... -
- Sorry for the delay folks, I was intermittently blocked from accessing bugs.ruby-lang.org, but things are working now!
I'll move forward with fixing DRb using the logic JRuby ships in https://bugs.ruby-lang.org/issues/15711.
Remain... -
- We have already discussed in https://bugs.ruby-lang.org/issues/15408 the deprecation and eventual removal of _id2ref, so perhaps we can move these things together.
The additional hashing logic to maintain the Object-to-ID maps will ad... -
- nateberkopec (Nate Berkopec) wrote:
> > Can we introduce it just after every major (full) gc?
> ...
As an experimental feature shouldn't it be disabled by default and only enabled via something like env variable?
But I do agree that... -
- Hanmac (Hans Mackowiak) wrote:
> Duplicate of #15620
It is irrelevant. -
- Another crash after updating to 2.6.2
ruby 2.6.2p47 (2019-03-13 revision 67232) [x86_64-darwin18]
Not sure they are related to the same issue
```
Process: ruby [42621]
Path: /Users/USER/*/ruby
Ident... -
07:03 AM Bug #15620: Block argument usage affects lambda semantic
- @nobu should this one be closed too?
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67307 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- Applied in changeset trunk|r67306.
----------
parse.y: fix var_ref of numbered param in ripper
* parse.y (string_dvar, user_variable): register numbered
parameter in ripper for var_ref.
[ruby-core:91867] [Bug #15673] -
- * parse.y (string_dvar, user_variable): register numbered
parameter in ripper for var_ref.
[ruby-core:91867] [Bug #15673]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67306 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- * parse.y (parser_token_value_print): in ripper, ID values are
wrapped in NODE_RIPPER at set_yylval_name(), so print the Symbol
wrapped together.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67305 b2dd03c8-39d4-4d8f-98ff-823fe6... -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67304 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
01:39 AM Bug #15675 (Closed): "fatal - exception reentered" error after installing Ruby 2.5.5
- At first I have 2.5.3 and 2.6.0 which are working fine. Then I started to encounter errors in Heroku after deployment, I tried installing Ruby 2.5.5 since that is the supported version in Heroku in order to replicate the problem. After t...
03/18/2019
-
10:48 PM Feature #4475: default variable name for parameter
- Is there a reason to do this other than to save some typing? I'm not sure we've proposed any terribly real-world cases here where this made code better.
I feel like we already have some single-character patterns around blocks with one... -
05:12 PM Feature #4475: default variable name for parameter
- I also dislike the use of `@` for this. It looks very weird and evokes strong references to instance variables in my mind. I'm not sure which characters exactly are an option, but I think we should avoid the use of `@`. Will something li...
-
03:43 PM Feature #4475: default variable name for parameter
- Would it be possible to make this more inline with other "magic" variables? Such as $1 and $2 for regex. Maybe $blockarg1 and $blockarg2?
-
- I think @1 @2 is ok, syntax-wise; it reminds me of $1 $2 for regex matching.
The main two advantages I see is that it is short to type; and also easy
to remember.
There is only one thing that I would like to add and this came from... -
10:12 PM Feature #9758: Allow setting SSLContext#extra_chain_cert in Net::HTTP
- I would also love to know about this. I'm running into an issue right now where I'm trying to use ruby (specifically with rest-client, but it's just a wrapper around Net::HTTP) to call out to an API with a client certificate and need a c...
-
08:51 PM Feature #15626: Manual Compaction for MRI's GC (`GC.compact`)
- > Can we introduce it just after every major (full) gc?
I agree. If the necessary steps are Full GC -> Update -> Move -> Full GC, then it would be faster to just compact automatically after a full GC which is already occurring. I unde... -
08:24 PM Feature #15632: Dynamic method references
- Okay, in that case this can be closed.
-
- I think I found it. I've attached a patch file. Please forgive me if I'm doing this wrong, this is my first contribution.
-
- Some more investigation yields that `compile_error` is called with:
identifier false is not valid to get -
- To be clear, I mean that:
``` ruby
require 'ripper'; Ripper.new('[1, 2, 3].map { @1 * 2 }').tap(&:parse).error?
```
returns true
-
- Hi there -
Love the new number args for blocks. When I run
``` ruby
[1, 2, 3].map { @1 * 2 }
```
everything works. However, when I run:
```ruby
require 'ripper'; Ripper.new('[1, 2, 3].map { @1 * 2 }').parse
```
it retu... -
07:22 PM Feature #14183: "Real" keyword argument
- mame,
Thanks for your continued work on this.
I still agree that for methods that accept keyword arguments, we should make changes to avoid the problems that currently exist for keyword arguments.
I still believe that breaking a... -
- Sorry for leaving this ticket. Matz, akr and I talked about this issue several times since the last year, and we have never reached a perfect solution. But I try to re-summarize the problem, current proposal, and migration path.
... - 06:30 PM Revision f86e5dae (git): Applied security patches for RubyGems
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/branches/ruby_2_4@67303 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- to make it easier to understand what values are grouped.
Just cosmetic changes.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67302 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- to eliminate necessity of error check and `free`
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67301 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- by changing interface of `mjit_copy_cache_from_main_thread`.
This is also fixing deadlock introduced by r67299.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67300 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- I noticed that r67287 was illegal because memory allocated by `alloca`
was used after the stack is expired.
So I just replaced that with `malloc` and `free` for now.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67299 b2dd03c8-39d4... - 04:14 PM Revision 08e9c58d (git): * 2019-03-19
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67298 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- This reverts commit ba51ae0109ee1d1fa7ca90b43da115ea68d7214a.
CI is failing again...
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67297 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- Originally I opened this up as an issue in memory profiler https://github.com/SamSaffron/memory_profiler/issues/67, however I was able to isolate the issue to just Ruby 2.6.
ObjectSpace.allocation_sourceline is reporting the line wher... -
- Take 2 of r67287.
For some reasons, passing pointer of pointer on stack to a function
and assigning an addresse to a pointer dereferenced from the pointer
seems not working on mswin.
So I achieved to return multiple values by returning... -
- Applied in changeset trunk|r67295.
----------
parse.y: numbered parameter in lambda
* parse.y (lambda): support numbered parameters, only when no
argument list including empty parentheses, like empty vertical
bars. [ruby-core:9185... -
- Koichi said it will be fixed. :)
(I guess this was never intentional, thus a bug.) -
- Duplicate of #15620
-
03:34 AM Bug #15672 (Closed): Lambda implicit arguments, differences between lambda {} and -> {} specifications
- Hi
Are the following differences intentional?
```
$ ruby -v
ruby 2.7.0dev (2019-03-18 trunk 67291) [x86_64-darwin18]
```
```
$ cat ptn1.rb
a = -> { p @1 }
a.call(1)
$ ruby ptn1.rb
Traceback (most recent call last):
... -
- * parse.y (lambda): support numbered parameters, only when no
argument list including empty parentheses, like empty vertical
bars. [ruby-core:91859] [Bug #15672]
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67295 b2dd03c8-39d4... -
- This reverts commit 6b136a044205f6e6b66df68cd2da2a9c3e952a7d.
This does not seem to work:
https://travis-ci.org/ruby/ruby/jobs/507646193#L2478
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67294 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- to make CI stable. See the PR for details.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67293 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- * parse.y (set_yylval_noname): continue after an invalid global,
instance, class variable name, without "unexpected end-of-file"
error.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67292 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- Schedule on 4/17 (Wed)
* 12:00- door open
* 13:00-18:30 meeting w/Matz.
* topics is welcome. please comment on this issue.
* 18:30 close
There are several pre-RubyKaigi parties. pls check them.
-
- Further note:
"RubyKaigi 2019 After Hack by Fukuoka.rb!!" https://fukuokarb.connpass.com/event/124406/ is open event.
Anyone can attend! Enjoy.
Thanks,
Koichi -
- "After RubyKaigi hack meeting" is merged with "RubyKaigi 2019 After Hack by Fukuoka.rb!!"
https://fukuokarb.connpass.com/event/124406/
Please sign-up this party if you want to attend it even if you already sign-up on doorkeeper.
Det... -
- This reverts commit 4161674b2fbea6bdd01783ac5d3b39d88db22972.
Revert "Eliminate mjit_copy_job_t reference from mjit_worker"
This reverts commit d86a1aa045959dfbf5cd472eae0d043180259727.
Reverting them because of CI failures
git-svn-i... -
- [Fix GH-2099]
From: Lourens Naudé <lourens@bearmetal.eu>
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67290 b2dd03c8-39d4-4d8f-98ff-823fe69b080e -
- * parse.y (parser_numbered_param): hoisted out the contextual
check for numbered parameters.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67289 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
03/17/2019
-
08:56 PM Bug #15662 (Closed): Fix CSV delegation to missing StringIO
- Thanks!
-
09:13 AM Bug #15662: Fix CSV delegation to missing StringIO
- We resolved it in https://github.com/ruby/csv/pull/80. Thank you @kou 🙇♂️!
-
- rather than preparing beforehand.
By having this change, implementing inlining by calling
`mjit_copy_cache_from_main_thread` for inlined methods was made
possible.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67288 b2dd03c8-39d4-4... -
- and make `copy_cache_from_main_thread` easier to use.
For implementing inlining later, I'll use `copy_cache_from_main_thread`
inside `mjit_compile`.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67287 b2dd03c8-39d4-4d8f-98ff-823fe6... -
- and guard iseq from GC by marking iseq in mjit_copy_job.
This is a refactoring for implementing inlining later and
should not be fixing or introducing any bugs.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67286 b2dd03c8-39d4-4d8f... -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67285 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
- 04:32 PM Revision 5bd10603 (git): * 2019-03-18
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67284 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67283 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67282 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- to check if it resolves "Permission denied" problem.
https://travis-ci.org/ruby/ruby/jobs/507381339
https://travis-ci.org/ruby/ruby/jobs/507392198
TBH I'm not exactly sure why it happens, but I don't have infinite time
to understand thi... -
- because --depth=1 may randomly break checkout:
https://dev.azure.com/rubylang/ruby/_build/results?buildId=208&view=logs&jobId=7ded14dc-7a77-59da-f40a-71e137ad96c0&taskId=2045950f-1dcd-54a4-4c23-fae2521239c1&lineStart=1554&lineEnd=1555&co... -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67279 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- Applied in changeset trunk|r67278.
----------
Numbered parameters [Feature #4475] -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67278 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- * --jit-min-calls: 5 -> 10000
--jit-min-calls=5 obviously can compile non hotspot. This was not a
problem for MJIT-benchmarks and Optcarrot because the former has very
few hot optimiziable methods and the latter is likely to trigger
com... -
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67276 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
03/16/2019
-
10:11 PM Bug #15671 (Third Party's Issue): Segfault
- We hit a segfault in wpscan (https://github.com/wpscanteam/wpscan) using docker (https://hub.docker.com/r/wpscanteam/wpscan) with alpine linux with ruby 2.6.2.
The command line used:
`docker run -it --rm wpscanteam/wpscan --url https... -
04:56 PM Bug #15490: socket.rb - recurring segmentation faults
- We're seeing this issue as well, on Ruby 2.6.1. For us, it occurs towards the end of a fairly large test suite when running one of our legacy Cucumber tests. When we only run the Cucumber section of our test suite (not the whole thing) t...
-
- ktsj-san recognizes this issue and it's intentionally left failing now.
As failure notification of this task is NOT indicating ruby is broken,
let's stop notifying the failure fo rnow.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@6... - 04:26 PM Revision 5b0bcb0b (git): * 2019-03-17
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67274 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- For 2 reasons:
* bundled_gems tend to be left broken (like now)
* We don't want Slack notification for pull request and it can't be
disabled on Azure Pipelines
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67273 b2dd03c8-39d4-4d8... -
09:52 AM Feature #11741: Migrate Ruby to Git from Subversion
- http://15news.ir
http://9news.ir
http://afexo.ir
http://aloofile.ir
http://aminpayam.ir
http://andishmes.ir
http://arikehvip.ir
http://azargo.ir
http://bassirat.ir
http://belton.ir
http://birligh.ir
http://brmm.ir
http://chag... -
- and simplified config by using dedicated webhook URL.
Sadly AppVeyor YAML does not support alias and so we need to copy-paste
the request body.
memo:
https://slack-files2.s3-us-west-2.amazonaws.com/bot_icons/2018-02-10/314363543719_48.p... -
04:00 AM Bug #15670 (Closed): Ripper treats :"sym" as xstring
- Applied in changeset trunk|r67270.
----------
dsym should be treated as string [ruby-core:91852] [Bug #15670] -
- Ripperで `:"sym"` をパースするとxstringとして扱われるようになっていますが、
`{"sym": ...}` と同様にstringとして扱われるべきだと思います。
~~~
$ ruby -rripper -e '_, (_, _, s) = Ripper.sexp_raw(%q{:"sym"}); p s'
[:dyna_symbol, [:xstring_add, [:xstring_new], [:@tstring_content, ... - 04:00 AM Revision f044cc10 (git): * 2019-03-16
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67271 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
-
- git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67270 b2dd03c8-39d4-4d8f-98ff-823fe69b080e