Closed chadlwilson closed 2 years ago
ntkme
commented
2 years ago The tests in GitHub Actions run with JRuby on Java 11 today, so that it does not expose the issue you're facing.
And yes, this is a JRuby issue: https://github.com/jruby/jruby/issues/6721
chadlwilson
commented
2 years ago @ntkme Thank you! I am previously aware of the underlying JRuby problem after doing a Java 17 migration, but it's a bit weird that one doesn't get any feedback or see the normal error from the JVM subsystem when you try to access something you're not allowed to. That's probably a separate JRuby quirk that it's swallowing the root cause error somehow.
HI there - thanks for this project, it looks promising to make a migration away from
ruby-sassandlibsasspossible, sincedartsass-railsdoesn't seem to be as nicely integrated with Rails/Sprockets as we'd like for development purposes and gettinglibsassto compile for Windows seems to be a bit of a nightmare; not worth the effort for something deprecated (supporting Windows dev/test is currently a requirement for us).I'm parking this here as came across an issue that might be of use to others on JRuby.
When pre-compiling assets for
testorproductionunder JRuby it's possibIe to get errors like the below, but no feedback on the problematic file. When indevelopmentmode, things just hang in JRuby threads without feedback - you can see forkeddartprocesses, but JRuby-land is just waiting for responses.Environment
Problem
Getting error with
rake assets:clobber assets:precompile --tracevia JRubyThere is no other feedback on the problem, or what it was trying to do. What is actually happening is that forking dartsass seems to require "Native subprocess control" which is restricyed on Java 16+. Normally JRuby will warn you with
Solution
Ensure you have these args (
--add-opens java.base/sun.nio.ch=ALL-UNNAMED --add-opens java.base/java.io=ALL-UNNAMED) to your JVM JRuby is running in, andsassc-embedded-shim-rubywill work correctly.I suspect this project isn't necessarily validated with JRuby, so wanted to note this here. I also suspect the "feedback" problem isn't so much this project's problem as some challenge with our setup, or JRuby itself. So we can probably close this immediately :-)
Fuller log