You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Worker uses the SecurityManager to prevent System.exit. The SM is deprecated for removal, and will be going away soon.
Previously, we've been punting on this issue by enabling the SM for Java 17+, but this won't continue to work.
The linked JEP contains source for a Java agent, which could be used to block System.exit (see the JEP appendix), but I'm wondering if we'd be better off just removing the SM code and not replacing it?
Do people actually have a lot of code they need to test with rules_scala, which calls System.exit, making it worth trying to block?
The text was updated successfully, but these errors were encountered:
The Worker uses the SecurityManager to prevent
System.exit
. The SM is deprecated for removal, and will be going away soon.Previously, we've been punting on this issue by enabling the SM for Java 17+, but this won't continue to work.
The linked JEP contains source for a Java agent, which could be used to block
System.exit
(see the JEP appendix), but I'm wondering if we'd be better off just removing the SM code and not replacing it?Do people actually have a lot of code they need to test with
rules_scala
, which callsSystem.exit
, making it worth trying to block?The text was updated successfully, but these errors were encountered: