https://bugs.ruby-lang.org/https://bugs.ruby-lang.org/favicon.ico?17113305112021-04-17T08:18:29ZRuby Issue Tracking SystemRuby master - Misc #17811: DevelopersMeeting20210521Japanhttps://bugs.ruby-lang.org/issues/17811?journal_id=915962021-04-17T08:18:29Zmame (Yusuke Endoh)mame@ruby-lang.org
<ul><li><strong>Related to</strong> <i><a class="issue tracker-5 status-1 priority-4 priority-default" href="/issues/14770">Misc #14770</a>: [META] DevelopersMeeting</i> added</li></ul> Ruby master - Misc #17811: DevelopersMeeting20210521Japanhttps://bugs.ruby-lang.org/issues/17811?journal_id=918902021-05-10T20:21:10Zjeremyevans0 (Jeremy Evans)merch-redmine@jeremyevans.net
<ul></ul><ul>
<li>[Bug <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Constant declaration does not conform to JIS 3017:2013 (Closed)" href="https://bugs.ruby-lang.org/issues/15928">#15928</a>] Constant declaration does not conform to JIS 3017:2013 (jeremyevans0)
<ul>
<li>Do we want to make constant assignment evaluation similar to attribute assignment (e.g. use left-to-right evaluation)?</li>
<li>We recently made a similar change to make multiple assignment use left-to-right evaluation (<a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: odd evaluation order in a multiple assignment (Closed)" href="https://bugs.ruby-lang.org/issues/4443">#4443</a>), and I think constant assignment should operate the same way.</li>
</ul>
</li>
<li>[Bug <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: `Cloned ENV` inconsistently returns `ENV` or `self` (Closed)" href="https://bugs.ruby-lang.org/issues/17767">#17767</a>] <code>Cloned ENV</code> inconsistently returns <code>ENV</code> or <code>self</code> (jeremyevans0)
<ul>
<li>How should <code>ENV.dup</code> and <code>ENV.clone</code> work?</li>
<li>I propose to have them return <code>ENV</code>, since they share the same storage.</li>
<li>If we do want <code>ENV.dup</code> and <code>ENV.clone</code> to return <code>ENV</code>, is the patch acceptable?</li>
</ul>
</li>
<li>[Bug <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Tempfile's finalizer can be interrupted by a Timeout exception which can cause the process to hang (Closed)" href="https://bugs.ruby-lang.org/issues/13876">#13876</a>] Tempfile's finalizer can be interrupted by a Timeout exception which can cause the process to hang (jeremyevans0)
<ul>
<li>Currently, exceptions can be raised during finalizer processing (in GC context), causing process hangs.</li>
<li>Can we mark when a thread is running finalizers and not check for pending interrupts in that case, as the patch does?</li>
</ul>
</li>
<li>[Bug <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Array#sort! changes the order even if the receiver raises FrozenError in given block (Closed)" href="https://bugs.ruby-lang.org/issues/17739">#17739</a>] Array#sort! changes the order even if the receiver raises FrozenError in given block (jeremyevans0)
<ul>
<li>Currently, freezing an array inside Array#sort! allows further changes to the array.</li>
<li>Should we prevent further changes to the array by checking whether the array is frozen each time the block returns?</li>
</ul>
</li>
<li>[Bug <a class="issue tracker-1 status-6 priority-4 priority-default closed" title="Bug: `Numeric#real?` incorrectly returns true for `NaN` and `INFINITY` (Rejected)" href="https://bugs.ruby-lang.org/issues/17631">#17631</a>] <code>Numeric#real?</code> incorrectly returns true for <code>NaN</code> and <code>INFINITY</code> (jeremyevans0)
<ul>
<li>Is the current behavior of <code>real?</code> and <code>complex?</code> expected, where <code>Complex#real?</code> is always <code>false</code> and <code>Numeric#real?</code> is always <code>true</code>?</li>
<li>I believe so and think this bug should be closed, but I would like to get confirmation.</li>
</ul>
</li>
</ul> Ruby master - Misc #17811: DevelopersMeeting20210521Japanhttps://bugs.ruby-lang.org/issues/17811?journal_id=918952021-05-11T09:12:24Zbyroot (Jean Boussier)byroot@ruby-lang.org
<ul></ul><ul>
<li>[Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Around `Process.fork` callbacks API (Closed)" href="https://bugs.ruby-lang.org/issues/17795">#17795</a>] Around <code>Process.fork</code> callbacks API
<ul>
<li>Was considered in the last meeting, but didn't reach any conclusion</li>
<li>Since then more use cases and argument were brought.</li>
</ul>
</li>
<li>[Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Provide a public WeakMap that compares by equality rather than by identity (Closed)" href="https://bugs.ruby-lang.org/issues/16038">#16038</a>] Provide a public WeakMap that compares by equality rather than by identity
<ul>
<li>Would allow user code to implement interned value objects, similar to <code>String#-@</code> but for arbitrary types.</li>
<li>Was initially proposed about 2 years ago, but didn't reach a conclusion.</li>
</ul>
</li>
</ul> Ruby master - Misc #17811: DevelopersMeeting20210521Japanhttps://bugs.ruby-lang.org/issues/17811?journal_id=919502021-05-13T10:07:03Zduerst (Martin Dürst)duerst@it.aoyama.ac.jp
<ul></ul><ul>
<li>[Feature <a class="issue tracker-2 status-1 priority-4 priority-default" title="Feature: Fix Timeout.timeout so that it can be used in threaded Web servers (Open)" href="https://bugs.ruby-lang.org/issues/17849">#17849</a>] Fix Timeout.timeout so that it can be used in threaded Web servers
<ul>
<li>Ruby is used a lot in Web servers and other places with Threads and potential timeouts.</li>
<li>We should make sure we can provide the best possible timeout solution for these environments.</li>
</ul>
</li>
</ul> Ruby master - Misc #17811: DevelopersMeeting20210521Japanhttps://bugs.ruby-lang.org/issues/17811?journal_id=919552021-05-13T15:40:28Zalanwu (Alan Wu)
<ul></ul><ul>
<li>[Bug <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Inconsistent visibility behavior with refinements (Closed)" href="https://bugs.ruby-lang.org/issues/17822">#17822</a>] Inconsistent visibility behavior with refinements (alanwu)
<ul>
<li>I think the three cases in the repro script should behave the same. What do you think?</li>
<li>If they should behave the same, what should be that behavior?</li>
</ul>
</li>
</ul> Ruby master - Misc #17811: DevelopersMeeting20210521Japanhttps://bugs.ruby-lang.org/issues/17811?journal_id=919892021-05-17T02:38:06Zko1 (Koichi Sasada)
<ul></ul><ul>
<li>[Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: rewrite lib/debug.rb with latest API (Closed)" href="https://bugs.ruby-lang.org/issues/17863">#17863</a>] rewrite lib/debug.rb with latest API (ko1)
<ul>
<li>Please confirm APIs (file name, method name, etc)</li>
</ul>
</li>
</ul> Ruby master - Misc #17811: DevelopersMeeting20210521Japanhttps://bugs.ruby-lang.org/issues/17811?journal_id=919902021-05-17T04:15:07Zsam.saffron (Sam Saffron)sam.saffron@gmail.com
<ul></ul><ul>
<li>
<p>[Bug <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Resolv::DNS RequestID table allocations are never freed, causing DNS lookups to eventually hang (Closed)" href="https://bugs.ruby-lang.org/issues/17781">#17781</a>] Resolv::DNS RequestID table allocations are never freed, causing DNS lookups to eventually hang</p>
<ul>
<li>Security issue is quite severe (can cause denial of service), any chance we can do a 2.7.4 release shortly?</li>
</ul>
</li>
</ul> Ruby master - Misc #17811: DevelopersMeeting20210521Japanhttps://bugs.ruby-lang.org/issues/17811?journal_id=920432021-05-20T10:47:10Zhsbt (Hiroshi SHIBATA)hsbt@ruby-lang.org
<ul></ul><ul>
<li>[Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Update of default gems in Ruby 3.1 (Closed)" href="https://bugs.ruby-lang.org/issues/17873">#17873</a>] Update of default gems in Ruby 3.1
<ul>
<li>Does anyone have any objections?</li>
</ul>
</li>
</ul> Ruby master - Misc #17811: DevelopersMeeting20210521Japanhttps://bugs.ruby-lang.org/issues/17811?journal_id=921472021-05-24T16:46:06Zmame (Yusuke Endoh)mame@ruby-lang.org
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/92147/diff?detail_id=60014">diff</a>)</li></ul> Ruby master - Misc #17811: DevelopersMeeting20210521Japanhttps://bugs.ruby-lang.org/issues/17811?journal_id=921502021-05-24T16:50:39Zmame (Yusuke Endoh)mame@ruby-lang.org
<ul><li><strong>Status</strong> changed from <i>Open</i> to <i>Closed</i></li></ul>