In some context, NoSuchElementException: No line found error thrown from telemetry

[apupier]

Describe the bug

It can be reproduced when using the devfile from the devfile registry and starting the remote dev

see devfile/api#1611

Expected behavior

no stacktrace

Actual behavior

there is a stacktrace logged:

tools: ----------------------------
tools: --- Help improve Quarkus ---
tools: ----------------------------
tools: * Learn more: https://quarkus.io/usage/
tools: * Do you agree to contribute anonymous build time data to the Quarkus community? (y/n and enter) 
tools: [WARNING] Failed to collect user input for analytics
tools: java.util.NoSuchElementException: No line found
tools:     at java.util.Scanner.nextLine (Scanner.java:1660)
tools:     at io.quarkus.maven.DevMojo.lambda$execute$0 (DevMojo.java:445)
tools:     at io.quarkus.analytics.ConfigService.lambda$userAcceptance$0 (ConfigService.java:79)
tools:     at java.util.concurrent.CompletableFuture$AsyncSupply.run (CompletableFuture.java:1768)
tools:     at java.lang.Thread.run (Thread.java:1583)
tools: [info] [Quarkus build analytics] Didn't receive a valid user's answer: `y` or `n`. The question will be asked again next time.

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

I wasn't able to reproduce with a local build devfile/api#1611 (comment)

[geoand]

cc @brunobat

[brunobat]

This is just a harmless warning it can be avoided altogether by placing the following file:
~/.redhat/io.quarkus.analytics.localconfig
with contents:

{"disabled":false}

This way analytics will be on and user input will not be requested, therefore speeding up the application startup.

[apupier]

In the context the error is hit, it is using the ubi (Universal Base Image). I do not think that we should put this kind of file in this image.
An alternative would be to provide a specific image for Quarkus devfiles but it sounds a bit overkill just for that.

And if we place it, we must set "disabled": true, the telemetry must be something opt-in.

I think a good solution is to provide a nicer message instead of a stacktrace.

[brunobat]

There was a nicer message: [WARNING] Failed to collect user input for analytics...

[quarkus-bot]

@maxandersen triage/backport* labels may not be added to an issue. Please add them to the corresponding pull request.

_{This message is automatically generated by a bot.}

[maxandersen]

this should be backported if possbile