-
Notifications
You must be signed in to change notification settings - Fork 130
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
Bug 1685522 - Add the 'clients activity API' and implement the baseline ping for the RLB #1455
Conversation
b71d05d
to
4bc764b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Implementation-wise this looks good.
Few things I'd like some rephrasing on.
One thing I realized is that we don't really have docs on how to integrate the RLB, that is: when to call what function.
It doesn't need to be solved in this PR (except maybe a short call out where/when handle_(in)active needs to happen)
glean-core/android/src/main/java/mozilla/telemetry/glean/Glean.kt
Outdated
Show resolved
Hide resolved
This makes the naming scheme a bit more meaningful outside of the mobile space. This additionally updates the documentation.
This additionally updates the docs.
f0ae668
to
c87022c
Compare
This additionally ports the tests from the Kotlin implementation.
This checks if the dirty bit is set at startup and generates the relative ping. It additionally ports the relevant tests from Kotlin.
This additionally moves the logic from the GleanLifecycleObserver to the Glean.kt file. The logic was spread between the two files, making it harder than needed to understand what happened when changing the state. This additionally fixes the tests.
d6beb33
to
86a3eab
Compare
This PR does a bunch of things:
baseline
ping with reasondirty_startup
for the RLB;TODO:
Swift!(filed a bug)