Closed apupier closed 1 month ago
cc @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.
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.
There was a nicer message: [WARNING] Failed to collect user input for analytics
...
@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.
this should be backported if possbile
Describe the bug
It can be reproduced when using the devfile from the devfile registry and starting the remote dev
see https://github.com/devfile/api/issues/1611
Expected behavior
no stacktrace
Actual behavior
there is a stacktrace logged:
How to Reproduce?
No response
Output of
uname -a
orver
No response
Output of
java -version
No response
Quarkus version or git rev
No response
Build tool (ie. output of
mvnw --version
orgradlew --version
)No response
Additional information
I wasn't able to reproduce with a local build https://github.com/devfile/api/issues/1611#issuecomment-2210420139