Skip to content
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

Losing Input Key Presses on OSX when running via gradle run #18819

Open
xasmx opened this issue Oct 29, 2021 · 4 comments
Open

Losing Input Key Presses on OSX when running via gradle run #18819

xasmx opened this issue Oct 29, 2021 · 4 comments
Labels
a:bug in:console output progress tty mintty cygwin cli

Comments

@xasmx
Copy link

xasmx commented Oct 29, 2021

Expected Behavior

I'm running a simple Java application via gradle and piping the output to less: 'gradle run | less'.
My application produces lots of output and I'd expect to be able to scroll up and down in the output within less.

Current Behavior

Every other of my key presses seem to disappear. Normally, I'd expect to press the enter key once to get less to go one row down and to press the space key once to get less to go one screen down. Instead, because every other key press disappears, I'll have to press enter twice or press space twice for this to occur.

When the application is ran directly without 'gradle run' and piped to less, everything works as expected.

Steps to Reproduce

demo.tar.gz

Extract the attached archive and run the application with 'gradle run | less'

Your Environment

Gradle 7.2
Macbook Pro 2019, running Big Sur 11.4.
Java version: openjdk 17 2021-09-14
Running on standard osx Terminal and zsh.

@jbartok jbartok added in:console output progress tty mintty cygwin cli and removed to-triage labels Nov 1, 2021
@jbartok
Copy link
Member

jbartok commented Nov 1, 2021

Could you pls. check what happens if you run gradle with the --console plain option?

@xasmx
Copy link
Author

xasmx commented Nov 1, 2021

The same problem happens when running with --console plain.

@github-actions
Copy link

github-actions bot commented Nov 1, 2022

This issue has been automatically marked as stale because it has not had recent activity. Given the limited bandwidth of the team, it will be automatically closed if no further activity occurs. If you're interested in how we try to keep the backlog in a healthy state, please read our blog post on how we refine our backlog. If you feel this is something you could contribute, please have a look at our Contributor Guide. Thank you for your contribution.

@github-actions github-actions bot added the stale label Nov 1, 2022
@ov7a ov7a self-assigned this Aug 4, 2023
@ov7a
Copy link
Member

ov7a commented Aug 4, 2023

Sorry for the late reply.

Thank you for providing a valid report.

The issue is in the backlog of the relevant team, but this area of Gradle is currently not a focus one, so it might take a while before a fix is made.


This issue is still reproducible with Gradle 8.3-rc-3, both with --console=plain and without it.

Note that it would be useful to add Thread.sleep to reproducer loop to avoid getting OOM error.

@ov7a ov7a removed the stale label Aug 4, 2023
@ov7a ov7a removed their assignment Aug 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a:bug in:console output progress tty mintty cygwin cli
Projects
None yet
Development

No branches or pull requests

3 participants