`elide kotlinc/javac --no-telemetry` fails with an exception

[y9vad9]

Expected Behavior

I am not sure whether --no-telemetry should be even applicable for javac or kotlinc, but it seems to have some kind of logic to it and behaves differently than elide --no-telemetry.

In case of unapplicable option, it should show the similar output to elide --no-telemetry:

> elide --no-telemetry
Unknown option: '--no-telemetry'

Actual Behaviour

I get an exception.

Stacktrace

kotlin.UninitializedPropertyAccessException: lateinit property telemetry has not been initialized
	at elide.tool.cli.AbstractSubcommand.getTelemetry$cli(AbstractSubcommand.kt:341)
	at elide.tool.cli.AbstractSubcommand.invoke-AZeniH0$suspendImpl(AbstractSubcommand.kt:583)
	at elide.tool.cli.AbstractSubcommand.invoke-AZeniH0(AbstractSubcommand.kt)
	at elide.tool.cli.AbstractToolCommand$call$$inlined$execute$1.invokeSuspend(AbstractToolCommand.kt:244)
	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
	at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:100)
	at kotlinx.coroutines.EventLoopImplBase.processNextEvent(EventLoop.common.kt:263)
	at kotlinx.coroutines.BlockingCoroutine.joinBlocking(Builders.kt:94)
	at kotlinx.coroutines.BuildersKt__BuildersKt.runBlocking(Builders.kt:70)
	at kotlinx.coroutines.BuildersKt.runBlocking(Unknown Source)
	at kotlinx.coroutines.BuildersKt__BuildersKt.runBlocking$default(Builders.kt:48)
	at kotlinx.coroutines.BuildersKt.runBlocking$default(Unknown Source)
	at elide.tool.cli.AbstractToolCommand.call(AbstractToolCommand.kt:292)
	at elide.tool.cli.AbstractToolCommand.call(AbstractToolCommand.kt:55)
	at picocli.CommandLine.executeUserObject(CommandLine.java:2031)
	at picocli.CommandLine.access$1500(CommandLine.java:148)
	at picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2469)
	at picocli.CommandLine$RunLast.handle(CommandLine.java:2461)
	at picocli.CommandLine$RunLast.handle(CommandLine.java:2423)
	at picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2277)
	at picocli.CommandLine$RunLast.execute(CommandLine.java:2425)
	at picocli.CommandLine.execute(CommandLine.java:2174)
	at elide.tool.cli.Elide$Companion.entry(Elide.kt:585)
	at elide.tool.cli.MainKt.main(main.kt:328)
	at java.base@24/java.lang.invoke.LambdaForm$DMH/sa346b79c.invokeStaticInit(LambdaForm$DMH)
elide Exiting with code -1 due to uncaught kotlin.UninitializedPropertyAccessException: lateinit property telemetry has not been initialized

Steps To Reproduce

1. Install 1.0.0-Beta6/1.0.0-Beta7
2. Run either elide javac --no-telemetry or elide kotlinc --no-telemetry

Environment Information

No response

Runtime

Native

Language

No response

Example Application

No response

Version

1.0.0-Beta7

[y9vad9]

It seems to fail for every command that doesn't have --no-telemetry in --help output.

[sgammon]

"Telemetry" in this case refers to some anonymous signals sent to analytics to let us know whether Elide is failing or succeeding for users. It basically contains the exit code and subcommand that was run, that's it (no user IP, no full args or env, no code, anything like that).

We have it on during the beta but it's definitely causing more problems than I'd like. I may just shut it off until we can get it right. In this case, I think the "common CLI options" specify --no-telemetry, but those aren't mixed into commands which implement a full entrypoint, like elide kotlinc or elide javac.