windows shell problem on quarkus dev

[taricu]

Describe the bug

Tests paused
Press [e] to edit command line args (currently ''), [r] to resume testing, [o] Toggle test output, [:] for the terminal, [h] for more options>2024-05-29 14:21:22,129 INFO  [org.aes.rea.ter.imp.WinSysTerminal] (WindowsStreamPump) read Windows terminal input error: : java.io.IOException: ReadConsoleInputW failed: Incorrect function.
	at org.fusesource.jansi.internal.Kernel32.readConsoleInputHelper(Kernel32.java:531)
	at org.aesh.readline.terminal.impl.WinSysTerminal.readConsoleInput(WinSysTerminal.java:83)
	at org.aesh.readline.terminal.impl.AbstractWindowsTerminal.pump(AbstractWindowsTerminal.java:311)
	at java.base/java.lang.Thread.run(Thread.java:1570)

Expected behavior

No response

Actual behavior

No response

How to Reproduce?

No response

Output of uname -a or ver

No response

Output of java -version

No response

Quarkus version or git rev

No response

Build tool (ie. output of mvnw --version or gradlew --version)

No response

Additional information

No response

[FroMage]

We observed this issue on Windows when launched from IntelliJ's console. It was working fine otherwise, but this kept being logged every few seconds.

[FroMage]

This was when running Quarkus DEV.

[mingcode100]

I also encountered the same problem. What needs to be supplemented is that I didn't have any issues on another Windows 11 computer.

Intel i5-10500
RTX 4060

[gregmagdits]

Same issue here, specifically with Windows 10, Intellij 2024.1.2 and Quarkus 3.11.0. I have not found a workaround yet and the issue makes developing quarkus apps on windows+intellij pretty difficult, since the error message floods the logs. The issue is probably in aesh.readline + Jansi dependencies though (versions 2.4 and 2.4.0 respectively). Unfortunately those libraries don't appear to have frequent releases.

[mingcode100]

I made new progress, switched to jdk 21, and then it was solved....
gnodet/jansi#1

[zelytra]

Still have this problem with jdk21, it spam every millisecond for me. That makes intellij unusable.
The only way to "solve" this problem is to run Quarkus by disabling the continous testing in the config file :
quarkus.test.continuous-testing=disabled

[FroMage]

Oh, interesting that it would be related to continuous testing :-/

[zelytra]

Work also by running dev mode with this command :
quarkus:dev -Dquarkus.console.enabled='false'
Don't know if it can help but just saying