From 533f52bdf9a79d243fcefbf0b03986883492a7e0 Mon Sep 17 00:00:00 2001 From: Kris Wright Date: Fri, 18 Dec 2020 21:24:33 +0000 Subject: [PATCH] Bug 1682571 - Update prefs_file_was_invalid telemetry r=chutten,decoder We are interested in knowing if and when the prefs file fails to read. Since Preferences silently handles this failure by resetting the prefs file (which is not ideal), the best way to find out if this is failing is via telemetry probe. The `prefs_file_was_invalid` telemetry already exists so it only needs to be updated. Differential Revision: https://phabricator.services.mozilla.com/D99911 --- toolkit/components/telemetry/Scalars.yaml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/toolkit/components/telemetry/Scalars.yaml b/toolkit/components/telemetry/Scalars.yaml index d1443cbdb5fb..a8f93b56c15e 100644 --- a/toolkit/components/telemetry/Scalars.yaml +++ b/toolkit/components/telemetry/Scalars.yaml @@ -1926,16 +1926,16 @@ preferences: prefs_file_was_invalid: bug_numbers: - 1367813 + - 1682571 description: >- Set to true if a failure occurred reading profile/prefs.js. - expires: "62" + expires: never kind: boolean notification_emails: - - bsmedberg@mozilla.com + - kwright@mozilla.com release_channel_collection: opt-out products: - 'firefox' - - 'fennec' record_in_processes: - main read_user_js: