Deprecation warning: warning: $SAFE will become a normal global variable in Ruby 3.0

Question

Deprecation warning: warning: $SAFE will become a normal global variable in Ruby 3.0

qortex opened this issue 4 years ago · comments

This warning shows up in the console when a variable needs to be evaluated in the watch panel (using vscode and ruby-debug-ide):

warning: $SAFE will become a normal global variable in Ruby 3.0

ViugiNick · Answer 1 · Tue Apr 14 2020 02:55:26 GMT+0800 (China Standard Time)

@qortex Can't find $SAFE occurrences, maybe the problem is on the vscode plugin side

Michael Monerau · Answer 2 · Tue Apr 14 2020 03:00:38 GMT+0800 (China Standard Time)

Ok thanks, will look into it!

dkallipo · Answer 3 · Fri Jun 19 2020 19:22:43 GMT+0800 (China Standard Time)

@qortex is there any solution to this problem? Why was the issue closed? Thanks

Michael Monerau · Answer 4 · Fri Jun 19 2020 19:27:35 GMT+0800 (China Standard Time)

Don't know, didn't look into it more than that.
It would be interesting to look up the root cause and know where it comes from, from debase or the vscode plugin.

dkallipo · Answer 5 · Fri Jun 19 2020 20:16:27 GMT+0800 (China Standard Time)

I found the root cause: it's because of vs code's evaluation of global variables during debugging. One way to solve this is by hiding the 'variables' sub-panel on the side-bar.

Michael Monerau · Answer 6 · Fri Jun 19 2020 20:27:36 GMT+0800 (China Standard Time)

Which project is it located in? We could work towards a fix PR.

Dennis Ushakov · Answer 7 · Fri Jun 19 2020 20:50:38 GMT+0800 (China Standard Time)

I think it might be handled on ruby-debug/ruby-debug-ide side, https://github.com/ruby-debug/ruby-debug-ide/blob/master/lib/ruby-debug-ide/commands/variables.rb#L41 //cc @ViugiNick

dkallipo · Answer 8 · Fri Jun 19 2020 22:26:03 GMT+0800 (China Standard Time)

Which project is it located in? We could work towards a fix PR.

What I described was actually just a workaround to get rid of the annoying warning by just changing the VS code GUI settings. FYI, I resorted to downgrading to Ruby 2.6 because I was experiencing inconsistent and strange behavior by the VS code debugger after upgrading to Ruby 2.7. Not worth it.