https://bugs.ruby-lang.org/https://bugs.ruby-lang.org/favicon.ico?17113305112022-08-25T12:39:55ZRuby Issue Tracking SystemRuby master - Misc #18977: DevMeeting-2022-09-22https://bugs.ruby-lang.org/issues/18977?journal_id=989162022-08-25T12:39:55Zmame (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 #18977: DevMeeting-2022-09-22https://bugs.ruby-lang.org/issues/18977?journal_id=989282022-08-26T04:12:40Zmame (Yusuke Endoh)mame@ruby-lang.org
<ul></ul><ul>
<li>[Feature <a class="issue tracker-2 status-1 priority-4 priority-default" title="Feature: `FileUtils.rm_f` and `FileUtils.rm_rf` should not mask exceptions (Open)" href="https://bugs.ruby-lang.org/issues/18784">#18784</a>] <code>FileUtils.rm_f</code> and <code>FileUtils.rm_rf</code> should not mask exceptions (mame)
<ul>
<li>I changed FileUtils.rm_f/rm_rf so that it raises a SystemCallError but Errno::ENOENT.</li>
<li>But it seemed to affect mkmf on Windows. mkmf uses rm_f to delete conftest.exe, but sometime it fails. I don't know why it happens.</li>
<li>I concern that this change will make users just ignore exceptions of FileUtils.rm_rf by wrapping <code>begin .. rescue SystemCallError; end</code>.</li>
<li>This is not what I wanted. Should we revert the change of FileUtils?</li>
</ul>
</li>
</ul> Ruby master - Misc #18977: DevMeeting-2022-09-22https://bugs.ruby-lang.org/issues/18977?journal_id=990072022-08-29T13:16:01Zbyroot (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: Add an `exception: false` argument for Queue#push, Queue#pop, SizedQueue#push and SizedQueue#pop (Closed)" href="https://bugs.ruby-lang.org/issues/18982">#18982</a>] Add an <code>exception: false</code> argument for Queue#push, Queue#pop, SizedQueue#push and SizedQueue#pop (byroot)
<ul>
<li>The existing exceptions (ThreadError) are a bit awkward to deal with.</li>
<li>Queue is often used deep into the stack where exceptions in common cases are fairly costly.</li>
</ul>
</li>
<li>[Feature <a class="issue tracker-2 status-6 priority-4 priority-default closed" title="Feature: Object#with to set and restore attributes around a block (Rejected)" href="https://bugs.ruby-lang.org/issues/18951">#18951</a>] <code>Object#with</code> to set and restore attributes around a block (byroot)
<ul>
<li>Works with any public accessor, e.g. <code>GC.with(stress: true) { do_something }</code>
</li>
<li>This is an extremely common pattern, especially in test suites, but is often implemented with subtle bugs.</li>
</ul>
</li>
</ul> Ruby master - Misc #18977: DevMeeting-2022-09-22https://bugs.ruby-lang.org/issues/18977?journal_id=990722022-09-03T17:17:41ZEregon (Benoit Daloze)
<ul></ul><ul>
<li>[Feature <a class="issue tracker-2 status-1 priority-4 priority-default" title="Feature: Add methods allow us to get visibility from Method and UnboundMethod object. (Open)" href="https://bugs.ruby-lang.org/issues/11689">#11689</a>] Add methods allow us to get visibility from Method and UnboundMethod object. (eregon)
<ul>
<li>I think we should re-add (undo revert) {Method,UnboundMethod}#{public?,private?,protected?} on master, see <a href="https://bugs.ruby-lang.org/issues/11689#note-27" class="external">https://bugs.ruby-lang.org/issues/11689#note-27</a>
</li>
<li>Both <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Method#owner and UnboundMethod#owner are incorrect after using Module#public/protected/private (Closed)" href="https://bugs.ruby-lang.org/issues/18729">#18729</a> and <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Regression on master for Method#== when comparing public with private method (Closed)" href="https://bugs.ruby-lang.org/issues/18751">#18751</a> are fixed, and now Method == method entry, and visibility is an attribute of method entry.</li>
<li>Ruby 3.1 already has those method and the fix for <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Method#owner and UnboundMethod#owner are incorrect after using Module#public/protected/private (Closed)" href="https://bugs.ruby-lang.org/issues/18729">#18729</a> and <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Regression on master for Method#== when comparing public with private method (Closed)" href="https://bugs.ruby-lang.org/issues/18751">#18751</a> was <a href="https://bugs.ruby-lang.org/issues/18435#note-25" class="external">backported to 3.1</a>. So if we keep them removed for 3.2 we cause incompatibility and there is no practical issue with those methods anymore.</li>
</ul>
</li>
</ul> Ruby master - Misc #18977: DevMeeting-2022-09-22https://bugs.ruby-lang.org/issues/18977?journal_id=990842022-09-08T11:12:18Zst0012 (Stan Lo)stan001212@gmail.com
<ul></ul><ul>
<li>[Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Proposal: Introduce new APIs to reline for changing dialog UI colours (Closed)" href="https://bugs.ruby-lang.org/issues/18996">#18996</a>] Proposal: Introduce new APIs to reline for changing dialog UI colours (st0012)
<ul>
<li>
<code>irb</code>'s autocompletion background can make texts hard to read for some users.</li>
<li>Because the colours are hardcoded in <code>reline</code>, users aren't able to change them. So many users need to disable the feature altogether.</li>
<li>The APIs proposed in the ticket actually have been implemented by <a href="https://github.com/pocari" class="external">@pocari</a> and me.</li>
<li>Since the maintainer <a class="user active user-mention" href="https://bugs.ruby-lang.org/users/11389">@aycabta (aycabta .)</a> is not available now, I hope we can decide if the APIs still need any improvement or they are ready for release.</li>
</ul>
</li>
<li>[Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Follow up of #18996: Support changing irb's autocompletion background (Closed)" href="https://bugs.ruby-lang.org/issues/19010">#19010</a>] Follow up of <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Proposal: Introduce new APIs to reline for changing dialog UI colours (Closed)" href="https://bugs.ruby-lang.org/issues/18996">#18996</a>: Support changing irb's autocompletion background (st0012)
<ul>
<li>If the above or similar <code>reline</code> APIs are introduced, I want to support <code>dark</code>/<code>bright</code> themes in <code>irb</code> (screenshots are included in the ticket)</li>
<li>The default will be <code>dark</code> theme. I don't want to add more themes for now. So it can be toggled to <code>bright</code> theme with a boolean config.</li>
<li>To customize more, <code>irb</code> can take and pass per-color configurations to <code>reline</code> too.</li>
</ul>
</li>
</ul> Ruby master - Misc #18977: DevMeeting-2022-09-22https://bugs.ruby-lang.org/issues/18977?journal_id=991272022-09-11T10:30:38ZEregon (Benoit Daloze)
<ul></ul><ul>
<li>[Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: `UnboundMethod#==` with inherited classes (Closed)" href="https://bugs.ruby-lang.org/issues/18798">#18798</a>] <code>UnboundMethod#==</code> with inherited classes (eregon)
<ul>
<li>OK to change <code>UnboundMethod#==</code> to check if same method definition (and ignore from which class <code>instance_method</code> was used on)? If yes, what about <code>UnboundMethod#eql?</code>?</li>
<li>If not, OK to add <code>{Method,UnboundMethod}#same_definition?(other)</code>?</li>
</ul>
</li>
</ul> Ruby master - Misc #18977: DevMeeting-2022-09-22https://bugs.ruby-lang.org/issues/18977?journal_id=991372022-09-14T20:22:38Zjeremyevans0 (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: Module#using raises RuntimeError when called at toplevel from wrapped script (Closed)" href="https://bugs.ruby-lang.org/issues/18960">#18960</a>] Module#using raises RuntimeError when called at toplevel from wrapped script (jeremyevans0)
<ul>
<li>Do we want to support this? I think since #using is permitted at top level and inside a module, we should.</li>
</ul>
</li>
<li>[Bug <a class="issue tracker-2 status-2 priority-4 priority-default" title="Feature: Ractor: can't share #Method objects (Assigned)" href="https://bugs.ruby-lang.org/issues/18919">#18919</a>] Ractor: can't share #Method objects (jeremyevans0)
<ul>
<li>Is this a bug? Ractor cannot share most objects, but some procs are sharable.</li>
<li>If not a bug, should it be switched to feature request?</li>
</ul>
</li>
<li>[Bug <a class="issue tracker-1 status-1 priority-4 priority-default" title="Bug: parse.y: Foo::Bar {} is inconsistently rejected (Open)" href="https://bugs.ruby-lang.org/issues/18878">#18878</a>] parse.y: Foo::Bar {} is inconsistently rejected (jeremyevans0)
<ul>
<li>This is currently invalid syntax, should we try to support it?</li>
<li>If so, do we consider this a bug or a feature request?</li>
<li>I tried to support it a couple weeks ago, but all my attempts ended in reduce/reduce conflicts.</li>
</ul>
</li>
</ul> Ruby master - Misc #18977: DevMeeting-2022-09-22https://bugs.ruby-lang.org/issues/18977?journal_id=991422022-09-15T03:26:54Zshioyama (Chris Salzberg)
<ul></ul><ul>
<li>[Bug <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Module#using raises RuntimeError when called at toplevel from wrapped script (Closed)" href="https://bugs.ruby-lang.org/issues/18960">#18960</a>] Module#using raises RuntimeError when called at toplevel from wrapped script (shioyama)
<ul>
<li><a class="user active user-mention" href="https://bugs.ruby-lang.org/users/1604">@jeremyevans0 (Jeremy Evans)</a> mentioned this, but I think this is a bug based on common reading of the wrap argument to load.</li>
<li>See also context for this in my next bullet point.</li>
</ul>
</li>
<li>[Feature <a class="issue tracker-2 status-1 priority-4 priority-default" title="Feature: require into module (Open)" href="https://bugs.ruby-lang.org/issues/10320">#10320</a>] require into module (shioyama)
<ul>
<li>Proof of concept implementing imports like CommonJS etc using some patches to extend top_wrapper: <a href="https://bugs.ruby-lang.org/issues/10320#note-13" class="external">https://bugs.ruby-lang.org/issues/10320#note-13</a>
</li>
<li>Key point is that I want to support <em>existing</em> code, including gems, with no changes.</li>
<li>POC gem: <a href="https://github.com/shioyama/im" class="external">https://github.com/shioyama/im</a>, requires patched Ruby</li>
<li>This is just for discussion of feasibility/approach.</li>
</ul>
</li>
</ul> Ruby master - Misc #18977: DevMeeting-2022-09-22https://bugs.ruby-lang.org/issues/18977?journal_id=991462022-09-15T13:36:32Zpeterzhu2118 (Peter Zhu)peter@peterzhu.ca
<ul></ul><ul>
<li>[Bug <a class="issue tracker-1 status-7 priority-4 priority-default closed" title="Bug: Unexpected behaviour in Time.utc and Time.local when 8 arguments are passed in (Feedback)" href="https://bugs.ruby-lang.org/issues/18978">#18978</a>] Unexpected behaviour in Time.utc and Time.local when 8 arguments are passed in (peterzhu2118)
<ul>
<li>Passing 8 arguments causes both the 7th (microseconds) and 8th arguments to be ignored.</li>
<li>The behaviour is undocumented, so it is inconsistent between various Ruby implementations.</li>
<li>Proposed fix raises an ArgumentError when 8 arguments are passed in (this is the behaviour when 9 arguments are passed in).</li>
<li>Proposed PR: <a href="https://github.com/ruby/ruby/pull/6281" class="external">https://github.com/ruby/ruby/pull/6281</a>
</li>
</ul>
</li>
</ul> Ruby master - Misc #18977: DevMeeting-2022-09-22https://bugs.ruby-lang.org/issues/18977?journal_id=991642022-09-16T10:25:27Zbyroot (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: End of boot advisory API for RubyVM (Closed)" href="https://bugs.ruby-lang.org/issues/18885">#18885</a>] End of boot advisory API (byroot)
<ul>
<li>The general concept was accepted, but it need a proper name.</li>
<li>Suggestions:</li>
<li>
<code>Kernel.booted</code> / <code>Kernel.application_booted</code> / <code>Kernel.code_loaded</code> / <code>Kernel.startup_done</code>
</li>
<li>
<code>ObjectSpace.loaded</code> / <code>ObjectSpace.optimize</code>
</li>
<li>The suggestions try to describe an "event" or point in time, more than which optimizations are being performed.</li>
<li>This is because the actual optimizations might change over time or be different on other implementations.</li>
<li>I'd like to implement the constant cache pre-warming soon, so having an accepted name for it would be very helpful.</li>
</ul>
</li>
</ul> Ruby master - Misc #18977: DevMeeting-2022-09-22https://bugs.ruby-lang.org/issues/18977?journal_id=992082022-09-19T16:27:05Ztenderlovemaking (Aaron Patterson)tenderlove@ruby-lang.org
<ul></ul><ul>
<li>[Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Object Shapes (Closed)" href="https://bugs.ruby-lang.org/issues/18776">#18776</a>] Object shapes as new caching system
<ul>
<li>YARV interpreter benchmarks are similar speed or faster</li>
<li>Memory increase is low</li>
<li>Opens door for more optimizations</li>
</ul>
</li>
</ul> Ruby master - Misc #18977: DevMeeting-2022-09-22https://bugs.ruby-lang.org/issues/18977?journal_id=992162022-09-20T22:19:23Zioquatix (Samuel Williams)samuel@oriontransfer.net
<ul></ul><ul>
<li>[Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Introduce coverage support for `eval`. (Closed)" href="https://bugs.ruby-lang.org/issues/19008">#19008</a>] Introduce coverage support for <code>eval</code>.
<ul>
<li>Working implementation.</li>
<li>Can introduce some challenges for existing code - same challenges as debug gem - accurate line information for <code>eval</code> must be given.</li>
<li>Useful for computing template coverage.</li>
</ul>
</li>
<li>[Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Introduce `Fiber.blocking` for disabling scheduler. (Closed)" href="https://bugs.ruby-lang.org/issues/18411">#18411</a>] Introduce <code>Fiber.blocking</code> for disabling the scheduler (efficiently).
<ul>
<li>Useful for writing pure Ruby schedulers.</li>
</ul>
</li>
<li>[Feature <a class="issue tracker-1 status-1 priority-4 priority-default" title="Bug: `IO#close` has poor performance and difficult to understand semantics. (Open)" href="https://bugs.ruby-lang.org/issues/18455">#18455</a>] <code>IO#close</code> has poor performance and difficult to understand semantics.
<ul>
<li>We need to fix implementation of <code>IO#close</code> which is O(number of blocking operations).</li>
<li>We need to hide implementation of <code>struct rb_io_t</code> because the internal implementation details are leaking into public interface (e.g. <code>ccan_list</code>).</li>
</ul>
</li>
<li>[Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Introduce general `IO#timeout` and `IO#timeout=` for blocking operations. (Closed)" href="https://bugs.ruby-lang.org/issues/18630">#18630</a>] Introduce general <code>IO#timeout</code> and <code>IO#timeout=</code> for blocking operations.
<ul>
<li>We can now support generally blocking and internally non-blocking operations (i.e. fiber scheduler).</li>
<li>Safer network I/O.</li>
</ul>
</li>
<li>[Bug <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Struct aref and aset don't trigger any tracepoints. (Closed)" href="https://bugs.ruby-lang.org/issues/18886">#18886</a>] Struct aref and aset don't trigger any tracepoints.
<ul>
<li>Do we care enough to fix this issue or is the performance cost too high?</li>
</ul>
</li>
</ul> Ruby master - Misc #18977: DevMeeting-2022-09-22https://bugs.ruby-lang.org/issues/18977?journal_id=992272022-09-21T12:31:46Zyui-knk (Kaneko Yuichiro)
<ul></ul><ul>
<li>[Feature <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Error Tolerant Parser (Closed)" href="https://bugs.ruby-lang.org/issues/19013">#19013</a>] Error Tolerant Parser
<ul>
<li>I want to get feedback for the direction and other use cases.</li>
</ul>
</li>
</ul> Ruby master - Misc #18977: DevMeeting-2022-09-22https://bugs.ruby-lang.org/issues/18977?journal_id=992602022-09-22T22:36:55Zmame (Yusuke Endoh)mame@ruby-lang.org
<ul></ul><p>We could not discuss all agenda items in time. We will have an extra meeting at 6th Oct.</p> Ruby master - Misc #18977: DevMeeting-2022-09-22https://bugs.ruby-lang.org/issues/18977?journal_id=993482022-09-26T22:04:46Zpkubaj (Piotr Kubaj)
<ul></ul><ul>
<li>
<p>[Feature <a class="issue tracker-2 status-1 priority-4 priority-default" title="Feature: Use __builtin_ppc_get_timebase on POWER with clang (Open)" href="https://bugs.ruby-lang.org/issues/19022">#19022</a>] Use __builtin_ppc_get_timebase on POWER with clang (pkubaj)</p>
<ul>
<li>A simple change that allows run performance improvement</li>
</ul>
</li>
<li>
<p>[Feature <a class="issue tracker-2 status-1 priority-4 priority-default" title="Feature: Enable riscv64 coroutines on riscv64-freebsd, arm32 on arm*-freebsd and ppc on powerpc-freebsd (Open)" href="https://bugs.ruby-lang.org/issues/19023">#19023</a>] Enable riscv64 coroutines on riscv64-freebsd, arm32 on arm*-freebsd and ppc on powerpc-freebsd (pkubaj)</p>
<ul>
<li>Passes make test</li>
</ul>
</li>
</ul> Ruby master - Misc #18977: DevMeeting-2022-09-22https://bugs.ruby-lang.org/issues/18977?journal_id=994842022-10-06T07:07:50Zhsbt (Hiroshi SHIBATA)hsbt@ruby-lang.org
<ul></ul><ul>
<li>[Bug <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: syntax_suggest is not working with Ruby 3.2.0-preview2 (Closed)" href="https://bugs.ruby-lang.org/issues/19016">#19016</a>] syntax_suggest is not working with Ruby 3.2.0-preview2
<ul>
<li>What's blocker now?</li>
</ul>
</li>
</ul> Ruby master - Misc #18977: DevMeeting-2022-09-22https://bugs.ruby-lang.org/issues/18977?journal_id=994942022-10-06T14:38:54Zmame (Yusuke Endoh)mame@ruby-lang.org
<ul><li><strong>Status</strong> changed from <i>Open</i> to <i>Closed</i></li></ul> Ruby master - Misc #18977: DevMeeting-2022-09-22https://bugs.ruby-lang.org/issues/18977?journal_id=995392022-10-10T17:42:23Zmame (Yusuke Endoh)mame@ruby-lang.org
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/99539/diff?detail_id=63259">diff</a>)</li></ul>