Closed Bug 2038991 Opened 19 days ago Closed 11 days ago

Update map_gecko_prefs_to_enrollment_slugs_and_update_store to have a param to signal not updating Gecko

Categories

(Firefox for Android :: Experimentation and Telemetry, task)

All
Android
task

Tracking

()

VERIFIED FIXED

People

(Reporter: olivia, Assigned: olivia)

References

(Blocks 1 open bug)

Details

(Whiteboard: [fxdroid][group6])

Attachments

(1 file)

Update map_gecko_prefs_to_enrollment_slugs_and_update_store to have a param that prevents updating the experiment with Gecko. Sometimes, we just need the information refreshed.

ToDo:

  • Expand map_gecko_prefs_to_enrollment_slugs_and_update_store with a param like update_gecko that guards set_gecko_prefs_state (maybe others)
  • Update commit_and_update to set the flag here
  • register_previous_gecko_pref_states should call writer.commit()?; and call self.database_cache.commit_and_update_without_telling_gecko(), which calls map_gecko_prefs_to_enrollment_slugs_and_update_store with update_gecko= false
  • Thoroughly test that this behaves as expected

Reason for this change is this is causing the dbcache can go out of sync. No identified bugs at this time, but it has the potential to introduce them in the future.

Assignee: nobody → ohall
See Also: → 2021137

Authored by https://github.com/ohall-m
https://github.com/mozilla/application-services/commit/242220acf4da784812dd2ec0495f3465a4aa4da8
[main] Bug 2038991 - Update Cache when calling register_previous_gecko_pref_states (#7369)

Status: NEW → RESOLVED
Closed: 11 days ago
Flags: qe-verify+
Resolution: --- → FIXED

Hi, Olivia
Could you provide us some steps in order to verify this fix?
Thank you!

Flags: needinfo?(ohall)

Thanks, Mira!

Sure, a spot-check retest of this this case or this case will probably be the best ones to run.

The patch adjusted how original values are saved in the database. So, the risk is if the database stopped saving the original value as expected or caused an unexpected issue somewhere else. That original value is then used to reset the pref back.

Randomly selecting any of the cases involved in unenrollment and restoring to an original value would be good for verification.

Thank you!

Flags: needinfo?(ohall)

I'll mark this as verified, since I went through all the unenrollment scenarios and in each case the prefs were correctly reset to their default values. Tested using Firefox Nightly 153.0a1 (Build #2016163802) on Android 11.

Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: