-
Notifications
You must be signed in to change notification settings - Fork 927
Fix custom trace event dispatch before initialization for Performance Monitoring #3850
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
Conversation
🦋 Changeset detectedLatest commit: 8f7a46a The changes in this PR will be included in the next version bump. This PR includes changesets to release 7 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Binary Size ReportAffected SDKs
Test Logs |
Size Analysis ReportAffected Products
|
Type | Base (a6af7c2) | Head (c480f14) | Diff |
---|---|---|---|
size | 16.8 kB | 16.9 kB | +67 B (+0.4%) |
size_with_ext_deps | 21.8 kB | 33.9 kB | +12.0 kB (+55.0%) |
trace
Size
Type | Base (a6af7c2) | Head (c480f14) | Diff |
---|---|---|---|
size | 16.7 kB | 16.8 kB | +67 B (+0.4%) |
size_with_ext_deps | 21.7 kB | 33.8 kB | +12.1 kB (+55.7%) |
Test Logs
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.
LGTM. Can you please add changeset? Is there a GitHub issue we can reference?
Changeset File Check
|
Thank you! I added a changeset, and the issue comes from internal support flow, Internal tracking bug: b/169126072. |
Developer reported that
custom trace
right after initializing perf object was not able to be recorded. That is because initialization didn't finish, thus was not able to flip the bit ofSettingsService.loggingEnabled
from false to true. Therefore custom trace was discarded.Fix
Check
SettingsService.loggingEnabled
after initialization finishes, thus avoid dropping events before reading RemoteConfig value.Internal tracking bug: b/169126072