Skip to content

[backport/v65.2] Kotlin: For lateinit metrics, check that the metric was instantiated before recording on it#3310

Merged
badboy merged 1 commit intosupport/v65.2from
hotfix-v65.2.3
Nov 6, 2025
Merged

[backport/v65.2] Kotlin: For lateinit metrics, check that the metric was instantiated before recording on it#3310
badboy merged 1 commit intosupport/v65.2from
hotfix-v65.2.3

Conversation

@badboy
Copy link
Copy Markdown
Member

@badboy badboy commented Nov 6, 2025

This should not happen, but apparently it does in Fenix. I have no idea why or how to prevent it.
But we can mitigate it.
Downside: If the instance is not instantiated by the time set actually runs we don't record any data. But then again before we just crashed, which also didn't record data.


Same as #3309, backported to v65.2

…before recording on it

This _should not_ happen, but apparently it does in Fenix. I have no
idea why or how to prevent it.
But we can mitigate it.
Downside: If the instance is not instantiated by the time `set` actually
runs we don't record any data. But then again before we just crashed,
which also didn't record data.
@badboy badboy requested a review from a team as a code owner November 6, 2025 10:12
@badboy badboy requested review from jeddai and removed request for a team November 6, 2025 10:12
@badboy badboy changed the title [backkport/v65.2] Kotlin: For lateinit metrics, check that the metric was instantiated before recording on it [backport/v65.2] Kotlin: For lateinit metrics, check that the metric was instantiated before recording on it Nov 6, 2025
@badboy badboy merged commit 35547a1 into support/v65.2 Nov 6, 2025
27 of 28 checks passed
@badboy badboy deleted the hotfix-v65.2.3 branch November 6, 2025 10:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant