[#101179] Spectre Mitigations — Amel <amel.smajic@...>
Hi there!
5 messages
2020/12/01
[#101180] Re: Spectre Mitigations
— Chris Seaton <chris@...>
2020/12/01
I wouldn’t recommend using Ruby to run in-process untrusted code in the first place. Are people doing that?
[#101694] Ruby 3.0.0 Released — "NARUSE, Yui" <naruse@...>
We are pleased to announce the release of Ruby 3.0.0. From 2015 we
4 messages
2020/12/25
[ruby-core:101435] [Ruby master Bug#17331] Let Fiber#raise work with transferring fibers
From:
eregontp@...
Date:
2020-12-13 12:16:59 UTC
List:
ruby-core #101435
Issue #17331 has been updated by Eregon (Benoit Daloze). Status changed from Open to Closed https://github.com/ruby/ruby/pull/3795 is merged, closing. IMHO this is not a bug but additional behavior, I don't think it makes sense to backport. ---------------------------------------- Bug #17331: Let Fiber#raise work with transferring fibers https://bugs.ruby-lang.org/issues/17331#change-89203 * Author: nevans (Nicholas Evans) * Status: Closed * Priority: Normal * Backport: 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN ---------------------------------------- It would be useful to use `raise` on transferring fibers just as we can with yielding fibers. I've added a `transfer` kwarg, so it is not automatic; the caller must know how to handle the fiber. If you call a yielding fiber with `transfer: true` or a transferring fiber without `transfer: true`, a `FiberError` will be raised. Resuming fibers still raise a `FiberError`. ```ruby yielding_fiber.raise "message" # => resumes and raises from the last Fiber.yield transferring_fiber.raise "message", transfer: true # => transfers and raises from the last fiber.transfer resuming_fiber.raise "message" # => raises FiberError ``` Implementation: https://github.com/ruby/ruby/pull/3783 I also implemented a second version that implicitly and automatically selects `rb_fiber_transfer_kw` for transferring fibers and `rb_fiber_resume_kw` for yielding fibers. The implicit version also raises `FiberError` on resuming fibers. ```ruby yielding_fiber.raise "message" # => resumes and raises from the last Fiber.yield transferring_fiber.raise "message" # => transfers and raises from the last fiber.transfer resuming_fiber.raise "message" # => raises FiberError ``` Alternate implicit implementation: https://github.com/ruby/ruby/pull/3795 I slightly prefer the explicit version, but I'm okay with the implicit version. -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>