-
-
Notifications
You must be signed in to change notification settings - Fork 925
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Warning "io/console not supported; tty will not be manipulated" occurs again on 1.7.23 #3550
Comments
Yes - I observe this with 1.7.22 on Windows but not 1.7.16.1 C:\Users\rattrill>jruby -v C:\opt\jruby-1.7.16.1\bin>jruby -v |
* jruby-1_7: (27 commits) Update jnr-posix to finally fix 32 bit JVM crasher on windows stat pend marshaling behavior - not working for Java non-member classes (GH-3526) local (non-member) classes should have correct name just like anonymous classes DRY out getClassFromPath usage in UnmarshalStream (all delegating to one method) review runtime's getClassFromPath hide unmarshalObject methods that use private inner type as a parameter Update for newer jnr-posix for windows 32 bit JVM stat workaround Remove remaining `should` uses from compiler specs. Don't deoptimize while loops just because of a block arg. Always assign masgn destructured args in block as block-local. Move parser scripts to tool. Add case for breakage fixed in b93fbb6e431. Check for empty identifiers and treat them as false. Same fix for AOT as for interp for #3180. Also use the anonymous wrap class for pushRubyClass, for defs. More robust, less breaky fix to omit bad class/package elements. Revert "Use methods instead of procs for converters." Fixes #3550. Warning "io/console not supported; tty will not be manipulated" occurs again on 1.7.23 updating to jcodings messes with this obscure char no longer being considered a space. Update to latest jcodings ...
I get the same error in Windows 10, with ruby 2.3.3 (64bit) ruby 2.3.3p222 (2016-11-21 revision 56859) [x64-mingw32] |
@psuzzi well we can't do much about that on JRuby's end :) ... report with Ruby! |
@kares I think he might be saying we match MRI behavior? |
Sorry, my bad. This IS about JRuby, but I wrongly reported the version of ruby. Here you can see a pastebin for the error: http://pastebin.com/Di6V9hAK |
and what would the version of JRuby (used by Gradle's asciidoctor) be than :) ? if you have any hints ... |
From my understanding, gradle asciidoctor plugin uses asciidoctorj. But the gradle plugin is using asciidoctorj 1.5.3.2 |
thanks @fap- ... @psuzzi please try the latest version (which should be 1.5.4) as this has been resolved around 1.7.24 thus 1.5.3 might not have the desired JRuby version (and would still warn) ! |
Using: jruby 1.7.23 (1.9.3p551) 2015-11-24 f496dd5 on Java HotSpot(TM) 64-Bit Server VM 1.7.0_79-b15 +jit [Windows 7-amd64]
A related issue, #1614, was closed on the grounds, that it was finally fixed (for Windows).
At least in JRuby 1.7.23, installed from
https://s3.amazonaws.com/jruby.org/downloads/1.7.23/jruby_windows_x64_1_7_23.exe
the warning still occurs, when I do a
jruby -c FILENAME
The text was updated successfully, but these errors were encountered: