[#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:101779] [Ruby master Bug#17484] pry & byebug gems not working properly with Ruby 3.0.0
From:
ventpdev@...
Date:
2020-12-28 13:41:08 UTC
List:
ruby-core #101779
Issue #17484 has been reported by pabs08 (Pablo Vent). ---------------------------------------- Bug #17484: pry & byebug gems not working properly with Ruby 3.0.0 https://bugs.ruby-lang.org/issues/17484 * Author: pabs08 (Pablo Vent) * Status: Open * Priority: Normal * ruby -v: 3.0.0 * Backport: 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN ---------------------------------------- When I try to use pry with version 3, it won't allow me. For example when I type in the command next in the terminal, an error message says: "can't escape from eval with next". When using byebug's command step, version 3 I get an error that says "NameError: undefined local variable or method `step' for main:Object". I'm using MacOS 10.15.7 at the moment. To circumvent this issue, I had to revert back to 2.7.1 where these gems work just fine. ---Files-------------------------------- Screen Shot 2020-12-28 at 13.33.56.png (406 KB) Screen Shot 2020-12-28 at 13.34.15.png (510 KB) ruby_3.rb (129 Bytes) -- 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>