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
Hi,
We came across this the other day. Our ruby file(incidentally in our rails/initializers) had a comment on how to use that initializer. But the comment started on the first line and read similar to
# To use this do
# ABClassName.turnOn= true
................
..........
This caused one of the jruby runtimes to fail with the message 'Cannot load ABClassName' which was clearly available and loaded already.
We were able to fix this issue by doing the following
(essentially by making the first line a non-parsable string)
# -----------------------------
# To use this do
# ABClassName.turnOn= true
................
..........
Possibly Jruby expects shebang kind of statements(#! /usr/bin/ruby) for interpretation on the first line and having anything else just confuses it.
-Hope this helps and is fixed.
Thanks
Sudhindra
The text was updated successfully, but these errors were encountered:
I also can't reproduce this problem locally. @betarelease are you still experiencing the problem? Can you provide a full test case with the file, the command line, the version and platform info?
Hi,
We came across this the other day. Our ruby file(incidentally in our rails/initializers) had a comment on how to use that initializer. But the comment started on the first line and read similar to
This caused one of the jruby runtimes to fail with the message 'Cannot load ABClassName' which was clearly available and loaded already.
We were able to fix this issue by doing the following
(essentially by making the first line a non-parsable string)
Possibly Jruby expects shebang kind of statements(#! /usr/bin/ruby) for interpretation on the first line and having anything else just confuses it.
-Hope this helps and is fixed.
Thanks
Sudhindra
The text was updated successfully, but these errors were encountered: