getting in $SAFE level 4 freezes

We very much appreciate reports on safe level bugs, especially with provided tests. If there's any test suites out there that hit safe levels and unsafe features like tainting really hard we'd love to know about it.

So how about your opinion on one thing: since safe levels are fairly broken in JRuby right now, should we just disable them and display a warning when someone sets safe levels? It seems the best case for broken safe levels would be that they don't actually do anything, since code would continue to run correctly.

Hi Charles,

> should we just disable them and display a warning when someone sets safe levels?

seems like the best immediate solution. I wouldn't even warn at setting the level, I'd just warn "in the documentation".

If I can spare some cycles, I will look for a test suite for safe levels and tainting, and post back.

I'd almost feel better with a runtime warning (maybe only once?) so people don't have a false sense of security in their code on JRuby...but it's debatable.

A suite of tests that really hit SAFE and all hard would be really, really cool for you to contribute.

I think we need to take a stand on SAFE levels; make them work right, or ignore them and disable tests that expect them to do something. We've let this drag on a long time.

Things released here and based on JRuby rely on "SAFE levels don't exist in JRuby". Not expecting them anymore.

Punting issues from 1.1 RC2 to 1.1 final.

I disabled safe levels completely for 1.1, since they blow up in horrible ways if you set them, and they wouldn't be accurate even if they were set. Now a warning is displayed and the safe level goes unchanged.

Post 1.1, if ever.

JRuby does not and will not support SAFE levels, or at least won't support them the way MRI does. However this bug was reporting the freeze-up when going into $SAFE level 4, which now is essentially a no-op. So I'm marking resolved retrospectively, and if we ever decide to revisit SAFE we can open new bugs/enhancements.